[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:14:34 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0 |
Follow-up Comment #8, bug #50295 (project octave):
To Mike: the problem for me is point 2. As I said in the previous comment, I
intended to add a callback to the datacursor of Pantxo Diribarne, but this
doesn't work as expected because the user has to press enter any time he
clicks on the menu item, otherwise the data cursor does not appear.
Perhaps, my approach is not the correct one, so if there is some alternative,
please tell me...
_______________________________________________________
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, 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 <=
- [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