On Mon, Oct 11, 2010 at 2:27 AM, Per Inge Mathisen <[email protected]> wrote: > I was told by Zarel and cybersphinx earlier that you absolutely needed > resolution changing before qt-branch could be merged
I'm sorry I was unclear, but I meant that we should have true-fullscreen instead of windowed-fullscreen, more for the performance and UI reasons than because of a need to change resolution. I'd always known that was infeasible, so I never strongly disagreed with the idea of merging qt-branch without it. > So where does this leave Qt branch? Writing our own support for true > fullscreen may be tough. I am not sure if using another library to set > true fullscreen then leaving it to Qt to control is even possible. But > I could look into it. As I said, I never strongly disagreed with the idea of merging Qt-branch without true fullscreen support. I gave some reasons against it, and I am mentioning them again, but ultimately I leave the decision to you guys to decide whether or not the trade-off is worth it. On Mon, Oct 11, 2010 at 7:05 AM, Christian Ohm <[email protected]> wrote: > The fvwm case is more of an annoyance, since you can e.g. configure a key > combo > to toggle it. It just was a concrete example for edge-activated things, since > I > don't know what modern desktop stuff does. It's more of a problem in Windows and OS X, where there is no global shortcut to toggle screen edge behavior. =/ If you have multiple applications with screen edge behavior, you'd have to open each one, go to their preferences dialog box, and turn it off. -Zarel _______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
