On 5/24/06, John Labenski <[EMAIL PROTECTED]> wrote:
On 5/24/06, Leandro Motta Barros <[EMAIL PROTECTED]> wrote:
It is strange that it used to work and now doesn't, but in any case I
think it's fixed. Previously the two parameter call to ConnectEvent
tried to get the wxWindowID of the event object, but this is not how
wxEvtHandler::Connect works, it just uses wxID_ANY. I have changed the
code to reflect this, hopefully it won't break other things, but it's
"correct" now.
To fix your problem, simply use -1 or wxID_ANY as the first parameter
until the next snapshot.
Thanks! I'll try this tomorrow, if have time.
ps. using Idle events w/ RequestMore() like this is pretty ugly, try
to see if you can find a better way to implement this...
Sure! In my "real code" I'm using idle events to resume the execution
of a coroutine that does some tasks "in the background", and I just
RequestMore() as long as these tasks are not completed. In practice, I
just get a limited number of idle events, not a continuous and
inifinite stream as in this example. So, perhaps my use of idle events
isn't exactly beautiful, but at least is not *that* ugly (or so I
think) ;-)
And thank you once more!
LMB
Ym�杽��j������Ljv�y���ا�h��������Z��b�An�\����y�^r�r&��8^�(!z�g�fޮ��y�ڵǫ�'�q�b�{"��^��-�x"�۬���jv��ƥJ�i��B�'$��^j�梷����ǥjˬ}�dj
� �ɝ
