summaryrefslogtreecommitdiff
path: root/docview/components/richtext
AgeCommit message (Collapse)Author
2015-08-22richview: fix bug where varied size fonts didn't start on baseline.Philippe Lévi
2015-08-09richview: earmarked TRichTextView.CopyTextToBuffer() to be removedGraeme Geldenhuys
2015-08-09richview: correctly typecast result in TLayoutLineList.GetItem()Philippe Lévi
2015-08-08richview: fixes bug with Italic text adding an extra space at the endGraeme Geldenhuys
I thought I fixed all of these before, but I missed this one.
2015-08-06RichText: fixed the bug where Underlined text didn't work.Graeme Geldenhuys
A simple spelling mistake!
2015-02-19Removed fpgApplication.DefaultFontGraeme Geldenhuys
We really don't need yet another "default font". All references to fpgApplication.DefaultFont has been changed to fpgStyle.DefaultFont - as it should be.
2014-03-30Richview resize/render speedAndrew Haines
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.
2013-05-22richview: let the fpgStyle object do the drawing for us.Graeme Geldenhuys
2013-05-13docview: replace some code with convenience function to make it more readableGraeme Geldenhuys
2013-04-29RichView Editor test application.Michael van Canneyt
2013-04-25docview: greatly improve scrolling speed when help topic contains imagesGraeme Geldenhuys
We always did StretchDraw() which is rather CPU intensive. Now we check the image dimensions first, then decide if StretchDraw() is really needed or not. If not, then do the much faster DrawImage() call.
2013-04-25docview: refactored text encoding versionGraeme Geldenhuys
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.
2013-03-12richtext: minor improvement to default used colorsGraeme Geldenhuys
2012-12-04RichTextView can now have Text set even in the constructor phase of a form.Graeme Geldenhuys
Before we were forced to only set text in the OnShow or later.
2012-11-26More richtext color tag improvements.Michael van Canneyt
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.
2012-11-26RichTextView syntax tag improvementsMichael van Canneyt
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.
2012-11-22Improves the text formating of the readme file.Graeme Geldenhuys
2012-11-22Fixes the description of the <rightmargin> tag.Graeme Geldenhuys
2012-11-22Fixes line ending issuesGraeme Geldenhuys
2012-11-21Adds a small stand-alone test app for the RichTextView component.Graeme Geldenhuys
2012-11-21Removed outdated code comment.Graeme Geldenhuys
2012-11-21richtextview - documentation in readme file is updated.Graeme Geldenhuys
2012-11-21richtext:: Incorrect "normal font" was assigned as default style.Graeme Geldenhuys
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.
2012-10-23richview: Removed the extra margin for text at the top and bottom of the ↵Graeme Geldenhuys
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().
2012-10-23richview: Implements a new BorderStyle propertyGraeme Geldenhuys
* 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
2012-08-28RichTextView: scrollbar width is now set to the standard size of 16pxGraeme Geldenhuys
2012-08-21docview: fixes a memory leak in font handling.Graeme Geldenhuys
We checked for the same fontdesc, but never for the same instance. So the NewFont instance might not have been freed, causing the memory leak.
2011-08-29richview: fixed another memory leak.Graeme Geldenhuys
2011-08-29richview: removed DoAllocateWindowHandle() which caused a memory leak.Graeme Geldenhuys
The above mentioned method called CreateWnd() twice, thus causing a memory leak. Now CreateWnd() is simply called once in the constructor.
2011-08-29richview: neatened up the CreateDefaultMenu() method.Graeme Geldenhuys
The code is more human readable now.
2011-08-29richview: making sure we tidy up everything.Graeme Geldenhuys
2011-08-29richview: fixed memory leak with font resources.Graeme Geldenhuys
2011-08-24richview: stop a possible index out of bounds error when there is no text.Graeme Geldenhuys
2011-08-17richview syntax and information file renamed so it is easier to spotGraeme Geldenhuys
2011-08-17richview: to prevent "index out of bounds" errors while RV is empty.Graeme Geldenhuys
2011-08-16richview: extra check to make sure LineIndex is in range.Graeme Geldenhuys
This shoud prevent the 'Index out of bounds' errors.
2011-08-12Removed hard-coded Code Generation option in lazarus package.Graeme Geldenhuys
2011-08-11richview: improved the scrollbar textwidth and SB max value calculations.Graeme Geldenhuys
This helps those odd borderline cases, so now the scrollbar always seems appropriate when it is visible.
2011-08-11RichView: Correctly calculate the HScrollBar Max value.Graeme Geldenhuys
Now that we correctly the FLayout.Width value this change could now be made.
2011-08-11richview: ExtractNextTextElement() changed to support UTF-8 charactersGraeme Geldenhuys
- 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.
2011-08-11richview: we should be looking at SB Width or Height propertyGraeme Geldenhuys
instead we should be looking at the overall FScrollBarWidth field value which defines the Width or Height of all Scrollbars in RichView.
2011-08-11richview: correct the localion where we call to update scrollbar coords.Graeme Geldenhuys
2011-08-11minor code formatting, improved code commentsGraeme Geldenhuys
2011-08-11richview: fixes the painting bug of bottom/right corner rectangleGraeme Geldenhuys
Refactored the code, so we only use UpdateScrollBarCoords() method.
2011-08-11corrected the bottom/right corner color for RichView.Graeme Geldenhuys
It's the rectangle between the two scrollbars.
2011-08-11add and remove commentsGraeme Geldenhuys
- added a unit header comment - removed old code comments not needed any more - removed old debug lines
2011-08-08richview: minor refactoring of code and fixing of one memory leak.Graeme Geldenhuys
2011-08-08bug: forgot to check in this change. Item[] -> Items[]Graeme Geldenhuys
A recent commit forced this change so it is consistent with fpGUI and RTL usage of array property.
2011-07-24docview: adjusted Margin Size Style to Avg Char Width.Graeme Geldenhuys
This gives an overall improved margin size. In future we should make this user selectable in Docview's Preferences dialog.
2011-07-24docview: various RichTextStyleUnit fixesGraeme Geldenhuys
- Rename Settings parameter to ASettings. This is to prevent possible confusion with the Settings global variable. - ApplyStyleTag had many issues, applying the style changes to the wrong properties. Manyly, styling was applied to the ASettings parameter when they should have been applied to the Style parameter. - Code formatting improvements.