| | [ Return to Bugs & Features | Roadmap 2.0 | Post Text | Post File ]
STR #1838
| Application: | FLTK Library |
|---|
| Status: | 5 - New |
|---|
| Priority: | 1 - Request for Enhancement, e.g. asking for a feature |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | Unassigned |
|---|
| Summary: | Bad Documentation |
|---|
| Version: | 2.0-feature |
|---|
| Created By: | Jonathan |
|---|
| Assigned To: | Unassigned |
|---|
| Fix Version: | Unassigned |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
[ Post File ]No files
Trouble Report Comments:
[ Post Text ]
| |
| #1 | Jonathan
03:15 Nov 30, 2007 |
| I think the documentation should realy be improved. The Documentation in the weekly snapshot of 2.x is not the same than the online documentation and both have seriously leaks.
For example: "The return value is value() of the window, which is true only if some callback does window->set(). To use this, make an OK button with a callback that does this."
This part of Window::exec() is missing in the online documentation (why??). Also a description of window->set() ist totaly missing in both. I used it, and it works, but i really want to know, why.
A good documentation with more examples would make the life with fltk much easier. The best features are only usefull, if someone knows, how to use them. All of the guys, that just want to make a littel tool with fltk have to learn it far to long.
Please make a better documentation. I would help with, if you want, because i think its realy realy necessary. (I am thinking about some kind of: "How to make a simple Dialog", and other usefull how-tos.)
(sorry for all my mistakes, i am german) | |
[ Return to Bugs & Features | Post Text | Post File ]
|
| |
FLTK Apps 
