yeah.. exactly... so that means that before the event is dispatched to a
window, the window manager knows to whom the event is to be dispatched, but
that doesn't seem to be the case because if I comment the calls to fusion
which dispatch the message to handle foreign reactions, the event structures
are not correctly filled. I checked theme using printf's and gdb..
then what may be the reason for this?
On 12/5/06, Amar M. Balutkar <[EMAIL PROTECTED]> wrote:
Fusion is just responsible for dispatching the events to the
appropriate window. After filling the appropriate structures, wm calls
the dfb_window_dispatch, so that the window (which may be created by
another application) receives the event. Note that there will just be
one instance of wm, spawned by the master, but the windows may be
created by any applications not necessary the master. So fusion will
just act as an IPC to pass information from the wm (master) to the
windows (master/slave).
As you have commented out post_event, the event structure is not
populated with new events and window information is lost (check
definition of post_event). Also dfb_window_dispatch is not called, so
the window doesn't receive any events.
Regards,
Amar M. Balutkar
Arvind Ayyangar wrote:
> so does it mean that fusion is responible for filling in the values of
> the structures? because from the code, i could not see any values
> being written into the structures until an ioctl call to the fusion
> driver where the values seemed to change. At the same time, the event
> on which the event occurred is ultimately taken from the
> CoreWindowStack->stack_data where all the window manager information
> is stored.
>
> I am not sure I have framed the question right.. the whole flow of
> events is just so confusing... some help would be appreciated :d
>
>
> Regards
> Arvind Ayyangar
>
>
>
>
> On 11/30/06, *Denis Oliver Kropp* <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>
> Arvind Ayyangar schrieb:
> >
> > hi,
> > I am trying to pass all the events to userspace through a
> socket. All
> > I need is the type of event and the window on which the event
> occured.
> > Assuming i am using the default window manager, I call a
> function to
> > send this information from handle_key_press,
handle_button_press,etc
> > since untill this stage no processing on teh events seems to be
> done.
> > I get the information correct until i comment a call to
> post_event (i
> > did this in the send_event_button) after which it doesn't return
the
> > correct window id on which the event occurred.
> > Could through some light on this?
>
> The window id (and other values) is filled in by
> dfb_window_dispatch()
> called by post_event().
>
> --
> Best regards,
> Denis Oliver Kropp
>
> .------------------------------------------.
> | DirectFB - Hardware accelerated graphics |
> | http://www.directfb.org/
> <http://www.directfb.org/> |
> "------------------------------------------"
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> directfb-dev mailing list
> [email protected]
> http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
>
--
Regards
ARviND AyyangaR
_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
