Race during startup posts incorrect window width/height?

In the moments during client start up, calls to GetInfo(280) and GetInfo(281) can apparently report the wrong numbers. I say wrong here because it looks like maybe the client window zooms to size but hasn't gotten to the desired size yet?

A user reported the following to me.



I have noticed this myself in the past as well, but didn't think to report it as a problem for some reason.

There are some race conditions there. Especially during initial startup the windows can be set to some default size (eg. chosen by the MFC library) before the code in MUSHclient has had a chance to read the saved window positions for that world and fix things up.

In particular, plugins are installed, and OnPluginInstall called, before the output window is set up.

I would suggest a short delay after the plugin starts up, if you need to know the output window size, that would give it a chance to stabilize.

Is this avoidable? It's not intuitive and will randomly screw up anyone who tries to get window geometry at plugin load.

See this post perhaps:




:P

I can't think of any particularly easy way, except maybe to defer loading plugins until somewhat later in the world-opening process.

Plugin loading is done as part of world (input) serialization, which is a part of opening a document. Basically we have all the XML data in memory, and are working through the various types of data (triggers, aliases etc.)

I'm not quite sure of the ramifications of attempting to defer the plugin part.

See? Randomly even to people who knew about it 2 years ago.