The VideoLAN Forums

I'm not sure if it's a bug, but it was good in v1.x, it's very inconvenient.

To reproduce:
- open any video
- place the window in the top right corner
- move the window 1 or more pixels over the top screen edge
- double click to go to fullscreen
- double click to leave fullscreen
= window is re-placed to the top left corner

VLC 2.0.0, Windows Vista HP 32 bit SP2.

Thanks, I opened ticket for this
http://trac.videolan.org/vlc/ticket/6241 (missed one, sorry)

Yes, I just saw this behavior and it is extremely frustrating (unless Twoflower fixes the constant crashing when seeking DVDs, then I will likely just revert to 1.11 for the time being).

I pretty much always drag the title-bar off the top of the screen, so this new behavior is aggravating to say the least. In addition to fixing this bug, it would be even better if VLC were to (finally) have a true minimal mode in which the title bar is not present (where the window is moved by clicking and dragging the video itself). Both GOM Player and MPC have this ability (and I’m sure a lot of other players do too). VLC is a terrific player, but it is shocking that it still lacks this basic mode.

A related issue to the whole window snapping back to a default position when it is moved to what it considers to be an “invalid” position is the controls in full-screen mode. Drag it to the corner of the screen (as most people are wont to do), but if you drag it even one pixel off screen, then next time that VLC is run, it defaults back to the middle of the screen.

...it would be even better if VLC were to (finally) have a true minimal mode in which the title bar is not present (where the window is moved by clicking and dragging the video itself)...

I have started a new topic for this, yesterday.

Hide the title bar in minimal view

That ticket is actually http://trac.videolan.org/vlc/ticket/6241, per this thread.

Any news for this bug? It's so annoying, when switching between fullscreen and window mode...

Trac ticket will most likely indicate when the issue is fixed, but currently nobody is working with this AFAIK.

Bug fixed, after 6 YEARS! Too late.