| Age | Commit message (Collapse) | Author |
|---|
|
|
|
A simple spelling mistake!
|
|
We really don't need yet another "default font". All references to
fpgApplication.DefaultFont has been changed to fpgStyle.DefaultFont - as
it should be.
|
|
while testing richview I noticed it's fairly slow, though only if there
are font changes in the content. So I added a font cache to the richview
fontmanager and now there is almost no delay to render content in the
richview. Big, big speed improvement.
|
|
docview now uses a single fpGUI call to do encoding conversions. This
make is much easier to maintaing - a single method needs to be
modified if new encoding conversions get added.
|
|
|
|
- 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.
|
|
|
|
|
|
The CanvasFontManager unit has totally been reworked to use the native
TfpgFont class instead of TLogicalFont, TFontFace etc... The code is
a lot more simplified now and DocView can actually display content
but there are some width wrapping issues and AV's on changing topics.
This will be fixed next.
|
|
|
|
A reference to a default font or fixed font are now the same
throughout docview. If you change one, you change them all.
|
|
|
|
NOTE
This is not a 100% fix, but rather a work-around. I need to still find out
why such AV's occur.
|
|
When scrolling pages that contain large tables of source code
examples using mono fonts, it changed no non-mono fonts. This
is now finally fixed!
|
|
We always use outline fonts in fpGUI.
|
|
We don't want to confuse properties and local variables, so the latter gets
a different style: normally prefixed with the letter 'l'.
|
|
No idea why!! So we comment them simply because they are debug lines
to start with.
|
|
Due to this change the text wrapping has also improved a lot. Still
not 100% but much better than before.
|
|
|
|
|
