Re: [Chicken-users] Chicken and GUI programming

[db05]

Check how many times your application call
GetMessage&DispatchMessage.
Faster message delivery give better responsibility.
If u see "Not responding..." caption in the process explorer thats mean 
your application didn't pump messages about 5 seconds or longer.
Also check srfi-18 theards usage, properly placed thread-yield or
thread-wait-for-i/o can help alot.


07/26/13 21:19:57, Michele La Monaca <address@hidden>:
> Hi,
>
> I am investigating the feasibility and the opportunity to write
> (basic) Win32 GUI apps using Chicken. So far I think I've obtained
> good results leveraging Christian Kellermann's nice technique to
> handle callbacks
> (http://pestilenz.org/~ckeen/blog/posts/callbacks.html)*.  I am able
> to create windows, add widgets, react to events and so on.
> Unfortunately I've stumbled upon a problem I am not able to overcome.
> When the app engages in long running operations, the (scheme)
> procedure in charge of handling GUI's events starves, with the net
> effect that the app seems to freeze.
>
> So my question is: it's just me not properly using Chicken's
> "cooperative" threads (which might be well the case since I am not
> accustomed to those), or I've hit an intrinsic limit of Chicken being
> single threaded (in the pthread sense of "concurrent" threads)?
>
> Ciao,
> Michele
>
> * I think there are a few errors in the example.
>
> _______________________________________________
> Chicken-users mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/chicken-users