The observant of you have noticed that I hadn’t posted since last December and there was a period of several months where Boxer’s repo lay suspiciously fallow.
Be that as it may, where the hell have you been? Boxer is a cleaner and less smelly codebase for it, with some powerful new systems for future growth, but there are still a number of new and existing features to be finished (which is to say “unbroken”) before it’s ready for release. Owing to mission creep Boxer 2.0 ( née 1.4) turned into a balls-out rewrite of large sections of Boxer’s underlying architecture: a labour comparable to cleansing the Augean stables of 3 year’s worth of thickly encrusted cattle poo written in Objective-C. (“<:/”, possibly, though that looks more like an apprehensive gnome.) The answer remains “when it’s done” followed by a frustrated and sympathetic smiley face. Those instructions will be corrected in the next release of Boxer, which brings us to… When the hell is the next version coming out? Unfortunately Boxer 1.3.2's UI and helpfile will still point you to the old System Preferences location to enable hotkey capturing, which no longer has the relevant option. This also applies to any GOG.com game apps you have: those will be listed separately in the Security & Privacy pane, and must be given permission individually. After that, everything will work the same as it always has.
#SHOUD I UPGRADE TO LATEST VERSION OF BOXER FOR MAC HOW TO#
Hello boys and girls! Let’s start with the pressing stuff: Go ahead and upgrade to Mavericks alreadyīoxer works just fine in the newly-released OS X 10.9 Mavericks, with the sole exception that you'll need to give Boxer permission to capture hotkeys again so that Ctrl+ arrowkeys won't switch spaces while you're playing.īoxer’s issue tracker has an illustrated walkthrough of how to do this but the short version is that you'll need to go into “Security & Privacy” in System Preferences, tick a box in the Privacy tab to give Boxer permission to do naughty accessibility things, and then restart Boxer.
0 kommentar(er)
