Re: [Libsigcx-main] Signal Queue Length

[Andreas R. <a.r...@gm...>]

Roland Welker <ro...@mm...> writes:

> Fairly simple, one thread holds a GUI (i.e. is the complete user interface), 
> the other task(s) is(are) executing the "hard work". The plan was, that the 
> GUI is completly independend (and non blocking) of the functionality. The 
> problem is, that some calculations might take a longer time (non of the 
> current implemented one has this problem, but you never knwo:-)). 
> Furthermore, I want to avoid, that a user starts clicking around, if there 
> seems nothing to happen any more. 
> Conclution, after n signals have been queued, a simple message to the user, 
> informing him, that there are currently jobs processed, and giving him the 
> option to queue more, or wait till the queue is empty again.
>
OK, this seems reasonable. I'll add a method returning the number of
pending callbacks in the next release (and as soon as I've some time
in CVS). Of course I welcome patches ;-)

Regards, Andy
-- 
Andreas Rottmann         | Rotty@ICQ      | 118634484@ICQ | a.r...@gm...
http://www.8ung.at/rotty | GnuPG Key: http://www.8ung.at/rotty/gpg.asc
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62

This reality is really just a fucked-up dream -- Papa Roach