Issue 4152 in pharo: CodeUpdate>>startUp using UIManager

Status: Accepted
Owner: [hidden email]

New issue 4152 by [hidden email]: CodeUpdate>>startUp using UIManager
http://code.google.com/p/pharo/issues/detail?id=4152


At image startup phase there should be no any attempts to use UI
before startup has finished and all classes are finished doing start up.

A CodeUpdate, if turned on, violating this rule. And it will definitely
hang the image in headless mode,
because UIManager switched to be non-interactive after all classes startup.


Now i wonder, if it would be better to switch to non-interactive ui manager  
before saving an image.. and restore it back to Morphic on at startup.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #1 on issue 4152 by [hidden email]: CodeUpdate>>startUp using  
UIManager
http://code.google.com/p/pharo/issues/detail?id=4152

is issue 4075
(http://code.google.com/p/pharo/issues/detail?id=4075)
a duplicate of this issue?





_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #2 on issue 4152 by [hidden email]: CodeUpdate>>startUp using  
UIManager
http://code.google.com/p/pharo/issues/detail?id=4152

no, this is not related to running a scripts from command line.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Duplicate
        Mergedinto: 4248

Comment #3 on issue 4152 by [hidden email]: CodeUpdate>>startUp  
using UIManager
http://code.google.com/p/pharo/issues/detail?id=4152

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker