Wiimote experiment

Okay, so I finally got to it. A few months ago I bought a wiimote to play a bit with the api’s floating on the net. It was until yesterday that I actually tried a driver, and since that seemed to work okay, I decided to give it a try myself. My simple goal, being an app plotting the raw inputs. However, it took me a 2 hours more than expected (1 =)) and also a lot more blood, sweat and tears. 😉 particularly because I made a lot of mistakes due to me being too tired 😉 So I will keep it short for now as I want to go to sleep.

I choose the wiiuse library as it seemed adequate for the job and still active (and even cross platform!). I started from the included example and tried to wrap it into a Qt app (hence I named it example-qt ;)). The obvious choice for drawing is using QGraphicsView. However, for once ;), I took the effort to see if there are no existing Qt graph plotting libraries. And this just happens to be the case. 🙂 Meet the excellent QWT lib. It couldn’t be more fit for the job. The site is (almost) nothing but the api docs, but that seemed sufficient. One second I thought this lib would not be qt4 ready, but it has been ported!

Quite a few seconds and segfaults later 😉 I got this:
wii experiment

Nothing fancy, but it does show the roll and pitch!! =)

Note: the wiimote survived the experiment 😉

Netbean probs

Some while ago, I start coding a feed reader in J2ME to run on mobile phones. After some searching, it seemed like Netbeans would be the way to go.. They provide a nice UI builder including modeling of the flow between the different screens, tailored towards cell phones. Also, it seems the Sony Ericsson SDK provides nice integration with Netbeans.

My favorite java IDE IntelliJ doesn’t seem to support mobile development at all. (for the record, I wouldn’t use IntelliJ if I had to pay for it myself ;)) The next best thing, Eclipse, seems to be less mature in this area, although they are progressing fast. So Netbeans it became.

To my surprise, I even found a tutorial on the netbeans site which already gave me a bootstrap to my task! 🙂

So, where’s the problem?

Well, I set up netbeans and created a project and all, so I could get to serious work on my 2h train trip. Unfortunately, I didn’t manage to write a single line of code! 🙂 As soon as I opened my laptop, the Netbeans IDE seemed to have become very unresponsive! Opening a menu could take 10 seconds, scrolling through the code is impossible. I couldn’t believe my eyes at first, so I rebooted because I thought my laptop was having trouble waking up after having the short nap. However, not improved. I had to give up.
At home, I searched the internet, and indeed, netbeans has problems with my ATI X600 ‘s PowerPlay function! Who would have imagined that. 😉 Especially since this is the only Java app I have trouble with… Anyhow, just disabling the PowerPlay function solves the problem! It’s probably related to my ATI drivers, but since I have a fricking Dell laptop, I’m not allowed to install drivers other than from Dell, so, as you can imagine, Dell never supplies updates to the driver! If anyone knows how to circumvent the checks going on in the driver installer from ATI, please let me know…


So, while I’m at it, why not add a first one. 😉 This is actually most recent. It is a very simple tool to inspect the ROT. The ROT (Running Object Table) is a system wide table in Windows, into which objects can register themselves, making them visible to and accessible by other applications. Inspect could be the wrong term: the tool just lists all objects in the ROT by their display name. There is a refresh button so that you don’t have to restart it all the time. 😉