> I find it very difficult to believe that 11 user events is
> enough to blow out the queue.
Believe it.
Instead, what you might want to do is the following:
* Add a private queue to hold your custom event data.
* Maintain a private boolean flag.
* When you want to post events for subsequent handling:
*** Post the custom event to your private queue.
*** If your private boolean is false:
****** Set it to true
****** Post a private event to the Palm OS queue
* When you pop that event off the Palm OS queue
*** Set your private boolean to false
*** Handle all the events you queued up in your private queue.
-- Keith
> -----Original Message-----
> From: Curtis Jackson [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 29, 2001 5:36 PM
> To: Palm Developer Forum
> Subject: event queue full after only 11 application events!
>
>
> I have an application that reads a message from a server and
> then acts upon
> that data by enqueuing a series of user events, each of which
> is an event
> of etype AWShuntEvent (typedef'd to firstUserEvent) with
> varying values
> stored in the EventType struct.
>
> The code that is enqueuing these events does so in a burst
> before returning
> back eventually to the event loop. The problem is, after
> enqueuing only 11
> of these user events, the system throws a fatal error
> claiming "event queue
> full". I have verified that there are no other events (system
> or otherwise)
> queued at the time.
>
> I find it very difficult to believe that 11 user events is
> enough to blow
> out the queue. Are there special queues for system events,
> and little or no
> space for user events?
>
> Curtis Jackson
> Director of Engineering
> Aniwhere, Inc.
> [EMAIL PROTECTED]
>
>
>
> --
> For information on using the Palm Developer Forums, or to
> unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
