Some of my thoughts on mouse support for Freevo...
Hans Meine wrote:
On Friday 24 September 2004 08:43, Thomas Weber wrote:
1. Arrow keys + buttons - Keyboards, Joysticks, Remotes, Mobile phones, ... 2. Pointer + buttons - Mouse, Touchscreen, Trackball, Touchpad, ...
Group one works nicely with freevo now, but group two would need some work. Maybe something like that detached player for extra buttons and ability to select items with cursor would be enough. [...]
First thought: Are there really users which want to use a mouse when they are sitting
in their livingroom??
Not really (which is the reason why Freevo refuses to support mice), but there have been several postings by people with touchscreens (in cars/kitchens for example).
Right. I don't know any of the developer crew, including myself, that are willing to work on mouse support. Patches are welcome though.
I think mouse/touchpad support is not really needed, but will probably be there "for free" if Freevo supports touchscreens.
Aren't mice, trackballs, and touchcreens all supported by mouse or mouse-like drivers? A common API even? I can see touchscreen support for Freevo being a good thing. BTW, DirectFB has touchscreen support too.
However, that could benefit from knowing the "active regions" of input elements on screen, which is exactly what is needed for touchscreen (/category 2 device) support.
Right. Actually _getting_ the mouse/touchscreen event is the easy part. I am betting the event would contain the coordinates of the action. So, for this to work inside Freevo would need to know the coordinates of every item, and get the event to that items eventhandler.
I don't know what's needed to add this kind of thing to Freevo but I think that's the missing link.
I had some idea of using some image map technique because at least acording to our display (mevas) the screen is just a big image. Maybe through the skin engine we could determine where each item is located. Anyhow... just a thought.
Maybe the new UI code could have this in mind - that some of the elements put on the screen are "active" (like menu entries), so that there can be a mapping from screen positions to elements that can then receive a KEY_ENTER event or sth. (maybe a future SCREEN_ACTIVATION event)?
The work I'm doing here won't touch on this sort of thing but mainly getting the events to Freevo. This architecture will allow for a mouse input plugin though, but we're left with the existing problem of connecting the event to an item on the screen.
-Rob
------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
