| | [ Return to Bugs & Features | Post Text | Post File | Prev | Next ]
STR #3379
| 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: | Documentation |
|---|
| Summary: | General documentation improvements/elaborations |
|---|
| Version: | 1.4-feature |
|---|
| Created By: | greg.ercolano |
|---|
| Assigned To: | Unassigned |
|---|
| Fix Version: | Unassigned |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
[ Post File ]No files
Trouble Report Comments:
[ Post Text ]
| |
| #1 | greg.ercolano
12:44 Apr 21, 2017 |
| This may also apply to the 1.3.x docs (as some people are still using 1.3.
As per a few threads on fltk.general today (04/21/17):
> The "handling events" section of the docs should include
code examples, e.g. showing how to derive a class,
overload handle(), pass through the subclass's handle(),
and trap common events such as FOCUS, ENTER, and keyboard handling.
> Regarding off-screen drawing and Fl_Image_Surface,
Chris recommends:
"""
There could be more (dedicated) examples and perhaps
the documentation about "offscreen drawing" could also mention
the new possibilities of Fl_Image_Surface.
""" | |
[ Return to Bugs & Features | Post Text | Post File ]
|
| |
FLTK Apps 
