> In FLTK 1.1.7, the API documentation has left me a little confused. > > It says that Fl::awake() will enqueue a message that can be > read from Fl::thread_message(). > > But then the documentation says: "The default message handler > saves the last message which can be accessed using the > Fl::thread_message() function." > > That makes it sound like I can only access the message that > was most-recently enqueued using Fl::awake(), and that > messages enqueued earlier but not yet read are rendered > inaccessible. E.g., the documentation makes it sound like > awake()/thread_message() are used to access a mailbox, not a queue. > > How is one supposed to actually use awake()/thread_message() > as a queue data structure rather than as a mailbox?
A lot of this has been enhanced in later variants, and the 1.1.7 version is "outdated" now. I honestly thnk you would get some benefit from moving to 1.1.9, or the 1.1.10 svn (despite your earlier reservations) as I do believe this mechanism has been improved. I was going to say that Matt would know more about this, but I see he has posted a reply also... Cheers, -- Ian SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
