Ansariel Hiller
added a comment - 05/Dec/11, 04:59 PM +0100 This has already been addressed in FIRE-2881 . If the zoom level doesn't persist, try deleting the settings_per_account.xml file in the settings directory for that particular avatar.

Raymond Martinek
added a comment - 05/Dec/11, 05:19 PM +0100 a) That doesn't address the position and size issues.
b) I had that before and after clean installs, so a new settings_per_account.xml file had been generated.

Position and size are stored in that file. Try deleting the file. Map parameters are properly saved, so it is an issue on your end, most probably a per account issue. I had it myself that it worked for one account, but for another one not.

BTW: I do NOT mean settings_per_account.xml in the FS installation folder, but the individual file that is created per avatar!

Ansariel Hiller
added a comment - 05/Dec/11, 05:37 PM +0100 - edited Position and size are stored in that file. Try deleting the file. Map parameters are properly saved, so it is an issue on your end, most probably a per account issue. I had it myself that it worked for one account, but for another one not.
BTW: I do NOT mean settings_per_account.xml in the FS installation folder, but the individual file that is created per avatar!

Raymond Martinek
added a comment - 05/Dec/11, 06:48 PM +0100 » I do NOT mean settings_per_account.xml in the FS installation folder, but the individual file that is created per avatar!«
Which is inside the avatar folder inside the Firestorm folder which I manually delete for clean installs.

Ansariel Hiller
added a comment - 01/Jan/12, 06:10 PM +0100 - edited This really seems to be some weird issue in the shining version now. Although the debug setting is properly updated when the zoom level is changed, it is not written to the settings file on logout.
EDIT: The correct zoom factor is saved if it changed in the map that is part of the radar, but not in the minimap floater.

The scaling has been fixed in 24368 (http://hg.phoenixviewer.com/phoenix-firestorm-lgpl/rev/d46337c62208). For some strange reason, during logout the scale is set by the minimap in the radar before the value is saved. Changed the behavior of the minimaps to synchronize the scaling throughout all instances (minimap floater and radar panel), thus also the correct scale is saved during logout.

The size/position of the minimap floater is not affected by this, however. That values are persisted by the floater itself. Is that actually still an issue by now?

Ansariel Hiller
added a comment - 01/Jan/12, 09:29 PM +0100 The scaling has been fixed in 24368 ( http://hg.phoenixviewer.com/phoenix-firestorm-lgpl/rev/d46337c62208 ). For some strange reason, during logout the scale is set by the minimap in the radar before the value is saved. Changed the behavior of the minimaps to synchronize the scaling throughout all instances (minimap floater and radar panel), thus also the correct scale is saved during logout.
The size/position of the minimap floater is not affected by this, however. That values are persisted by the floater itself. Is that actually still an issue by now?

Raymond Martinek
added a comment - 20/Jan/12, 02:09 PM +0100 - edited No. For a few relogs it looked right, now all of a sudden it isn’t. And I didn’t crash before relog, I have just quit and logged back in.

Whirly Fizzle
added a comment - 05/Feb/12, 03:27 AM +0100 Proposed fix at 24855-sh ( http://hg.phoenixviewer.com/phoenix-firestorm-sh/rev/449d8145d161 )
Please thoughroughly test this fix on the next QA (it will be part of the smoketest).