Wiimote Project

Thanks for the answers. But I saw one problem. I don't know why, but it seems that your program doesn't use the hole view area of the Wiimote.

I know that because I used BoonJin's program first and with it I normally calibrated. With the Wiimote on the same position, the calibration failed with your program (I had to put the Wiimote a little far for a good calibration).

This is the problem most Windows users find with the Java version. I thought it was related to the sensitivity settings, ujs as you advised me the setting of your application is to maximum.

p.s. When you try Boonin's app in Mac OS can you let me know the results so I can update the above post

But in this case, vbrayon had to put the Wiimote further away to make it work.
This sounds not like a sensitivity problem...

I believe it's really a sensitivity problem. Boonjin's program has a sensitivity adjust that is on level 5 for default (i put it on maximum and works well). Is not this the problem with your Java version? What's the level of sensitivity of your program?

PS.: I'm interested in help on a translation to portuguese-brazil.

PS.2: Visual calibration in BoonJin's program (Very interesting and necessary).

... the "calibrated screen area" didn't show the real calibration view (as you can see in the image below).

The point 1 is the preview of the mouse position in the "calibration details". The point 2 is the same preview, but outside the screen in agreement with "Calibrated Screen Area". And the point 3 is the really mouse position.
[...]
PS.2: if this function of preview calibration is working on mac (I belive it is) it explain the sensitivity problems on Windows told by me and benpaddlejones.

PS.: Everything works well but when the program starts everything is slow temporarily. This problem desappers when I minimize the program.

Quote from: ujs

I can give you a translation account for both European and Brazilian Portuguese if you want.

Yes, I would be honored. But there would be few modifications in Francisco's translation.

Some soggestions:
- System tray fuction. For now a can fix this using a program named ACTUAL WINDOWS MANAGER
(http://www.actualtools.com/windowmanager/). Otherwise it showld be interesting if you program could do it for itself.

- I liked the 'right click' function. But I can't move objects in some programs. Explanation: On ArtRage program (freeware in

http://www2.ambientdesign.com/files/artrage2.5starteredition_win.msi), for example, you can only move the "stencil" by clicking with the right button + drag

(drag with right click). I thought in something like this: after "X" seconds stopped at the same point, instead of a simple right click, just change the

fuction (maybe make a circle line around the mouse as an alert). If stay in the same point and you stop pressing the button, than you have a simple right

click. With this we could have both, simple right click and drag with right click. For now I can do it using another program named DMOUSE

(http://www.swapmousebuttons.com/)

- Can you do something as I told in the topic http://www.wiimoteproject.com/project-ideas/real-tablet-pc-on-windows-vista/?

The "Calibrated Screen Area" shows the area bounded by the 4 calibration points, not the corners of the actual screen.
It's works the same on all platforms, and doesn't explain the sensitivity problems on Windows.

Btw, I can't read anything in your image, it's too small.

What do you exactly mean by "slow"?
I didn't notice this when I tested the app on Windows XP.

I was just suggesting that you could take a look at Francisco's translation, since some of it could also be used for Brazilian Portuguese.
I'll send you a message with your translation account in a while.

I changed the right click function a while back, before that it worked like right button drag.
What you suggested (better control for drawing applications) will probably be possible in a future version.