I don't know how many people can imagine that going to "switch interface", than choosing a skin IS NOT what you have to do to actually change the skin. It did change, but I had to do that every time I wanted to use a skin. Now I found about the magic droptdown that can be saved with the preferences.
OK, here is a detailed explanation.
The problem here is to define the limit between what should be saved from one session to another and what shouldn't. For example, the Extended GUI, which allows controlling contrast/brightness/etc, is not persistent either. However, almost no-one complains about it. Why? It's exactly the same issue as what you dislike with the skins, isn't it?
In fact, since the time when VLC started to handle preferences, any change in the interface was not persistent unless done in the preferences. So, when opening a disc, you had to specify the drive letter (or device), but it was back to the default value the next time you started vlc, unless you set it once and for all in the preferences (it's still working that way btw).
Even though this behaviour makes sense for most options, it is a bit awkward for GUI settings. Thus, more and more, some GUI-specific options were remembered from one session to another (like the opened windows and their position, in the wxWidgets interface, or the last skin used and its characteristics, in the skins2 interface).
We would have done the same for the "Switch to skins" parameter, if there was not a technical issue: on Windows, the wxWidgets toolkit crashes when we switch back to the wxWidgets interface from the skins one. Said differently, we can switch to skins, but not switch back to the default interface (it simply crashes, so we deactivated the option). Now we are in front of the following choice:
- we let the situation as is, and users complain because "switching to skins" is not remembered
- we automatically switch to skins, but users who just wanted to give it a try without really wanting to use it will complain that they cannot go back to the default interface (of course they could reset the preferences, but they may not even know how to do that).
We chose the 1st one, in particular because the skins2 interface was undergoing a lot of development and it was not very stable. So being "locked" with a buggy interface was not fun
However, information to reduce users frustration can be found on the skins download page, on the forums, on irc, and with VLC 0.8.6 the installer creates a "quick shortcut" to activate the skins2 interface by default. I agree that it still lacks a FAQ entry though.
The good news is that the technical issue should disappear in VLC 0.9.0, because we get rid of the wxWidgets toolkit in favour of the QT one, and it will hopefully work better for this. The saving of the interface will then be the default (we are not opposed to that by principle, despite what you may think
)
Personally I would be happy without the skin but there is a big issue: the slider jumps crazily when you click on the timeline, to control it you have to "drag" it. I can't see why it's implemented like that, it's annoying Evil or Very Mad
This is a well-known problem, discussed in hundreds of threads in the "Feature Requests" forum. The short answer is that we can't do anything about it, but the QT interface in VLC 0.9.0 won't have this problem.
the skins can't be maximized easily, although I can stretch it by dragging it by the corner like any other window, sort of "fake maximize" or "force maximize".
True. The skins engine is not yet able to do that, so no skin can implement this feature. This feature will be added one day (probably for version 0.9.0)
while in skins2 mode, I don't have access to video controls (hue, saturation, brightness, contrast, etc)
Same thing, the skin engine is not able to create such actions.
This feature will be added as well, when I have some time for coding...