On 4 May 2011 17:04, Gary Chambers <[email protected]> wrote: > Of course, now, we get no warning of being unable to write to the changes > file... > (e.g. when starting a second invocation of Pharo...) >
which is never shown properly , because it was "shown" before morphic initialized. To fix that, it should use #addDeferredUIMessage: to inform user, when UI is ready to work after startup is complete. But apparently not in the middle of startup, when you cannot clearly tell, if its already safe to make any calls to morphic or not.. > Regards, Gary > > ----- Original Message ----- From: "Igor Stasenko" <[email protected]> > To: <[email protected]> > Sent: Tuesday, May 03, 2011 2:52 AM > Subject: Re: [Pharo-project] PharoCore 1.3 built stalled > > > On 3 May 2011 00:49, Stéphane Ducasse <[email protected]> wrote: >> >> it is my fault but I have no idea how to solve it. >> A package was loading over an already existing one and you get a pop up. >> > > i have a fix for it. > See #4075 > > it makes sure that no matter what current UI manager you using > (running image headless or not) > a system startup (all classes startup) is _always_ performed using > non-interactive UI manager. > > So, since CommandLine file-in scripts during startup, this will make > sure that it will run non-interactively. > > >> Stef >> >> On May 2, 2011, at 11:39 PM, Igor Stasenko wrote: >> >>> On 2 May 2011 23:26, Igor Stasenko <[email protected]> wrote: >>>> >>>> On 2 May 2011 23:13, laurent laffont <[email protected]> wrote: >>>>> >>>>> Last built started more than 1 day ago and not finished .... >>>>> Laurent. >>>> >>>> This is not good. I killed the jobs. Lets see if it will repeat again. >>>> >>> >>> Okay the problem is that there is a warning and it is handled by >>> MorphicUIManager, >>> instead of NonInteractiveUIManager which just forcing it to always >>> proceed, while morphic one >>> expects user to press proceed or abandon. >>> >>> So, the problem is with an update of >>> progressTitle: 'Loading 13179-Pha-PlentyOfCleans...' >>> >>> >>> But i don't undestand why it not switched to NonInteractiveUIManager >>> at image startup. >>> Aha.. i guess i know why. >>> Is its not because command line stuff that are triggered at image >>> startup, which tries to evaluate some code >>> before full startup procedure completes? >>> >>> A command line , i think should be changed to start loading external >>> code only after >>> everything else is started (including UI manager). >>> Otherwise we will have problems like that. >>> >>>> -- >>>> Best regards, >>>> Igor Stasenko AKA sig. >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > > -- Best regards, Igor Stasenko AKA sig.
