changed:
-
adding pointer input control plugin support to FreeVo
update: that work was pretty much done and has been somewhat tested now, hopefully on it's way to cvs after some cleaning - besides this did a minor tweak to FreevoMenuConfig
am adding mouse input support (pointer device, for touchscreen use) to Freevo, hopefully finishing the work this week (Feb 4 2005). decided to work with the 2.0 development version which has been considerably refactored. the system must be in production use soon - everything workable (for a museum setup) latest by the end of February (i have asked the people who are doing the actual set up to test if 2.0 works for them).
the second draft patch is at http://an.org/freevo/freevo-pointer_input-works.diff and will inform freevo-dev about the update. it now 'works' (doesn't crash) and does what is supposed to, but am getting drawing errors in the picture browsing (the selection rectangles) and the activation of items is a bit hacky (in the menu event handling). required quite a bit of digging into the event system, area handlers, and even to the underlying mevas library (where am finally getting the widget(s) clicked
on -- they are then mapped back to items using a new dict in listing_area)
below are what was found in the dev archives before starting this work:
from http://sourceforge.net/mailarchive/message.php?msg_id=9620087
<pre>
From: Rob Shortt <rob@in...>
Re: input architecture
2004-09-24 06:12
> 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.
</pre>
there's been a previous thread on TouchScreen support too: http://sourceforge.net/mailarchive/message.php?msg_id=8636914
<pre>
From: Dirk Meyer <dmeyer@tz...>
Re: About using mouse or touchscreen
2004-05-31 08:25
Luis Miguel García Mancebo wrote:
> Perhaps a "plan" can be done before start coding in order to have a
> good idea of what needs to be done.
We need to think about the following questions:
- how translate mouse click to item below it?
- how to add extra options with no space on the screen, like menu
back? Maybe a plugin drawing some sort of remote?
Dischi
</pre>
a message discussing encapsulating the pygame depency to the use of SDL, mentions 'mouse_input' separately (which is a bit awkward, as SDL and pygame give the mouse nicely too) http://sourceforge.net/mailarchive/message.php?msg_id=9414620