> leowang wrote:
> > The two window are not in one process.
>
> Yikes, then you're basically trying to do two tricky things:
>
> * Undermine the window manager behavior for focus of events
> * Allow events to cross processes
>
> Not impossible, but might be h
>
>
> > The two window are not in one process. Process A has a window=20
> > in left hand side, and Process B has a window in right hand=20
> > side. So I think I can't use the above two method. Sorry I=20
> > forget to mention this in my description.
>
> By "not in one process" do you literally me
leowang wrote:
> The two window are not in one process.
Yikes, then you're basically trying to do two tricky things:
* Undermine the window manager behavior for focus of events
* Allow events to cross processes
Not impossible, but might be hard if
> The two window are not in one process. Process A has a window
> in left hand side, and Process B has a window in right hand
> side. So I think I can't use the above two method. Sorry I
> forget to mention this in my description.
By "not in one process" do you literally mean that they are in
>
> > I have two window in the screen display, one is on the left=20
> > side, another is on the right side. Now if I push in the left=20
> > side window, the right side window will be in deactivate=20
> > status and can't recieve any keypad event. It only can=20
> > receive keypad event until I pu
> I have two window in the screen display, one is on the left
> side, another is on the right side. Now if I push in the left
> side window, the right side window will be in deactivate
> status and can't recieve any keypad event. It only can
> receive keypad event until I push inside it.
>
>
6 matches
Mail list logo
