Re: GPVAL_TERM_VCHAR (was: problem with "set x11 {size WW,HH} {position XX,YY}")

[Ben A. <bpa...@ma...>]

On Thursday, February 12, 2009, at 02:17PM, "Ethan Merritt" <merritt@u.washington.edu> wrote:
>On Thursday 12 February 2009 10:37:25 Ben Abbott wrote:
>> On Thursday, February 12, 2009, at 11:46AM, "Ethan A Merritt" <merritt@u.washington.edu> wrote:
>> >On Thursday 12 February 2009, Ben Abbott wrote:
>> >
>> >> To properly interpret the "size" information I'll get from x11 using  
>> >> the GPVAL_TERM_WINDOWID, I'll need the value for GPVAL_TERM_VCHAR.  
>> >> Temporarily I can assume it is 13 pixels. However, as I'll be using  
>> >> the window size obtained from x11 to determine if the mouse was used  
>> >> to change its size, and subsequently update the figures' size property  
>> >> on the octave end, I'd like to make sure I get his correct.
>> >
>> >Use it for what?  
>> 
>> The window size reported by x11 includes the portion reporting the mouse coordinates, 
>> which is not part of the gnuplot canvas. 
>> So I'd like to have TERM_VCHAR so that I can subtract this from the window's height.  
>
>Would you prefer a mousing mode that wrote the mouse coordinates without
>extending the size on y?   That would be a trivial change, and could be 
>toggled by the same hot-key that currently toggles the mouse coords on and off.

hmmmm. I was not aware the mouse coordinates could be toogled on and off. What are the default hot-keys?

If the mouse coordinates did not extend the y-size, the hassle of accounting for it would be more convenient.

If the mouse coordinates continue to extend the y-size, then I suppose I'd need to know when the mouse coordinates are active, and by how many pixels the window has been extended (which is presently equal to GPVAV_TERM_VCHAR).

Personally, I'd prefer that the mouse coordinates did not change the y size, but any solution that allow me to determine when the window is extended and by how much is ok.
 
Ben