World window sizes

Regarding bug #395 - Input window sizes identical between different worlds
http://www.gammon.com.au/scripts/showbug.php?bugid=395&productid=0

Could MUclient save it's window and input sizes inside the world file instead of the registry? Every time I open the registry to edit some MUclient options (usually just to remove certain worlds from the recent file list), I really don't like seeing all those entries for window sizes and positions. It seems excessive...

The bonus to saving the sizes and positions inside the world file would be that the world would look the exact same way when copied to a different computer, without the need to export then import registry settings. Having to export/import means the registry file has to be edited to remove unwanted keys or alter other keys. The con would be different screen resolutions. MUclient would have to automatically resize the world size if it exceeded the screen resolution on the new computer when the world was first opened.

Just a thought...

Yes, this is the plan. It is excessive. However in my mitigation I suggest that if the window placement is stored in the world file, then after playing a world, and maybe moving the window a pixel, you would be asked "do you want to save changes?" and you would think "what changes?".

I see how that could be confusing to many people. Maybe the window sizes could always be saved, or perhaps an additional save question that asks "Do you want to save the window sizes?" which only pops up if world details are not saved.

By the latter I mean if the world is always saved, there is no question. If the world is not automatically saved, and there is something to save, such as a new trigger or variable, only one save question is posed (the existing one). If there is no automatic save and no new triggers, variables or whatever to save, then a world sizes question is posed.

$0.02... :)

I see where you are coming from, but say you had made some changes (eg. to triggers, aliases) which didn't work, and you resolve to *not* save the world.

However, earlier on, you moved it. Then by not saving it you then grumble that the world position has not been remembered.

Move, save, change alias, don't save, same as any other change :p