Il 13/01/2014 2.25, Igor Stasenko ha scritto:

On 13 January 2014 00:08, paolo.bernardi.67@gmail.com <mailto:paolo.bernardi.67@gmail.com> <paolo.bernardi.67@gmail.com <mailto:paolo.bernardi.67@gmail.com>> wrote:

�� �� Il 12/01/2014 19.41, Igor Stasenko ha scritto:

�� �� �� �� All i can say that callbacks for handling window events need
�� �� �� �� special handling:
�� �� �� �� ��- you basically should prevent VM to do event handling during
�� �� �� �� handling of event by callback.


�� �� Do I achieve that when starting in headless mode?
�� �� (no ui, no messages...)

nope. VM will still run event loop (in ioProcessEvents) and do more or less the same things.
that is another reason, btw to bring event loop handling to image level.

--
Best regards,
Igor Stasenko.

Could I prevent VM (as you say, Igor) do process events
using primitiveEventProcessingControl?

I tried hacking
NBFFICallback >> pvtEnter:stackPointer:primitiveMethod:

by disabling events before block execution
and enabling them after callback termination.

Pharo still works for a while, then crashes.