**
**
** Please stop posting to this list. It is for internal use only as we stated
many times.
** Please use fltk.general instead.
** This is the last reply that I send to your mails in "bugs".
**
** You have been told.
**
** I assume you are just high on life.
**
**
On 01.04.2010, at 22:52, rainbowsally wrote:
> 1. Text->append("string");
>
> How many times have you needed to append text to the end of a Text_Display or
> a Text_Edit widget?
>
> In Fl_Text_Display.H
>
> void insert(const char* text); // <-previous existing line in the file
> void append(const char* text); // <-rs add
The text in a Text Display is handled via Fl_Text_Buffer. This is great,
because two Text_Displays can share a singe Text_Buffer. Fl_Text_Buffer already
has insert() and append().
> insert_position(0x7FFFFFFF); // insert at end (32-bits max positive integer)
FLTK code is always written to work in 32 and 64 bit. We don't support 16 bit.
64k of RAM is just rediciously small.
> 2. msg_dispatch(Fl_Widget* receiver, uint msgID, uint nParams, ...);
We don't dispatch anything beyond user interface related data. If you need to
transport large amounts of data, simply call the receiver in your destination
widget directly.
- Matthias
_______________________________________________
fltk-bugs mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-bugs
