Postby erwan10 » 07 Jan 2011 21:54
There is indeed a limitation that could be worked out.
As of today, a "window provider" is looked for with a whole set of initial parameters (x, y, width, height, is_standalone). Unfortunately, fullscreen is not passed at this level, but only in a subsequent call. This results in the interfaces (skins2, qt4, dummy, ...) creating, sizing and displaying a windowed video, then only eventually switching to fullscreen.
Should fullscreen mode be passed as another initial parameter, the dummy interface could directly size the window to be fullscreen. On Windows, there should be no problem. On Linux, fullscreen is set via a EWMH call (no direct sizing). So an explicit resizing may be needed (to be checked) if EWMH fullscreen feature doesn't work on a hidden window.
Regarding "real" interfaces (qt4 or skins2), they will still appear because there is no reason to hide them (albeit may be the --qt-start-minimized parameter that I don't know). But you won't see any longer the unpleasant fleeting intermediary resizing in windowed mode before going fullscreen. Using the dummy interface, you should really get a clean fullscreen.