|
|
Unsupported — We cannot guarantee that this software will work properly on Mac OS 10.8 and above. Please be careful.
Release: WiiMote Control, v20071201
Release Type:
Beta
Version:
20071201
Release Notes
I've apparently fixed the connectivity issues that would crash the WiiMote Control patch. I'm not sure how stable it is, and there are a number of things I still need to fix (nunchuk support, better IR support, atan2 [harder than I initially thought], etc) before a production public release. But for you early adopters, this might be useful :)
Installation InstructionsPlace the plugin file in |
Once the patch is enabled, it'll start searching for a wiimote to communicate with. If it doesn't find one after a brief timeout (10-20 seconds?), it gives up, and doesn't restart (restarting the search is a bit trickier than expected), so it'll never connect after this brief window. I'm working on this, don't worry.
recreating the patch may or may not work? (It looks like it did at least once for me).
thank you so much Chris, i'll dive into this. Hope you'll manage to implement the IR part too !
btw, is there a way to bundle your plugin into one's custom app ? (hence avoiding to manual install the plugin)
(I'd wait for today's wiimote beta, it's super :)
yes, we've solved the bundled plugin-loading for both Tiger and Leopard.
[QCPatch loadPluginAtPath:{my plugin path}] (or something to that effect) before any QC code, and you're good to go. It's documented wherever you asked this earlier (in Tiger, I think).
does this statement goes into the main.h ? (i don't really see where else it could go.../ sorry for my total lack of objC knowledge)
That depends on how your app is coded. Most Cocoa apps will have a class called "AppController" or something, which will have a method like this:
- (void) applicationWillFinishLaunching:(NSNotification*)notificationYou'll want to put it in there (this is executed whenever the application is launched). Putting it in main.h will probably not compile, and if it does, it almost certainly won't do what you're expecting it to :)
For reference, here's how I did it in one of my recent Tiger/Leopard projects:
[QCPatch loadPlugInsInFolder:pluginPath];That'll load all the plugins found at pluginPath, which is an NSString.