ID:132831
 
Instead of having some round-about, almost workaroundish feeling method for making full-screened games; could you just make a check-box for it in the interface editor?
This could also help prevent inconsistencies like the one reported here. Just because I don't want the window to be re-sized; doesn't mean I want it to be full-screened =[

EDIT: We all decided you should just add an is-fullscreen setting =P
Falacy wrote:
Instead of having some round-about, almost workaroundish feeling method for making full-screened games; could you just make a check-box for it in the interface editor?
This could also help prevent inconsistencies like the one reported here. Just because I don't want the window to be re-sized; doesn't mean I want it to be full-screened =[

I think to respond to this request I'd have to understand what's going on in that bug report, but the bug report is lacking in detail.

At present, BYOND does not support full-screen (meaning that the game covers the taskbar), and any situations that actually do cover the taskbar are bugs. One such bug was fixed already (issue 548) and will appear in build 455.

Lummox JR
In response to Lummox JR
Lummox JR wrote:
At present, BYOND does not support full-screen (meaning that the game covers the taskbar), and any situations that actually do cover the taskbar are bugs.

Hrm, thought that was the whole point of "full-screen" in BYOND games.
In response to Lummox JR
Doh, I thought that was intended behavior :(
In response to Lummox JR
I have a verb which I put into the interface for making the game full screen. It works perfectly in every way, besides the black spaces on the sides in most resolutions, which is normal. I don't see the problem though. It works perfectly with no issues. Some issues were found when it came to taking off the full screen mode, but they were easily resolved.

verb/FullScreen()
if(!src.Fullscreen)
winset(src, "default", {"
titlebar=false;
statusbar=false;
can-resize=false;
is-maximized=false;
"}
)
sleep(1)
winset(src,"default","is-maximized=true")
src.Fullscreen=1
return
if(src.Fullscreen)

winset(src, "default", {"
titlebar=true;
can-resize=true;
is-maximized=false;
is-minimized=true'
"}
)
sleep(1)
winset(src,"default","is-minimized=false")
src.Fullscreen=0
return


If I don't minimize it when taking it off, I found that it would leave weird black blocks all over the screen, some of which won't come off of the desktop.

You also need that sleep(1) before maximizing after you take off the titlebar, statusbar, and resizability, otherwise the taskbar doesn't go away.

[EDIT]

I noticed that for some reason the rest of the code under the verb's name is tabbed one too many. I don't know why it did that, but that's not how it's actually written =/.
In response to Lummox JR
Lummox JR wrote:
...situations that actually do cover the taskbar are bugs. One such bug was fixed already (issue 548) and will appear in build 455.

:O

DO NOT WANT!

I always thought this was intended behavior, and one of the most user friendly aspects of how BYOND handles skins. It's also too damn good to not have as part of the system. All my projects post 4.0 make use of this bug:

Migma, my GiaD 2009 project.

Regressia, which I'll finish if it kills me.

Note that in each case, what you see is the entire interface. When Esc is pressed the game pauses and a standard menu appears, and F11 toggles between Full Screen and 1x display sizes. This is the first time I've ever seriously considered not upgrading BYOND. Does the fix affect DS or DM?
In response to IainPeregrine
IainPeregrine wrote:
DO NOT WANT!

/agree
In response to SuperAntx
SuperAntx wrote:
IainPeregrine wrote:
DO NOT WANT!

/agree

seconded
In response to Fugsnarf
thirded
In response to D4RK3 54B3R
This is absurd, why take away fullscreen? >_>
Fourthed.
In response to IainPeregrine
IainPeregrine wrote:
DO NOT WANT!

I always thought this was intended behavior, and one of the most user friendly aspects of how BYOND handles skins. It's also too damn good to not have as part of the system.

It's a Windows thing actually; if it's intended behavior it's at their end, but it's still stupid because 1) they didn't document it and 2) it's not all that logical.

It may be that perhaps it'd make sense to add some sort of full-screen parameter to the window control, if there's a real need for this, but the old behavior is most definitely a bug so it can't stay the way it was.

Lummox JR
In response to Lummox JR
Lummox JR wrote:
It's a Windows thing actually; if it's intended behavior it's at their end, but it's still stupid because 1) they didn't document it and 2) it's not all that logical.

It may be that perhaps it'd make sense to add some sort of full-screen parameter to the window control, if there's a real need for this, but the old behavior is most definitely a bug so it can't stay the way it was.

Yeah, Its a user preference you can define for the taskbar whether or not it always stays on top, so I understand that it's a bug, and bugs certainly should not be treated as features. I'm just afraid that an actual feature will never arrive. We've been asking for a simple way to determine the client's screen resolution, and the feeling a lot of us have gotten is that this isn't a priority and that hacking kludge workarounds will suffice. This may not be the official stance, but sometimes a simple "This is on the to-do list, we just don't know how yet" could really set our minds at ease.
In response to Lummox JR
Lummox JR wrote:
It may be that perhaps it'd make sense to add some sort of full-screen parameter to the window control, if there's a real need for this

"If"? >_>
If the many past requests on this general topic haven't told you so already, then... I believe I formally speak for the entire BYOND developer community when I say: DO WANT.

<small><code>oh, do not scorn me for the intentional exaggeration, please</code></small>
In response to IainPeregrine
IainPeregrine wrote:
Yeah, Its a user preference you can define for the taskbar whether or not it always stays on top, so I understand that it's a bug, and bugs certainly should not be treated as features. I'm just afraid that an actual feature will never arrive. We've been asking for a simple way to determine the client's screen resolution, and the feeling a lot of us have gotten is that this isn't a priority and that hacking kludge workarounds will suffice. This may not be the official stance, but sometimes a simple "This is on the to-do list, we just don't know how yet" could really set our minds at ease.

I'm okay with adding a winget() parameter to grab screen resolution, though it would be grabbing the work area (i.e., everything but the taskbar) and not the full screen res. I'm actually also okay with the idea of a full-screen parameter to allow games to expand beyond the work area, but only if the end user hasn't set their taskbar to always-on-top. Considering that the bug fix does affect people, I suspect this will get some attention shortly.

Tom and I can always work out a game plan, but the important thing is figuring out:

1) What do the authors want?
2) Is it possible to satisfy the authors without overriding client settings (e.g., taskbar always on top)?

Lummox JR
In response to Vic Rattlehead
Vic Rattlehead wrote:
This is absurd, why take away fullscreen? >_>
Fourthed.

They don't want fullscreen byond games, seeing as taskbar's always-on-top var is on by default on most computers, and 99% of the players on BYOND don't even know such a var exists.

Fifth'd.
In response to Lummox JR
I hope this "shortly" you're talking about is actually shortly. I'm rather dissapointed to have to take out my current fullscreen feature when the next version comes out. I don't want to bother switching between versions so I don't compile with 455+.

[EDIT]

It's not very comforting to hear you say, "It'll get attention."
In response to Fugsnarf
Fugsnarf wrote:
I hope this "shortly" you're talking about is actually shortly. I'm rather dissapointed to have to take out my current fullscreen feature when the next version comes out. I don't want to bother switching between versions so I don't compile with 455+.

Which version you compile with won't make any difference. The bug fix applies at the DS level.

[EDIT]
It's not very comforting to hear you say, "It'll get attention."

Um... why? Saying that I think this is a thing we should look at in light of the bug fix's ramifications is a good thing. This is practically the opposite of sweeping the issue under the rug.

Mind you there's no pleasing everyone. Some authors are going to want the ability to force fullscreen regardless of a user's Windows settings. But for those authors who want fullscreen support and users who turn off the taskbar-on-top feature, I'm sure we can work out some kind of accommodation.

Lummox JR
In response to Mista-mage123
Mista-mage123 wrote:
They don't want fullscreen byond games, seeing as taskbar's always-on-top var is on by default on most computers, and 99% of the players on BYOND don't even know such a var exists.

If the end user has that setting, we should respect it, even if 99% of people forget to turn it off. I see no reason to rudely override the user's settings.

We could, I suppose, set up some kind of config setting that asks if the user is okay with games going full-screen regardless of that, and maybe even default that on for most BYOND users. Kind of a pain, but if full-screen is going to be allowed (right now it only exists as the result of a bug) then we need to give users the ability to opt out of it.

Lummox JR
In response to Lummox JR
ANY MMO supports fullscreen, Game Maker supports it... anything does.

Why can't BYOND? A helpful bug is what your getting rid of, unless an actual fullscreen option is put in.
In response to Vic Rattlehead
Vic Rattlehead wrote:
ANY MMO supports fullscreen, Game Maker supports it... anything does.

Why can't BYOND? A helpful bug is what your getting rid of, unless an actual fullscreen option is put in.

I have said several times now that this will get attention, and I'm sure we can work something out considering how many people want full-screen support. I'm not sure how much clearer I can get than that, since at the moment I'm not in any position to make any promises on exactly what path we'll take with this. The only important proviso as far as I'm concerned is that users who want to opt out of forced full-screen should have that choice.

Lummox JR
Page: 1 2 3