| 
     
      
      
      From: Vitaly V. B. <vit...@uk...> - 2004-04-21 16:34:31
      
     
   | 
On Wed, 21 Apr 2004 14:45:22 +0200 Dennis Smit <sy...@yo...> wrote: > On Tue, 2004-04-20 at 15:44 +0300, Vitaly V. Bursov wrote: > > I've a kinda ported scivi to libvisual. It runs under libvisual xmms plugin. > > In different window :) All mouse/keyboard events are also ok both for libvisual > > and scivi :-) > Wow that is promising! can i see some code ? :), also how have you been > implementing the key/mouse events in the libvisual window, and do you I haven't, there are two windows. one is libvisual and another scivi :) patch againts scivi 0.2.0rc3 is here http://xmms-scivi.sf.net/scivi-to-libvisual.patch.bz2 it's a hack and there are few lines of libvisual code. > like the idea of modelling our own event system to that off SDL ? Well, can't say nothing bad about SDL's event system. One thing: what kind of events will be passed? You've already "grabbed" some keyboard keys ('a' and 's' for example) what should be passed to plugin if 'a' was pressed? plugin gets cleanup request now ;) It looks logical to make plugin define a list (description) of events it want to receive. List can be composed from event id predefined by libvisual for generic events like prev/next preset, visualization mode, window resize, etc. or plugin defined id's. In a last case plugin must supply description, default binded key for keyboard events. Libvisual then will have confugurable keyboard bindings which user can change as he/she likes. Plugin will not get events like "key 'p' was pressed" but will get SWITCH_PRESET event. > For the rest my plan of abuse for the upcoming weeks looked good ? AFAIR, yes. A huge TODO :) -- Vitaly GPG Key ID: F95A23B9 -- Vitaly GPG Key ID: F95A23B9  |