[Pharo-project] Handle Close Event in Image - necessary for 1.0?
stephane.ducasse at inria.fr
Wed Apr 7 16:47:16 EDT 2010
On Apr 7, 2010, at 5:54 PM, Henrik Johansen wrote:
> On Apr 7, 2010, at 12:38 25PM, Stéphane Ducasse wrote:
>> Thanks Henrik
>> this is something I understand. I will integrate that for 1.1
> Yes, there's some new stuff there which won't work well if we ever move towards multi-window support, but the entire event-handling will have to be rewritten in that case anyways, so I didn't think too much of it.
> I'd say the first step in any case would be moving Event-object generation out of the HandMorph class... (did MVC make its own kind of events?)
> Probably a good idea to switch to something reacting to new events in the queue rather than polling it too, if we intend to ever switch the inputEventPollingFetcher for the actual InputEventFetcher some time in the future.
Yes I think that we should move to not use a polling of event.
> Though, InputEventSensor installEventSensorFramework seems borken on Windows now (eventbuffer overflows with 4.0.2 VM ), and incredibly slow to signal semaphore (albeit not loosing any events anymore in 1.1) on a Mac 4.2.4 VM. On the 5.X series, it works like a dream though :D
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
More information about the Pharo-dev