Cannot dismiss startup cartoon

[michaelkenward]

I decided to try MW201 on my laptop today.

Hilarious experience.

Start it. Thing goes through its unwelcome star up animation. Comes to end.

Unfortunately, it then refuses to let me check the box that says "Play a start up". The thing just freezes.

So, kill mw2010, start again.

Thing goes through its unwelcome star up animation. Comes to end.

Unfortunately, it then refuses to let me check the box that says "Play a start up". The thing just freezes.

So, how do I get to us MW2010?

[anniebrion]

You can do it manually: Help >>> User files >>> Startup.xml

Exit MWP then:-

And look for:

Code: Select all

<PlayAnimationOnStartup>True</PlayAnimationOnStartup>
<ShowPreviewSplashOnStartup>True</ShowPreviewSplashOnStartup>

Change to:

Code: Select all

<PlayAnimationOnStartup>False</PlayAnimationOnStartup>
<ShowPreviewSplashOnStartup>False</ShowPreviewSplashOnStartup>

[michaelkenward]

Thanks.

No "/" switch?

[anniebrion]

Nope, the only switch is -nosplash

I'm sure the programmers will fix your fault eventually but I don't think it is that critical as there is a work-a-round for now

[rusticdog]

If you press ESC does that close the animation.

We've just made another fix where we think where the startup animation and trial reminder notice might conflict, which may be the cause too.

[michaelkenward]

If you press ESC does that close the animation.

We've just made another fix where we think where the startup animation and trial reminder notice might conflict, which may be the cause too.

ESC didn't help.

I think the conflict was it.

Alt+Tab showed a hidden window that simply would not come into focus.

Nor could I grab the window that was up front.

In the event, I installed a newer version of MW2010. (I thought I had done that already, following an error report from Windows.) That brought the "Trial" window to the front.

I was not able to do all of these when the issue first hit me. I was on the road away from the usual tools.

[rusticdog]

OK great. All instances of this ought to be fixed with the next version, guess next week sometime.