| | [ Return to Bugs & Features | Roadmap 1.1 | SVN ⇄ GIT ]
STR #998
| Application: | FLTK Library |
|---|
| Status: | 1 - Closed w/Resolution |
|---|
| Priority: | 2 - Low, e.g. a documentation error or undocumented side-effect |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | Core Library |
|---|
| Summary: | HTML page for Fl_Input is garbled |
|---|
| Version: | 1.1-current |
|---|
| Created By: | a.rburgers.quicknet |
|---|
| Assigned To: | matt |
|---|
| Fix Version: | 1.1.7 (SVN: v4566) |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
No files
Trouble Report Comments:
| |
| #1 | matt
13:20 Aug 29, 2005 |
| Please give me some more information. Would that be on fltk.org? Which link? Or is that in any of the source code packages? What exactly is the garble? | |
| |
| #2 | a.rburgers.quicknet
14:40 Aug 29, 2005 |
| The problem occurs when browsing the documentation
within fluid. When opening the page in an HTML browser
it looks OK.
When moving to the documentation
for the Fl_Input class, the page displayed
is extremely high and wide. The text in
the Description section before the table is
displayed as one long line. The table is
not visible. | |
| |
| #3 | matt
15:02 Aug 30, 2005 |
| Thanks for the clarification.
The Fl_Help_View only interpretes a subset of HTML. In this particular case, it gets confused by the "center" attribute right before the "table" tag. This is not easy to fix and I don't know if I will get to this any time soon. It is unfortunate that our own HTML browser hickups at our documentation. | |
| |
| #4 | matt
01:48 Sep 13, 2005 |
| Fixed in Subversion repository.
The problem would occur if there was formatting inside a table. The next text block would be set to the formatting of the table member, not the table itself, or, even better, the parent block of the table.
This fix sets the x offset back to the left page border. While this fixes pretty much all pages in our documentation, this is obviously wrong for tables inside of tables. To fix this issue, we would have to introduce a full blown hierarchy of text blocks. This would blow the complexity of a simple help browser out of proportion. | |
[ Return to Bugs & Features ]
|
| |
