79
edits
Changes
Jump to navigation
Jump to search
Line 19:
Line 19: +
→Cursor control
What a great addition to Wii homebrew! That said, could I make a couple quick suggestions? I spent about 5 minutes trying to figure out how to start a game because I was holding the Wiimote sideways like an NES controller (the cursor moves, but pressing A or 2 does nothing). Could you update the button-press handler(s) to register a button press wherever the cursor is displayed, rather than wherever the Wiimote is pointing? Thanks again for porting this to the Wii! -- [[User:goodsoup|goodsoup]] <span style="font-size: smaller;" class="autosigned">—Preceding undated comment added 20:29, 18 March 2010 (UTC).</span><!--Template:Undated-->
What a great addition to Wii homebrew! That said, could I make a couple quick suggestions? I spent about 5 minutes trying to figure out how to start a game because I was holding the Wiimote sideways like an NES controller (the cursor moves, but pressing A or 2 does nothing). Could you update the button-press handler(s) to register a button press wherever the cursor is displayed, rather than wherever the Wiimote is pointing? Thanks again for porting this to the Wii! -- [[User:goodsoup|goodsoup]] <span style="font-size: smaller;" class="autosigned">—Preceding undated comment added 20:29, 18 March 2010 (UTC).</span><!--Template:Undated-->
: I just thought I would add that if you're pointing the Wiimote at the screen and obstruct the line-of-sight between the Wiimote and Sensor Bar, then pressing A, B, 1, or 2 on the Wiimote does nothing (as one might expect) but the cursor is still displayed on the screen where it was last pointing before line-of-sight was obstructed. I looked at the source code, and I wonder if this is due to the way the cursor is kept in the bounds of the screen or game in the constrain_mouse function in sdl.c (since the cursor/"mouse"'s position is reset when out of bounds). I'd love to help with this, but I've never programmed for the Wii or used SDL before, so I'm still trying to get on my feet. [[User:Goodsoup|Goodsoup]] 21:50, 21 March 2010 (UTC)
: I just thought I would add that if you're pointing the Wiimote at the screen and obstruct the line-of-sight between the Wiimote and Sensor Bar, then pressing A, B, 1, or 2 on the Wiimote does nothing (as one might expect) but the cursor is still displayed on the screen where it was last pointing before line-of-sight was obstructed. I looked at the source code, and I wonder if this is due to the way the cursor is kept in the bounds of the screen or game in the constrain_mouse function in sdl.c (since the cursor/"mouse"'s position is reset when out of bounds). I'd love to help with this, but I've never programmed for the Wii or used SDL before, so I'm still trying to get on my feet. [[User:Goodsoup|Goodsoup]] 21:50, 21 March 2010 (UTC)
:: Jeez, I should come here more often. Point (1) - the menu event code is somewhat messy. I think even if the mouse is hidden you can still 'move' it and have the menu react. This code was originally developed for a touch-screen device so it's not surprising that the mouse behaves as it does. I'll see if it's feasible to eliminate the mouse part of it. As for point (2), this seems to be more of a limitation of SDL-Wii, as I've heard this topic in other discussions before. I don't think SDL-Wii has any way of being made aware that the pointer no longer has line-of-sight, so it simply keeps the pointer at its last known location. [[User:Madmanguruman|Madmanguruman]] 23:59, 11 October 2010 (CEST)