winset(), Why You No Full Screen?

ID:676432
 
Apr 16 2012, 7:34 pm
Not a bug
BYOND Version:494
Operating System:Windows XP Pro
Web Browser:Opera 11.62
Applies to:DM Language
Status: Not a bug
This is not a bug. It may be an incorrect use of syntax or a limitation in the software. For further discussion on the matter, please consult the BYOND forums.
This will put your window in full screen mode, overtaking the task bar: 
.winset "mainwindow.titlebar=false mainwindow.can-resize=false mainwindow.is-maximized=true"

This will not: 
winset(src, "mainwindow", "can-resize=false;titlebar=false;is-maximized=true")


I'm not sure why this is, but not being able to use winset() to initiate full screen mode and not being able to use nested ternaries makes a decent full screen toggle annoyingly impossible.
Apr 17 2012, 9:21 am
The reason for this is sequence; the .winset command processes all changes sequentially, whereas the server version uses a more efficient method. Using separate winset() calls would have the same effect.

However, the fact that the taskbar can be obscured is itself buggy behavior; it's basically something Windows foists on us that we've been unable to find a suitable workaround for in the past.
Apr 17 2012, 9:21 am
Lummox JR resolved issue (Not a bug)
Apr 18 2012, 8:55 am
Thank you for the workaround. But if the covering of the taskbar in such a buggy manner is unwanted behavior, noting that you once tried to override it, are there any plans for implementing any sort of true full-screen?