[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #39304] ginput for FLTK does not return correc
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #39304] ginput for FLTK does not return correct X, Y coordinate on keypress |
Date: |
Thu, 20 Jun 2013 21:48:53 +0000 |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 |
URL:
<http://savannah.gnu.org/bugs/?39304>
Summary: ginput for FLTK does not return correct X,Y
coordinate on keypress
Project: GNU Octave
Submitted by: rik5
Submitted on: Thu 20 Jun 2013 02:48:52 PM PDT
Category: Plotting with OpenGL
Severity: 2 - Minor
Priority: 5 - Normal
Item Group: Incorrect Result
Status: Wont Fix
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: Any
_______________________________________________________
Details:
This report is just a note in case anyone runs into the same problem. If you
use ginput() and press a key instead of using the mouse to click on a point
then the button field returned will be the ASCII key code but the X,Y
coordinates will be those of the last mouse click.
Fixing this would be cumbersome as __fltk_ginput__.m relies on the axis
property "CurrentPoint" but this is specifically only updated when a mouse
button is pressed. One could modify __init_fltk__.cc to update the
CurrentPoint whenever a key is pressed, but this would not be correct Matlab
behavior. One could also modify __init_fltk__.cc to return a struct with the
key event information as well as the X, Y coordinates of the event. This
would possibly change how the @keypressfcn is handled though.
So, I'm just observing that this issue exists and marking it as won't fix.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?39304>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #39304] ginput for FLTK does not return correct X, Y coordinate on keypress,
Rik <=