[Pharo-project] Issue 4003 in pharo: Build of Core 1.3 broken because of integration of 13147

pharo at googlecode.com pharo at googlecode.com
Wed Apr 13 16:17:39 CEST 2011


Comment #7 on issue 4003 by siguc... at gmail.com: Build of Core 1.3 broken  
because of integration of 13147
http://code.google.com/p/pharo/issues/detail?id=4003

here the part of code which responsible for doing startup:

	self processStartUpList: resuming.
	resuming
		ifTrue: [ self recordStartupStamp ].
	UIManager default onSnapshot: resuming.	"Now it's time to raise an error"

as you can see, the process list are ehmm.. processed before UIManager  
takes a control (and before switching to non-interactive mode).

It means that if any startup procedure added by some arbitrary class will  
fail with error, it will end up using old UIManager, which could open a  
debugger window and waiting for user's interaction.
 From other side, im not sure it would be wise to switch UIManager before  
processing the startup list, because it in own turn could depend on startup  
of things like Delay etc.





More information about the Pharo-project mailing list