Actually it's Michael who is messing in this area to improve the event
handler for Pharo (and in general) as part of some funding from ESUG
for the iPhone VM development work.
Me? I'm just an innocent bystander. I'd assume he has to fork off any
logic with low io process priority which is what I think happens if
you follow the bouncing ball by reviewing what
installInterruptWatcher and handleUserInterrupt do. The key
consideration is that fetchMoreEvents is the trigger, not the code in
the VM.
On 20-Nov-08, at 10:58 AM, Andreas Raab wrote:
Hi John -
The reasoning sounds about right but you have to be *very* careful
when making changes to that logic. As a simple example,
fetchMoreEvents is not only called from the event tickler and
consequently the interrupt handler might be forked at the priority
of some random process using "Sensor anyButtonPressed" ;-) If I
remember correctly, there were several other gotchas in this area (I
tried changing some of this stuff in Croquet once) and since this is
a place where screwing up will make a lot of people *very* unhappy I
would advise extreme caution when making these changes.
Cheers,
- Andreas
--
=
=
=
========================================================================
John M. McIntosh <[EMAIL PROTECTED]>
Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com
=
=
=
========================================================================
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
