| Age | Commit message (Collapse) | Author |
|---|
|
not correctly
set the ActionType parameter if the drag was not accepted.
|
|
component
|
|
This does error checking before and DND gets triggered. The error messages
must still be replaced with resource strings though.
|
|
|
|
If the Drop occured, but AcceptDrops = False, we must not do
any Selections conversions. This is now so.
We must still send the XdndFinished message though, so data object
can be freed, and to simply comply with XDND protocol. We now
correctly set the Accept or Decine status in the XDNDFinished
message.
|
|
This will hopefully reduce the confusion between the other
TfpgWidget.AcceptDrops property - they had too similar names.
* Applied rename changes to all other descendants too
* Updated DND demo project
|
|
If the developer did not set the AMimeChoice in OnDragEnter, then
the incorrect default could have been used. By default it
used to deflaut to 'text/plain' and never actually checked the
mime-type list to see if that exists. :-(
Now the default AMimeChoice is set the the first mime-type in
the mime-type list. This keeps with the methodology that the
mime-type list must be from most specific to least specific mime types.
|
|
The bug was that it only checked for the immediate children of
the toplevel window. It never recursed through all levels of
children finding the correct child the mouse cursor is over.
This is now fixed.
This also allows embedded frames or forms to work with DND.
|
|
There was a bug where if the component had a OnDragDrop event
handler and AcceptDrops was False, it still triggered the event.
Not any more.
|
|
I also made sure that all writeln() statements are wrapped in IFDEF's.
|
|
* Single click produces one OnClick event
* On a Double Click in produces a OnClick, then a OnDoubleClick
event. Old behaviour used to procuder yet another OnClick at
the end. This is not needed.
* OnMouseDown and OnMouseUp events behaviour has not changed.
The reason we introduce the FOnClickPending instead of fully
handling the events in TfpgWidget.MsgMouseUp is because a TfpgButton
has slightly different behavior (eg: When clicking on a button, keep
mouse down, and move mouse out of button rectangle, then an
OnClick must not fire.) The extra FOnClickPending allows us to
toggle this behaviour of HandleLButtonUp (which normally fires
the OnClick event)
|
|
This adheres to general coding style.
|
|
This applies to:
clInactiveSel, clUnset, clGridInactiveSel
I wasn't fond of the purple / faded blue color from before.
|
|
|
|
The property does more that just set the color. It calls FormatEdit,
which changes the color of TextColor property. This meant the
parent color was never stored in FOldColor field variable.
|
|
By defining the default color, the UI Designer can omit that
line in generated code, if the color did not change.
|
|
Those properties are exactly the same visibility as inherited
classes, so no point in simply listing them again.
TextColor was the exception, it was public, so you can't decrease
the visibility in descendants.
|
|
* The selection variables were not updated before
* Little error checking was done, so you could get index out of
bounds errors.
|
|
You can now set the Cursor X position via code.
|
|
|
|
|
|
This allows you to add/delete many lines and the memo only
repaints once.
|
|
|
|
It makes more sense to have the tiOPF related units with the
rest of the tiOPF. It's easier to keep changes in sync, and have
atomic commits across the various GUI toolkits supported by tiOPF.
|
|
|
|
|
|
* The last column was already resized to whatever space is available
ignoring the developers preferred (minimum) size. Now the last
column in grows in size, not shrink.
|
|
* It conflicted with the ListBox item mediator introduced in
a earlier commit.
|
|
* one is ItemIndex based returning an int
* one is Dynamic List based returning an object from ValueList
|
|
|
|
|
|
|
|
|
|
The DoMessagesPending() only processed OS events, now ProccessMessages
processes all events like the real event loop does. This gives
a more expected behaviour to developers that write blocking
loops etc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This meant ClearList was never called anywhere.
ClearList() was also slightly incorrect in the ListView mediator.
|
|
|
|
|
|
|
|
|
|
|
|
* It used to have a hard-coded processing of alignment.
Top, Bottom, Left, Right and then Client.
* This meant extra "fake" panels was required to get a specific
design.
* Align property is now processed in the creation order of the
widgets.
|
|
Add extra border painting so it will be more visible in the UI Designer.
|
|
The detection of which neighbouring control to resize was not
100% which resulted in a non-movable splitter. This is now fixed.
|
|
|
