Winamp 5.8b - Forgets previous window position w/ Modern Skin

[justtesting]

Hi, I'm having a problem with the latest 5.8 3660 beta:

When using the Modern Skin (Winamp 3 UI style) after closing the program and opening it again, the player window and playlist window won't retain the previous position. This doesn't happen with the Classic Skin, on which the previous position is restored.
This is under W10 1809 17763.107, previous Winamp 5.666 is free from this issue.
Thanks for looking into it.

[PeterK.]

Hi, I'm having a problem with the latest 5.8 3660 beta:

When using the Modern Skin (Winamp 3 UI style) after closing the program and opening it again, the player window and playlist window won't retain the previous position. This doesn't happen with the Classic Skin, on which the previous position is restored.
This is under W10 1809 17763.107, previous Winamp 5.666 is free from this issue.
Thanks for looking into it.

Close Winamp. Go to C:\Users\*****\AppData\Roaming\Winamp. In there you will find a file called studio.xnf. Delete it. Restart Winamp. Everything should be ok now since all sizes and desktop positions of all components are stored in this file.

[justtesting]

Thanks for your response. Unfortunately it doesn't work.

When fresh installed (no roaming Winamp folder) in the first time it starts, I place and resize the Modern Winamp skin to my usual place on bottom right over the start bar (I use an expanded playlist under the main window, resized to the same width with all remaining windows closed, no menus, like it was common on old Winamp 2 days). Then, after relaunching, only the playlist will stay where it was left previously, but the main winamp window will be at top left of the screen (album art and library will remain closed).

Then, by deleting studio.xnf, both player/pl/art/ml will have the position and sizes reset, and after I re-organize them and re-open, the main winamp window will return to top left just as before.

OTH, if remove everything, then install the old winamp 5.666 and place my windows where I want them (working properly after relaunching the program); if do an in-place upgrade to current 5.8b (selecting current skin), Winamp will start in the correct position that was left before on the studio.xnf file. But then, if I move it and close the program, It'll jump back to where it was as 5.6 left it. It seems like the program is failing to write the last position for the Modern Skin on the file, given that it's capable to read and apply values that were created before on a previous Winamp version.

[MrSinatra]

interesting... it would be nice for winamp to have some options in prefs to delete files like this one, caches, temp files, DBs, etc, to "refresh" it or return to defaults, etc.

if not, maybe something to be added to winamp info tool or all about winamp?

[PeterK.]

interesting... it would be nice for winamp to have some options in prefs to delete files like this one, caches, temp files, DBs, etc, to "refresh" it or return to defaults, etc.

if not, maybe something to be added to winamp info tool or all about winamp?

Being honest I think it is a good idea users do not know this file. Removing this particular file is called "the last resort" when any other attempt failed. Please remember deleting this file clears ALL settings. You will lose everything from every skin you have had on your desktop since the last installation. So let us keep it a secret.

[justtesting]

I've replied yesterday with my findings about this, but it's still pending approval. Maybe the filename was filtered as link.
The short story is that deleting that file does nothing regarding the issue, only resets all windows, and the problem happens again (main window will always revert to top left). But if the file is created with the correct positions stored under 5.6, then 5.8 will read and apply them but, it'll keep being unable to modify it. This happens only with the modern skin, not classic which behaves ok.

[PeterK.]

... 5.6, then 5.8..

First of all I would stop switching between 5.6 and 5.8, which as we all know is still beta.
Second: uninstall Winamp and remove ALL leftovers from the installation folder and from this one I showed you. Third: Grab the last official 5.666 Build 3516, install it and I am sure your odd appearances will belong to your past problems.

[justtesting]

Thanks for your help, I believe we are having a misunderstanding.
I created this thread to report a problem with the current 5.8 beta: from a fresh install (no leftovers) it doesn't save the main window position correctly with the Modern skin. It always returns to top left.

I'm a Winamp user since late 90s, so I'm familiar with it's registry and file folders. The last Winamp 5.666 3516 is free from this problem. So, to test if the latest 5.8b has a problem with the file you've pointed (at least on this system), I've done an in-place upgrade to see how it behaved with a previously created and functional position file. And by this way, it'll restore the previous position created with 5.6, but it's unable to update the file to a new changed position for the main window under that skin.

I was already back to Winamp 5.666 3516 as my daily player, since it doesn't exhibit this issue. But it was never the point of this thread.

[PeterK.]

... I created this thread to report a problem with the current 5.8 beta ...

Well, in this case I think this would be the proper thread.

[justtesting]

Will do, thanks.

[Chad Cloman]

Close Winamp. Go to C:\Users\*****\AppData\Roaming\Winamp. In there you will find a file called studio.xnf. Delete it. Restart Winamp. Everything should be ok now since all sizes and desktop positions of all components are stored in this file.

This does not work. All it does is reset the location completely, and keep it that way.

After investigating, there appears to be a problem in WinAmp where it doesn't save the location of the main window when the Modern theme is selected. The playlist window, for example, is correctly saved, provided it's not linked to the main window. But the "Y" position of the main window is always zero in the studio.xnf file, even if I move it and exit WinAmp. So the updated value is not being saved to file.

I was able to manually edit the studio.xnf file to get the main Winamp window where I wanted it. So the problem is not in *reading* that file; rather, it's in *writing* it. And not just writing the whole thing; rather, it's in writing the information for the main window.

One thing, however, even though I've got the main window and the playlist window right where I want them, they are not attached. So when I move the main window, the playlist window stays. What configuration option in studio.xnf will attach them such that when I move one I move them all?

[Chad Cloman]

I can verify this occurs in 5.8 beta with the Modern skin and does not happen with the Classic skin. Deleting the studio.xnf file did not fix the problem.

Here are the entries in studio.xnf that I currently use:

code:
<entry name="rect" value="2688,-285,436,285" />

<entry name="restoredrect" value="2688,-285,436,285" />

After investigating, it appears that the code that writes the position and size information to studio.xnf has a bug. The first coordinate, the X-axis position, is written as zero. The last two parameters seem to be written correctly, but the first two (X and Y) are problematic.

Fortunately, the software is able to read the parameters correctly. So I was able to modify the file manually to get the desired screen position.

The problem I now have, however, is that the main window and playlist aren't stuck together, even though they are exactly next to each other. When I move the main window, the playlist doesn't move. Is there a studio.xnf setting that indicates the two windows are connected and should be moved together?

[MrSinatra]

Can u upload a fixed ver so we can send people here for it?

[MrSinatra]

Would it be possible for someone to first install 5.666, and then mark the affected files with a temporary .old extension, and then install 5.8, and then delete the affected 5.8 files, and then remove the .old extensions from the 5.666 versions, and get proper behavior that way?

If so, what are the exact files necessary to mark?

Or is this not practical due to other changes / updates in those specific files?

[r.e.e.d]

The problem seems to be the new version of modern skin, removing it and installing an older version from 5.666 the bug disappears.

I uploaded the older version that is working, until someone fix the new one.