Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Attached is another patch I made for the richtext edit. Now the
red/green/blue/black tags can/must be closed by a correct
red/green/blue/black closing tag.
That means that except for the margin tags, all tags can/must now
be closed with a matching tag.
|
|
Due to stricter syntax and other mark-up (tag) changes in RichTextView, we need to update
DocView accordingly. Not much was needed though.
|
|
1) h1, h2 h3 are now ended by /h1 /h2 /h3
2) <wrap yes> and <wrap no> are changed to <nowrap> </nowrap>
3) The size part of the font tag is now optional.
I suspect a small change is still needed in order to apply
the font size if one is specified anyway. I put a comment
in the text for that.
4) I adapted the sample01.txt so it reflects the 1. and 2. changes.
|
|
We already done this for all the predefined colors, but somehow forgot about these.
|
|
|
|
Selected text can now be replaced with new text, or text could be inserted at the current
cursor position by setting SelectionText.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This lets git know how to handle certain files, and overrides the
developers own settings to a project specific setting.
|
|
Those many logevent() calls makes other debugging really difficult.
|
|
|
|
|
|
|
|
Very weird, there was even a code comment saying that it was wrong!! The constructor of
TRichTextSettings already sets the "normal font". So by ignoring the ASettings parameter,
the end-user couldn't assign a new normal font values.
Anyway, this is now fixed.
|
|
|
|
Some fonts like "Anonymous Pro" have characters like ( or ) that is larger (taller) than capital
letters. Using the .Height property make multi-line text with ( or ) symbols not touch. This issue
was noted in the TfpgTextEdit widget used in Maximus IDE.
|
|
|
|
|
|
This makes it very easy to display an image on a form.
|
|
|
|
Under Windows 7, the ',' character for thousand separator was replaced with
a '?' character for some reason. Number formatting now uses a space char
separator instead.
|
|
Multi-threaded apps under Windows requires the main thread to be woken up
periodically. We now simply hook into the Classes.WakeMainThread function
which is automatically called by TThread.Synchronize.
I did the same testing under X11, but it doesn't seem needed there. If we
do find a case for this under X11, it is easy to implement.
|
|
|
|
|
|
No need for so much code duplication. This also means that widgets like TfpgStringGrid now
have keyMenu keypress behaviour. Basically any widget that supports a PopupMenu.
|
|
|
|
|
|
If a report had several sections with different margins, headers, footers,
orientation, frames did not adapt to the correct size and position to each
section.
|
|
any selection.
|
|
Thanks to Michael van Canneyt <michael@freepascal.org> for the patch.
|
|
|
|
This has been a long awaited feature. There is still some functionality missing and some
more tweaks that need to be applied, but this implementation does work. It has been tested
under JWM (Joe's Window Manager), MATE (Gnome2 fork) and KDE 4.8.x
The Windows implementation will follow shortly.
|
|
Sometimes we want to display a popup window, but would like the framework to take into
account the desktop screen size. If the popup window would display outside the bounds of
the screen, we would like fpGUI to reposition the popup window to be fully visible. This will
be used in the System Tray Icon implemenation.
This parameter defaults to False, so the behaviour is exactly like it was before this changes.
|
|
The splash form itself was never freed.
|
|
I'm not sure if this changes is needed any more for the latest FPC though. Anyway, now it is
consistent with most other usages of Xlib API and boolean values.
|
|
is being used.
Hopefully this code changes make it more clear.
|
|
The XLib man pages clearly state that the TXEvent structure must be cleared to 0 values
before use.
|
|
|
|
|
|
No more hard-coded 2 pixel widths.
|
|
client area
There was a hard-coded 2px margin at the top and bottom of the text client area. So when
scrolling the text disappeared 2px away from the actual widget border. This was inconsistent
with other text widgets in fpGUI, and I simply didn't like it either.
So GetTextAreaRect() now returns the same values as GetDrawRect().
|
|
* Also took into account theming support, so we get the size of the default borders from the
theme class.
* Improved the method that sets the coordinates of the scrollbar
|
|
I forgot the actually set the Font property of the Canvas. :-/
|