summaryrefslogtreecommitdiff
path: root/docview/components/richtext
AgeCommit message (Collapse)Author
2010-08-11RichTextView: Minor method parameter refactoring.Graeme Geldenhuys
To reduce in possible confusion - with Images property found in some other classes.
2010-08-06docview: Correctly pass in the text area height to DrawTextGraeme Geldenhuys
2010-08-06docview: Code cleanup, removing already commented code.Graeme Geldenhuys
2010-08-06docview: We don't have Line.MaxDescender set, so no need to use it.Graeme Geldenhuys
2010-08-06docview: Fixed mono font screwup when scrolling large tables.Graeme Geldenhuys
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!
2010-08-06docview: Removed the check for FontType = ftOutline.Graeme Geldenhuys
We always use outline fonts in fpGUI.
2010-08-05RichTextView: Improved the scrollbar PageSize and SliderSize based on ↵Graeme Geldenhuys
content displayed.
2010-08-05RichTextView: fixed the scrolling direction when PgUp or PgDn is pressed.Graeme Geldenhuys
2010-08-05DocView: clicking on scrolled pages did not detect hyperlinks.Graeme Geldenhuys
This was a bug, where I didn't apply the scroll offset correctly. for the Y-axis.
2010-03-11fixes compilation for docview and fpc 2.5.1Andrew
Not sure when it became the case but it makes sense that var parameters must use the exact type and not a descendant class. This patch puts that into effect.
2010-03-09docview: renamed local variables to reduce future confusion.Graeme Geldenhuys
We don't want to confuse properties and local variables, so the latter gets a different style: normally prefixed with the letter 'l'.
2010-03-09When debugging with GDB these lines sometimes gives FPC AnsiString errors.Graeme Geldenhuys
No idea why!! So we comment them simply because they are debug lines to start with.
2010-02-24docview: Give a more accurate draw width to TRichTextLayout.Graeme Geldenhuys
This still contains one issue. We need to ask TRichTextLayout to calculate lines and word wrapping, giving the maximum text width available. Well, if text wrapping occurs and the text is long enough to require scrolling, we suddenly need to take the scrollbar width into account for word wrapping!! A chicken and egg situation. :-( This needs to be fixed somehow!! Signed-off-by: Graeme Geldenhuys <graemeg@gmail.com>
2010-02-24docview: GetTextAreaWidth already includes ScrollbarWidth in the calculation.Graeme Geldenhuys
2010-02-24docview: GetTextAreaWidth implementation fixGraeme Geldenhuys
Also some minor code formatting changes.
2010-02-24docview: code formatting changes.Graeme Geldenhuys
2010-02-24docview: This drastically improved text width calculations.Graeme Geldenhuys
Due to this change the text wrapping has also improved a lot. Still not 100% but much better than before.
2010-02-24docview: Lets not hardcode the Arial font.Graeme Geldenhuys
2010-02-23docview: content doesn't disappear as soon as it reaches the top/bottom edgeGraeme Geldenhuys
lines at top and bottom of richview component are now painted even if they are only partially visible. They don't suddenly disappear any more.
2010-02-11Fix compiler waring about unreachable code.Graeme Geldenhuys
2010-02-11Fix visibility problem with constructor and destructor.Graeme Geldenhuys
2009-11-27Quick summary documentation for RichTextView.Graeme Geldenhuys
2009-11-27Merged separate DocView project as our subdirectoryGraeme Geldenhuys