| [ Return to Bugs & Features | Roadmap 1.1 | SVN ⇄ GIT ]
STR #94
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: | fl_draw()'s docs are in error |
Version: | 1.1.3 |
Created By: | greg.ercolano |
Assigned To: | mike |
Fix Version: | 1.1-current |
Update Notification: | |
Trouble Report Files:
No files
Trouble Report Comments:
|
#1 | greg.ercolano 13:02 Jun 22, 2003 |
| In the html file:
fltk/documentation/drawing.html#text
One error, and one omission:
1) The docs for fl_draw(s,x,y) indicate x+y are floats, but are actually ints.
2) The docs for fl_draw(s,x,y,w,h,..) should indicate what the w/h values are for.. clipping? image positioning? | |
|
#2 | greg.ercolano 13:17 Jun 22, 2003 |
| PPS. the docs for fl_draw(s,n,x,y) should probably indicate that it does /not/ draw symbols, since it appears to call the platform specific drawing routines directly. | |
|
#3 | greg.ercolano 16:52 Jun 23, 2003 |
| One other addition; as described in fltk.general on 06/22/03-06/23/03:
The docs for fl_draw(s,x,y) should indicate it draws text /above/ the x/y origin, and fl_draw(s,x,y,w,h..) draws /below/ the x/y origin.
Maybe a warning that if you try to mix the two functions, a Y offset of the font's height must be specified to make them print in the same vertical position.
| |
|
#4 | greg.ercolano 11:47 Jun 24, 2003 |
| Also, the 1024 character limit should be documented for the bounding version of fl_draw(), and a note that the non-bounding fl_draw() does *not* have this limit. | |
|
#5 | matt 22:10 Jul 17, 2003 |
| Updated documentation in CVS.
Matthias | |
[ Return to Bugs & Features ]
|
| |