There is no reason to setup event fetcher, if there is nobody to
consume events (like Morphic) in image.
I would
1. remove event fetcher registration from startup list
2. change
MorphicUIManager>>onSnapshot: resuming
"The resuming argument is true when image boots from disk,
and false, if user just did an image snapshot."
"if we resuming, check if we're still interactive "
resuming ifTrue: [
Smalltalk isInteractive ifFalse: [
^ self nonInteractiveManager onSnapshot: resuming ].
Smalltalk isHeadless ifTrue: [
^ self headlessManager onSnapshot: resuming ]].
+++ InputEventFetcher startup.
SystemWindow wakeUpTopWindowUponStartup
---------------
then we no need to guess where to put Sensor in startup sequence,
because it will start up in right place, right before the guy who
going to consume events.
Starting it up before this place makes little sense anyways - no
events will be handled.
Shutdown then can be thrown out..
As a bonus, there will be no pointless shutdown/startup when you saving image.
On 25 May 2012 15:40, Guillermo Polito <[email protected]> wrote:
> Does InputEventFetcher really depend on Cursor & Form to install/uninstall
> the event fetch process?
>
> install
> "InputEventFetcher install"
>
> Smalltalk addToStartUpList: self after: Cursor.
> Smalltalk addToShutDownList: self after: Form.
>
> Default := self new.
> Default startUp
>
>
> Guille
--
Best regards,
Igor Stasenko.
