When I've been using MUSHclient, since time immemorial, I've been having a continual problem. I'd resize the windows, then maximize them to the client window again, and it'd suddenly start minimizing a world not in use, whenever it was clicked to restore. This in itself isn't a problem, but the problem is, it maximizes from minimized still, when its SUPPOSED to have them all maximized, taking a second to expand with its green world bar visibly moving out and up. Now do I fix that problem? I've tried restoring it to non-maximized size and saving world details, multiple times. But it always does it till I crash out mushclient and reopen. And sometimes after, if I've saved a world since. It's getting ANNOYING.
Addendum:
It only seems to happen after initial time, if I've flipped windows to something else, then flipped back a time or two. Then it restores/responds that way, from then on. I really am sick of trying to re-make worlds, from it saving like that and getting 'stuck'.... But it bothers my eyes when it does it.
I'm not even sure of the /exact/ steps of it happening, but I can say this, for certain, in relation to the last time. mushclient itself wasn't in full screen, but the world windows were full screened in the mushclient window. Instead of resizing them, at one point, I clicked minimize for the one that became the problem, causing the restore and minimization. After doing that, fearing it would cause exactly what I described, I restored it, it wanted to restore to full screen from minimize after, but clicking restore again from full screan made it 'normal' with the other windows. But the size settings wouldn't stay after it. After I saved it restored and maximized again, but after flipping back to check activity on another world, it visibly 'restored' from minimized, when it should have flipped over as a full screen already. Somehow, if a world has been minimized, it won't acknowledge it as full size when its supposed to be, rather changing to it in full size triggers restore every time, because the settings aren't saved once its been minimized, except to 'stay minimized when not the 'top' window'. It's in Windows 98.
Okay, after just having it happen again, I have a better idea. I was moving to minimize the MUSHclient window completely, from a less than full screen size. By accident, I clicked minimize for current world, world 1. (just underneath main minimize). After realizing the error, I re-maximized world 1 into the mushclient window, and switched to world 2. When I switched back to world 1, the bug I posted about popped right up.
You don't happen to have multiple worlds with the same world name do you (not the file name but the name that appears in the title bar of the window)?
The window position is stored in the Registry, under the name of the world's name. This is done so that you don't need to save the world file just because you move it around on the screen.
The key will be something like this:
HKEY_CURRENT_USER\Software\Gammon Software Solutions\MUSHclient\XXXXXXX World Position
Where XXXXXXX is the world name.
You could use RegEdit to delete that particular key (there will be 10 items under it, starting with the letters "wp.", such as "wp.bottom").
However if you are not comfortable with the use of RegEdit you should not do this, as misusing RegEdit can cause your system to become un-bootable, leading to the need to re-install Windows.
I don't have any 'exact' same world names, no, but I have multiple world windows to some places, which have the basic place name, then the char name, as their listing. The trick is, it didn't always /happen/ with the similarly named worlds, the one I reported yesterday when I caught the exact error in fact has a totally unique name to it. There are spaces between the like stuff and the different stuff, though... I'll try deleting that key, and see how it works.
I've encountered this problem as well. one quick fix i used was to get a copy of TweakUI (free from microsoft *gasp*), and disable "window animation". this means the window will still 'restore' itself, but you won't see it.