Skip to content

Commit

Permalink
STR 1306: udated documentation to reflect limitation in Fl::delete_wi…
Browse files Browse the repository at this point in the history
…dget(). For a different bug, I was forced to implement an automated widget deletion system which seems to work well. I would like to reuse that for all cases that depend on 'delete_widget', making 'delete_widget' obsolete. I will change the STR accordingly.

git-svn-id: file:///fltk/svn/fltk/branches/branch-1.1@5195 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
  • Loading branch information
Matthias Melcher committed Jun 14, 2006
1 parent a0cbcf3 commit fee47db
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 3 deletions.
2 changes: 2 additions & 0 deletions CHANGES
@@ -1,5 +1,7 @@
CHANGES IN FLTK 1.1.8

- Updated documentation to reflect limitation of
Fl::delete_widget() (STR #1306)
- Fixed line wrapping in Fl_Text_Display (STR #1227)
- New function Fl::event_original_key() returns key
code before NumLock handling.
Expand Down
11 changes: 8 additions & 3 deletions documentation/Fl.html
Expand Up @@ -501,9 +501,14 @@ <H4><A NAME="Fl.default_atclose">void default_atclose(Fl_Window*,void*);</A></H4

<H4><A NAME="Fl.delete_widget">void delete_widget(Fl_Widget*);</A></H4>

<p>Schedules a widget for deletion when it is safe to do so. Use
this method to delete a widget inside a callback function. When
deleting groups or windows, you must only delete the group or
<p>Schedules a widget for deletion at the next call to the event loop.
Use this method to delete a widget inside a callback function.
To avoid early deletion of widgets, this function
should be called toward the end of a callback and only after any call
to the event loop (<tt>Fl:wait()</tt>, <tt>Fl::flush()</tt>,
<tt>fl_ask()</tt>, etc).</p>

<p>When deleting groups or windows, you must only delete the group or
window widget and not the individual child widgets.</p>

<H4><A NAME="Fl.display">void display(const char*);</A></H4>
Expand Down

0 comments on commit fee47db

Please sign in to comment.