Age | Commit message (Collapse) | Author |
|
|
|
processing order is now as follows;
- widget that keypress occured it trys to handle the event.
- then to keyboard shortcut processing for the widget's children
- then work back towards the top-level form giving chance for
keyboard navigation (tabstop) processing. eg: pressing Tab key
- then let the top level form to keyboard shortcut processing
eg: allowing MainMenu to process the event.
- then allow the top level for to process OnKeyPress if such an
event handler is implemented.
- then if the top level form is not the MainForm, and the current
top level form is not shown model, allow the application.mainform
to process the keyshortcut in it's main menu.
|
|
This is similar to HandleKeyPress() but takes into account the original
widget that started the process, so it doesn't process that widget or its
children twice.
|
|
In KeycodeToText(), 'Shift+' came before Ctrl or Alt. This is not normal
practice, so I moved it.
|
|
This is a UI Designer friendly component that allows you to embed frames
"Windows" inside other windows.
|
|
|
|
|
|
- Renamed the timer field variable from T_Chrono to FTimer.
- Renamed the OnTimer event handler from T_ChronoFini to HintTimerFired
- Disabled the timer *before* hinding the hint window. This prevents
those add AV's that occur when you close an application.
- No need to explicityl disable the timer in HintWindow destructor.
When you free a timer, it automatically gets disabled.
|
|
Now the internal blink timer only gets activating when a Canvas is assigned.
|
|
|
|
I was clearly smoking something that day! Anyway, the GDI timer is now
correctly implemented, and doesn't push up the CPU load any more. No matter
how long the timer runs for. The timer is much more accurate/consistent in
firing as well. :-)
|
|
Refactored the TfpgTimer by introducing a TfpgBaseTimer and X11 & GDI Timer
descendants. This now allows use to add platform specific extensions to
the timer implementation.
|
|
|
|
This shoud prevent the 'Index out of bounds' errors.
|
|
|
|
This helps those odd borderline cases, so now the scrollbar always seems
appropriate when it is visible.
|
|
Now that we correctly the FLayout.Width value this change could now be
made.
|
|
- Ultimately this is so we can fix the Layout.Width problem when UTF-8
characters are used in INF documents. eg: the FPC ref.inf file.
- UTF-8 characters can be greater than one byte, so we had to make some
changes.
- Changed some usages of Char to TfpgChar
TODO:
- CopyPlainTextToBuffer() implementation has been commented, until we can
rewrite it for use with fpGUI.
This is a big changes, but I tested DocView with numerous INF documents and
all seems well.
|
|
instead we should be looking at the overall FScrollBarWidth field value
which defines the Width or Height of all Scrollbars in RichView.
|
|
|
|
When we reach the end of a line, we shouldn't always default alignment
back to Left - I think. Anyway, this changes makes the output in DocView
look the same as IBM's iview program.
|
|
|
|
|
|
Refactored the code, so we only use UpdateScrollBarCoords() method.
|
|
It's the rectangle between the two scrollbars.
|
|
- added a unit header comment
- removed old code comments not needed any more
- removed old debug lines
|
|
- fixes the spelling of 'useful'
- Many 64-bit support fixes. Mainly Integer vs PtrInt changes
- Correct implementation of TRegExpr.GetMatch()
- extra debugging measures
|
|
We now support comments correctly, compiler defines, strings, decimal
and hex numbers.
|
|
|
|
Getting font resources are very costly. So now we cache the font used
for reserved keyword highlighting and simple reuse it, instead of creating
and freeing it for each line (like we did up 'till now).
This caused a MASSIVE speed increase! :-D
|
|
- multiple matches in the same line are now supported
- regex reserved keyword matching is now case-insensitive
|
|
This was used before we implemented regex syntax highlighting.
|
|
- Also improved correct highlighting by using word boundaries in regex.
|
|
|
|
|
|
|
|
A recent commit forced this change so it is consistent with fpGUI and
RTL usage of array property.
|
|
|
|
|
|
|
|
|
|
This is consistent with other components in the RTL, FCL and even fpGUI
itself.
|
|
- A new toolbar button is added in the main form.
- The Bookmarks menu is correctly updated
- Closing a help file correctly clears the bookmarks menu too.
|
|
|
|
|
|
It incorrectly showed "1 match found" due to the message we added to the
search result listbox.
|
|
|
|
|
|
I have successfully tested fpGUI using OpenSolaris 2010.03 (x86) using
FPC 2.4.4.
|
|
It seems FPC only supports users.pp unit in Linux. Making this changes
allows use to compile fpGUI under OpenSolaris too!
|