[Partially solved] VLC 0.9 doesn't remember size of Open Dlg

[theone256]

I have been testing the nightlies for a while, and 0.9 works quite well for me, except for a little annoying problem: the position and size of the open dialog are not remembered when VLC is restarted.

Also, with the latest nightly build, when you resize the open dialog vertically to its minimum size and then click on "Use a subtitles file", the checkbox becomes hidden by the file extension filter combo box (this is a very minor issue).

[Jean-Baptiste Kempf]

Well, this is NORMAL, Open Dialog center on the underlying main Interface.

The resizing bug will be fixed 2morrow.

[theone256]

Well, this is NORMAL, Open Dialog center on the underlying main Interface.

Ah! I didn't notice that. Well, the positioning behavior is normal then. But what about remembering the size of the dialog?

The resizing bug will be fixed 2morrow.

I see that you've fixed the overlap of the checkbox (in git). Thank you for that. But the size of the dialog still doesn't seem to be remembered.

Actually, I infer that from the git log, but I couldn't test the open dialog with the latest nightly build. VLC crashes when I try to open it (under Windows XP):

Code: Select all

Error message:Unhandled exception at 0x02035ff4 in vlc.exe: 0xC0000005: Access violation reading location 0x0075007d. Call stack: > libqt4_plugin.dll!02035ff4() [Frames below may be incorrect and/or missing, no symbols loaded for libqt4_plugin.dll] msvcrt.dll!77bfc3c9() msvcrt.dll!77bfc3e7() msvcrt.dll!77bfc42e() msvcrt.dll!77bfc42e() libqt4_plugin.dll!02555281() libqt4_plugin.dll!024ddf27() msvcrt.dll!77bfc3c9() libqt4_plugin.dll!024ab852() libqt4_plugin.dll!024e096c() libqt4_plugin.dll!02086de6() libqt4_plugin.dll!02087165() libqt4_plugin.dll!0209beea() libqt4_plugin.dll!0209e3f0() libqt4_plugin.dll!020acd7d() libqt4_plugin.dll!0209980c() msvcrt.dll!77bfc3c9() libqt4_plugin.dll!024ab852() libqt4_plugin.dll!024d8a16() libqt4_plugin.dll!02078e54() libqt4_plugin.dll!020797dc() msvcrt.dll!77bfc3c9() libqt4_plugin.dll!020a5459() libqt4_plugin.dll!021ab206() msvcrt.dll!77bfc2de() libqt4_plugin.dll!021b1372() libqt4_plugin.dll!024e55e9() libqt4_plugin.dll!021ab206() msvcrt.dll!77bfc2de() libqt4_plugin.dll!0220efb8() libqt4_plugin.dll!021a9d4c() libqt4_plugin.dll!021ab206() msvcrt.dll!77bfc2de() libqt4_plugin.dll!020aab5c() libqt4_plugin.dll!023d1aa0() msvcrt.dll!77bfc2de() oleaut32.dll!770e48b5() libqt4_plugin.dll!024d8a16() libqt4_plugin.dll!02078e54() libqt4_plugin.dll!02078f6e() msctf.dll!746915d1() msctf.dll!74694fae() msctf.dll!7469467f() msctf.dll!74694fae() msctf.dll!74694fb8() msctf.dll!74694fb8() msctf.dll!74694fae() msctf.dll!746a09cd() msctf.dll!746a13d4() msctf.dll!746a13d9() msctf.dll!746a0f0f() user32.dll!7e3ab372() user32.dll!7e3ab317() user32.dll!7e398a10() user32.dll!7e3a8d8b() user32.dll!7e3a8d8b() ntdll.dll!7c921008() ntdll.dll!7c921008() ntdll.dll!7c921008() ntdll.dll!7c9218a0() ntdll.dll!7c92a3e1() ntdll.dll!7c921008() ntdll.dll!7c921008() ntdll.dll!7c921008() ntdll.dll!7c920a16() ntdll.dll!7c9201bb() msvcrt.dll!77bfc3c9() msvcrt.dll!77bfc3e7() libvlccore.dll!6a5b0f02() libqt4_plugin.dll!01f732e4() msvcrt.dll!77bfc3c9() libvlccore.dll!6a5bbdbf() kernel32.dll!7c8024c7() libvlccore.dll!6a54ea55() libvlccore.dll!6a5adc54() msvcrt.dll!77c0a3b0() kernel32.dll!7c80b713()

I know it might not be very useful without method names. Why aren't the nightlies compiled in debug mode (with debug symbols), by the way? Wouldn't that help locating these kind of bugs more easily?

[Jean-Baptiste Kempf]

I will fix this crash soon.