[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #44833] ginput doesn't correctly process shift
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #44833] ginput doesn't correctly process shift/ctlr/alt key combinations |
Date: |
Tue, 14 Apr 2015 12:31:52 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0 |
URL:
<http://savannah.gnu.org/bugs/?44833>
Summary: ginput doesn't correctly process shift/ctlr/alt key
combinations
Project: GNU Octave
Submitted by: philipnienhuis
Submitted on: Tue 14 Apr 2015 02:31:51 PM CEST
Category: Plotting with OpenGL
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Regression
Status: None
Assigned to: None
Originator Name: Philip Nienhuis
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: Microsoft Windows
_______________________________________________________
Details:
>> [a, b, c] = ginput (1)
error: ginput_keypressfcn: mx_el_eq: nonconformant arguments (op1 is 1x7, op2
is 1x6)
error: called from
ginput>ginput_keypressfcn at line 130 column 3
ginput at line 81 column 7
fltk / qt makes no difference. Works fine on gnuplot, save Alt-<key>.
Matlab (I just checked on r2014a):
Plain "i" returns 105
Shift-i returns 73
Ctrl-i returns 9
Alt-i returns 105
Octave/gnuplot gives the same as Matlab except Alt-modifier => gnuplot doesn't
react to that.
In 3.8.2 this used to work on fltk (hence the "regression"), be it that
ginput() there couldn't differentiate e.g., shifted keys: Shift-i still
returned 105 for button value, rather than 73
On 3.8.2 ginput() didn't work yet with Qt.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?44833>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #44833] ginput doesn't correctly process shift/ctlr/alt key combinations,
Philip Nienhuis <=