[Pharo-project] addToStartUpList and World extent
Hello Pharoers, I am using "Smalltalk addToStartUpList: self" to register DrGeo in the startup sequence, so a new drgeo window is instantiated fullscreen automatically if none exist. However I have noted, at least on iPad and Android, that the instantiated window is not set to the correct fullscreen extent (it is smaller). DrGeo Window instantiated later from user request are correctly set fullscreen. Could it be that World, at the startUp sequence time, does not know yet the screen extent? Should I use another kind of startup sequence Thanks Hilaire -- Dr. Geo -- http://www.drgeo.eu
I am tempted to use #addDeferredStartupAction: instead, but it is not clear yet. If anyone has some experience to share about that I take it. Hilaire Le 28/01/2012 22:01, Hilaire Fernandes a écrit :
Hello Pharoers,
I am using "Smalltalk addToStartUpList: self" to register DrGeo in the startup sequence, so a new drgeo window is instantiated fullscreen automatically if none exist. However I have noted, at least on iPad and Android, that the instantiated window is not set to the correct fullscreen extent (it is smaller). DrGeo Window instantiated later from user request are correctly set fullscreen.
Could it be that World, at the startUp sequence time, does not know yet the screen extent? Should I use another kind of startup sequence
Thanks
Hilaire
-- Dr. Geo -- http://www.drgeo.eu
This is strange. Did you look at the startup sequence? On Jan 28, 2012, at 10:01 PM, Hilaire Fernandes wrote:
Hello Pharoers,
I am using "Smalltalk addToStartUpList: self" to register DrGeo in the startup sequence, so a new drgeo window is instantiated fullscreen automatically if none exist. However I have noted, at least on iPad and Android, that the instantiated window is not set to the correct fullscreen extent (it is smaller). DrGeo Window instantiated later from user request are correctly set fullscreen.
Could it be that World, at the startUp sequence time, does not know yet the screen extent? Should I use another kind of startup sequence
Thanks
Hilaire
-- Dr. Geo -- http://www.drgeo.eu
The scenario looks like the following: - image is save with main window at an arbitrary extent - image is load in a different system with the different screen extent, the main window is automatically set to this screen extent - #startUp class registered messages are sent - World is set to the screen extent Indeed there is a DisplayScreen class>startUp setting the Display extent to the actual screen extent. Looks like addToStartUpList: aClass after: predecessor will be handy. Hilaire Le 28/01/2012 22:28, Stéphane Ducasse a écrit :
This is strange. Did you look at the startup sequence?
On Jan 28, 2012, at 10:01 PM, Hilaire Fernandes wrote:
Hello Pharoers,
I am using "Smalltalk addToStartUpList: self" to register DrGeo in the startup sequence, so a new drgeo window is instantiated fullscreen automatically if none exist. However I have noted, at least on iPad and Android, that the instantiated window is not set to the correct fullscreen extent (it is smaller). DrGeo Window instantiated later from user request are correctly set fullscreen.
Could it be that World, at the startUp sequence time, does not know yet the screen extent? Should I use another kind of startup sequence
Thanks
Hilaire
-- Dr. Geo -- http://www.drgeo.eu
-- Dr. Geo -- http://www.drgeo.eu
participants (2)
-
Hilaire Fernandes -
Stéphane Ducasse