Just wanted to weigh in, as this is a pretty important usability issue IMHO. Personally I would also prefer the option of capturing all the displays (make this a checkbox in the launcher), otherwise your cursor will exit the screen in a multi-monitor setup. I'm an iOS developer by day who knows very little about AppKit but it should work. In the options dictionary, include the NSFullScreenModeApplicationPresentationOptions key, where its value contains the bitwise or of both NSApplicationPresentationHideMenuBar and NSApplicationPresentationHideDock. Im actually surprised to see they still sell these. Without those APIs you need to make a small change when invoking NSView's enterFullScreenMode:options: method. They are great for gaming and the only way I play except for driving games when I use a steering wheel. Previous games like Avernum 2: CS (presumably) used the older CGDispla圜apture APIs in order to black out all screens, and prevent normal system interactions. The result is a more productive and truly personalized computing.
#KENSINGTON TRACKBALLWORKS GAME CONFLICTS SOFTWARE#
I'm pretty sure there is an easy fix for this problem, which I hope that Jeff would consider offering in a patch. Kensington TrackballWorks is software that allows you to customize the functions of each of the buttons found on your trackball. Scrolling in fullscreen is difficult given that the menu bar and dock are auto-revealed when mousing over them. It's a nasty problem when you use mouse on border to scroll the view. Mouse on border bottom in fullscreen show Dock if you insist a little bit to move the mouse to bottom.
Mouse on border top in fullscreen show menubar and generate a game pause/slowdown, it's a nasty problem when you use mouse on border to scroll the view.
0 kommentar(er)
