Videowall windows can be maximized not set to fullscreen

On Windows and apparently on linux, video windows created by videowall outside the main UI can be maximized but not set to fullscreen with right-click/double click/alt+enter or F11.

added Component::Video: filters Severity::normal Type::bug Version::master git + 1 deleted label

changed milestone to %Bugs paradize

Isn't that the case with all video splitters?

Maybe, yet videowall doesn't really make sense in just maximized state. TBH I have no idea of the work needed for that but it apparently used to work in 1.1.11.

assigned to @fenrir and unassigned @MigrationBot

I have no troubles putting any given window from a video wall to fullscreen and back.

VLC controls do not work since the fullscreen boolean variable of the playlist cannot really deal with more than one window (whether due to splitter or to multiple angles). Splitter controls are explicitly unimplemented in the core so far.

added Component::Core: Video output label and removed Component::Video: filters label

Replying to [comment:3 courmisch]:

I have no troubles putting any given window from a video wall to fullscreen and back.

I can not get this to work with VLC 2.0.6 and Windows 7. I can maximize any given window, but not set them to absolute fullscreen (without the window decorations).

See #8888 (closed)

Replying to [comment:4 fabianvanliempt]:

Replying to [comment:3 courmisch]:

I have no troubles putting any given window from a video wall to fullscreen and back.

I can not get this to work with VLC 2.0.6 and Windows 7. I can maximize any given window, but not set them to absolute fullscreen

I don't know about Windows 7, but KDE allows setting any given of the video wall window to fullscreen mode from window's system menu.

Doing it by double click would require handling of mouse events in video splitters. Doing it via VLC hotkeys would require per-output hotkey handling - which has never ever been implemented.

#3843

added Status::duplicate label

closed

mentioned in issue #8684 (closed)

mentioned in issue #8888 (closed)