| Age | Commit message (Collapse) | Author |
|---|
|
Painting outside the HandlePaint is possible but very unpredictable,
so it is best we do not do it.
|
|
of columns.
|
|
This is handy if you apply version version information to your
ini files, and on a new version the program must ignore the
old size values (because that sepecific form might have changed
dimensions at design time).
|
|
|
|
* Before, the image was 4 pixels away from the left, in default layout
So when you align many components with there left edges, it
looked as if the checkbox widget wasn't aligned correctly.
* Now the image is only 2 pixels from the edge, so aligning with
other widgets looks much better.
* Focus rectangle is now only drawn around the text portion of the
widget too. This is now similar to most OSes.
|
|
* ComboBox was always auto sized which is not always desired.
We now have a property to control that behaviour.
* Default is False, in preperation for layout managers which
control the size.
* Widget frame borders are now retrieved from the current Style
instance.
* default Height is set to 24px. The same default used for TfpgEdit
widget. Default sizes have been moved up into TfpgBaseComboBox,
out of TfpgBaseStaticCombo.
|
|
* This was done in preperation for layout managers which will
control widget sizes, and AutoSize will just interfere.
* Default Height is now set at 24px (same as what it was before
with default Arial font)
* Also implementeted setter for AutoSize property. This now
correctly adjusts the widget set when the property is changed
to True.
|
|
It's disabled by default. Enabling can be done via project level
or inside each unit at the beginning of such units.
|
|
Old behaviour was that the beginning of long text was scrolled
off the left of the edit, so you saw the end of the text.
Now we should see the beginning of the text and the end of the
Text is out of view on the right.
|
|
|
|
Another one of those annoyances I had to fix. When I enter a file name
to save and want to press ENTER to save and close the dialog.
|
|
|
|
|
|
scrolled. DrawImage does not obey the cliprect.
|
|
TfpgListView.Subitems is actually TfpgListViewSubItems and can be casted as such to alter the imageindex of subitems
Updated the example so subitems have an assigned imagelist
|
|
Fixed a crash in the listview example when it was closing
Updated listview example to use icons
|
|
a large amount of items
Commented a stray WriteLn
|
|
|
|
* TfpgButton now ignores double clicks by default
|
|
* The popup menu caption changes if you click over any non-active tabs
* Selecting the popup menu item, closes the tab you clicked over - no need
to set it as the active tabsheet first, before closing.
|
|
method called TabSheetAtPos(). This allows the developer to reuse this
method too for other things.
|
|
Grid.HeaderStyle has Button, Thin and Flat options
New DrawBevel can draw a bevel raised or lowered using standard system
colors. Quite similar to TfpgBevel.
New DrawBevel() method and new Grid.HeaderStyle option.
|
|
|
|
When I changed the DoubleClick and SingleClick behaviour I accidently
broke the 'click via keyboard' (Enter or SpaceBar).
|
|
This is so they can be tested. Once DND stabilizes, I'll make the
properties available on the other components too.
|
|
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
|
|
* 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)
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
* The SelectedColor is now based on the last active tab.
- If the ColorWheel was active, it takes that selected color
- If the Color Palette Listbox was active, it takes that selected color.
|
|
|
|
|
|
|
|
* A default font size is now set.
* The Writeln() statement is now hidden under IFDEF's like it
was supposed to be.
|
|
repaint
|
|
* Now the UI Designer can work with that property too
* A few other components got one or two other properties published too.
|
