Mac OS X Lion Feature Support
Posted: Sun Jul 24, 2011 5:09 am
Some observations about the way Löve currently works in Mac OS X Lion:
In Lion, "fullscreen" apps are first-class citizens now. You put an app in fullscreen, and you don't have to leave it to switch to another app. It gets its own space and can be switched between via a swipe of four fingers on your Magic Trackpad. It's very convenient. I keep iTunes and Mail open at all times in their own spaces and swipe between them like it's nothing.
The problem is Löve, when placed in "Fullscreen" takes over the entire computer. Same thing happens with Minecraft, but that's probably Java's fault. Another problem with this method is if the game freezes, or Löve freezes, or all around stops working, you cannot get out of it. In Lion, Löve grabs the screen and doesn't let go. I can't switch between apps or anything while it's running which kinda sucks. So it would be really neat if OS X Löve could get proper Lion Fullscreen support.
I propose it is set up so Löve would have a love.fullscreen(f) function. And that the user could optionally customize it themselves. By default it could toggle Fullscreen up and down. But if the user so chooses, it could be customized so they could toggle it themselves and add their own code to help it along. The "f" variable would of course be like the focus version where f is true or false based on whether or not the app is being put into or taken out of fullscreen. And if the user just uses an empty function, the button for Fullscreen would be there, but it would do nothing. Whether the button appears or not would be a setting in the config file.
I know nothing about how Löve works, so I don't know how, or why it chooses the "take over the screen" method instead of a more passive "Just another window on top of the others" mode. I know that Fullscreen mode will usually keep the current resolution and change the display's resolution to fit it as long as it's valid. Maybe we could get an alternative mode where if the "haspassivefullscreen" flag is set, it will not use the resolution changing version and will just let you make the window itself as big as the screen and if the content is smaller than the screen, it would just get centered. Otherwise we could have total coding control over how big the content area is.
Just wanted to put that out there. Was hoping to get some input from whichever of you is in charge of the Mac builds. (Sorry, I always forget!)
In Lion, "fullscreen" apps are first-class citizens now. You put an app in fullscreen, and you don't have to leave it to switch to another app. It gets its own space and can be switched between via a swipe of four fingers on your Magic Trackpad. It's very convenient. I keep iTunes and Mail open at all times in their own spaces and swipe between them like it's nothing.
The problem is Löve, when placed in "Fullscreen" takes over the entire computer. Same thing happens with Minecraft, but that's probably Java's fault. Another problem with this method is if the game freezes, or Löve freezes, or all around stops working, you cannot get out of it. In Lion, Löve grabs the screen and doesn't let go. I can't switch between apps or anything while it's running which kinda sucks. So it would be really neat if OS X Löve could get proper Lion Fullscreen support.
I propose it is set up so Löve would have a love.fullscreen(f) function. And that the user could optionally customize it themselves. By default it could toggle Fullscreen up and down. But if the user so chooses, it could be customized so they could toggle it themselves and add their own code to help it along. The "f" variable would of course be like the focus version where f is true or false based on whether or not the app is being put into or taken out of fullscreen. And if the user just uses an empty function, the button for Fullscreen would be there, but it would do nothing. Whether the button appears or not would be a setting in the config file.
I know nothing about how Löve works, so I don't know how, or why it chooses the "take over the screen" method instead of a more passive "Just another window on top of the others" mode. I know that Fullscreen mode will usually keep the current resolution and change the display's resolution to fit it as long as it's valid. Maybe we could get an alternative mode where if the "haspassivefullscreen" flag is set, it will not use the resolution changing version and will just let you make the window itself as big as the screen and if the content is smaller than the screen, it would just get centered. Otherwise we could have total coding control over how big the content area is.
Just wanted to put that out there. Was hoping to get some input from whichever of you is in charge of the Mac builds. (Sorry, I always forget!)