[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI
From: |
Roland Baudin |
Subject: |
[Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy |
Date: |
Fri, 17 Feb 2017 03:11:39 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0 |
Follow-up Comment #7, bug #50295 (project octave):
To jwe: yes, same behaviour with your example. OK, I understand this is the
correct and expected way.
In fact, my problem is the following. I thought it was simple to add a
callback to a function to the figure window menu (the function I was
interested in is the datacursor() function written by Pantxo Diribarne, see
http://octave.1599824.n4.nabble.com/Data-cursor-in-Octave-td4681801.html).
So I added the menu callback but it doesn't work properly because the user has
to press enter in the command window after he has clicked somewhere on the
figure to put the datacursor.
Perhaps, there is some method to call to simulate this enter pressing ?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50295>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy, Roland Baudin, 2017/02/13
- [Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy, Mike Miller, 2017/02/14
- [Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy, Roland Baudin, 2017/02/15
- [Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy, Mike Miller, 2017/02/15
- [Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy, Roland Baudin, 2017/02/16
- [Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy, John W. Eaton, 2017/02/16
- [Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy, Mike Miller, 2017/02/16
- [Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy,
Roland Baudin <=
- [Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy, Roland Baudin, 2017/02/17
- [Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy, Mike Miller, 2017/02/17
- [Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy, Roland Baudin, 2017/02/18
- [Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy, Mike Miller, 2017/02/19
- [Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy, Roland Baudin, 2017/02/19
- [Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy, Mike Miller, 2017/02/19