|
From: Ethan A M. <merritt@u.washington.edu> - 2006-04-10 02:48:44
|
On Sunday 09 April 2006 05:14 pm, Daniel J Sebald wrote:
>
> For an X11 window there can't be two clients desiring the ButtonPress
> event at the same times.
> The external client that created the window may or may not have requested
> ButtonPress via ButtonPressMask.
That would clearly be a programming error. Why open a window for the purpose
of displaying gnuplot output, and then fail to let gnuplot have access to the
window events?
> If it did and gplt_x11.c attempts to also set ButtonPressMask, the window will crash.
Seems unlikely.
Shouldn't you just get an error return from the call to XSelectInput?
Regardless. Even if you are correct that there is a potential conflict,
it is the fault of the application that opens the window and then
hands it over to gnuplot without letting go of the mouse input.
Gnuplot should expect mousing as normal, including mouse button events.
> The "b", "B" option is a solution that may not be elegant, but it works.
> It could be changed and placed under {un}set mouse if ever we find an X11 expert.
How do you know it works, if the tcl demo you have either crashes or
prevents mousing? Sounds to me like the mousing code is basically untested.
Do you have another demo that does work?
--
Ethan A Merritt
Biomolecular Structure Center
University of Washington, Seattle 98195-7742
|