[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: |
Pantxo Diribarne |
Subject: |
[Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy |
Date: |
Wed, 13 Jun 2018 10:01:22 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 |
Follow-up Comment #13, bug #50295 (project octave):
@jwe: about comment #5. Matlab deletes the current prompt, displays the string
and then redraws the prompt. After one click it looks like
>> foo = @(h, e) disp ('foo');
>> h = figure ();
>> set (h, 'buttondownfcn', foo);
foo
>>
Then if I click again it looks like
>> foo = @(h, e) disp ('foo');
>> h = figure ();
>> set (h, 'buttondownfcn', foo);
foo
foo
>>
For completeness, with a "numbered" prompt it would look like this in Octave
octave:1> foo = @(h, e) disp ('foo');
octave:2> h = figure ();
octave:3> set (h, 'buttondownfcn', foo);
foo
foo
octave:4>
So from that point of view, the answer to your question "but how much output?"
is: delete the prompt, display output, redraw the prompt for each output. This
would also avoid the first output to be displayed after the prompt as it is
currently the case in octave:
octave:1> foo = @(h, e) disp ('foo');
octave:2> h = figure ();
octave:3> set (h, 'buttondownfcn', @foo);
error: @foo: no function and no method found
octave:3> set (h, 'buttondownfcn', foo);
octave:4> foo
foo
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50295>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy,
Pantxo Diribarne <=