David MacMahon wrote:
> Hi, Hazen,
> 
> On Mar 21, 2010, at 12:50 , Hazen Babcock wrote:
> 
>>
>> ./x01c -dev xwin -locate
>> This will stop reporting positions as soon as you move the cursor
>> outside of a plot.
>>
>> ./x01c -dev xcairo -locate
>> This device only reports the position when you press a key. It will also
>> stop reporting positions when you move outside a plot and press a key.
>>
>> ./x01c -dev qtwidget -locate
>> This device is the same as xwin.
>>
>> Was this the intended behavior? Since the xcairo device is the only one
>> that does not report the cursor position in real time it is the only one
>> that lets you move between the plots.
> 
> When you say the xwin device reports the cursor position in real time, 
> do you mean that it spews out position information every time you move 
> the cursor?  That it not the behavior I get for the xwin driver.  I get 
> xwin and xcairo behavior that matches your description of the xcairo 
> driver (plus clicking the mouse is like pressing the space bar).  I 
> don't have the qt devices built so I can't comment on them.

Yes, when I run the xwin device in -locate mode it prints out the cursor 
position every time an event of any kind occurs (mouse movement, mouse 
click or keypress).

On my linux box the xcairo device does not respond to mouse clicks, only 
key presses.

I thought I would look up how the devices are supposed to respond, but 
it looks like plGetCursor() is undocumented. I'd be happy to fill in the 
documentation and implement for the Qt devices, but, any thoughts on 
what the "correct" behavior should be? I think we have the following 
possibilities for when this function should return:

(1) After any key press or mouse event including movement.
(2) Key press and mouse button events (release events only?).
(3) Mouse button event only.
(4) Key press only.
(5) Other permutations of the above.

-Hazen

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Plplot-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to