Hi mike I read the code with emacs (without chekcing the differences) 1- Here I have a question =================== in this comment EventSensor = InputEventSensor? I found it confusing to me especially when you know a little to the previous architecture and the the new one. !InputEventSensor commentStamp: 'mir 8/14/2008 14:16' prior: 0! An InputEventSensor is xxxxxxxxx. EventSensor is a replacement for InputSensor based on a set of (optional) event primitives. An EventSensor updates its state when events are received so that all state based users of Sensor (e.g., Sensor keyboard, Sensor leftShiftDown, Sensor mouseButtons) will work exactly as before, by moving the current VM mechanisms into EventSensor itself. An optional input semaphore is part of the new design. 2- I saw a method defined on Controller But there are no reference to this class in pharo. So we could remove Controller I imagine 3- could you tell me what kind of code we would have to change? So that I can evaluate the task? On Nov 22, 2008, at 3:31 AM, Michael Rueger wrote:
Hi all,
finally got it. Turned out to be related to the host window/menu work, the window index slot needed to be set to 1 if 0. Sigh...
Attached is a change set that installs the new logic into a recent Pharo image. I'm not sure if and how we can get the install into a package load, but this version is for the adventurous types anyways :-)
A few remarks about the new sensor architecture (need to put this into the class comments).
First what's not changed, which is the morphic side. HandMorph still polls for nextEvent and also all old polling methods are still supported and heavily used in the image.
Basically the input event handling has been split into two parts: one event fetcher and event handlers.
The event fetcher fetches events from the even and currently still polls. Next step will be to get the input semaphore signaling working.
The event fetcher then signals the event to all registered event handlers. In the current version there are two: the new morphic sensor and the user interrupt handler.
Events currently are handled multiple times (rather their copies), we might need to change that later.
There needs to be some work done on how the user interrupt handler works, I had some problems with launching the debugger, but that might have been a problem in my development image. It would be helpful though, if the VM would provide information about the interrupted process as it does (or should do?) for the low space watcher.
So much for now, questions welcome and happy testing :-)
Michael <new-sensor-mir.cs.gz>_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project