Updates:
Status: WontFix
Comment #3 on issue 36 by benoit.m...@gmail.com: Problem between Process
and DrawingArea
http://code.google.com/p/gambas/issues/detail?id=36
That's it!
By using DrawingArea.Clear() inside the Draw event handler, you are
actually calling it again and again. In gb.gtk+, the event loop only raises
these events, and does not have the time to call the other events,
especially Process_Read and Process_Kill.
Don't call DrawingArea.Clear() inside the Draw event handler, it does not
do what you want. Use Draw.Clear() instead.
I will check why gb.gtk+ event loop cannot raise other events in that case.
DrawingArea.Clear() will not call Refresh() anymore. That method is only
useful when the DrawingArea is cached.
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Gambas-user mailing list
Gambas-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gambas-user
