|
From: | Mike Miller |
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 12:38:53 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0 |
Follow-up Comment #9, bug #50295 (project octave): I'm sorry I don't really understand what the data cursor on a plot has to do with what is printed to the command window or whether the user has to press Enter. As I understand it the data cursor is a tooltip that appears on a figure window when the figure area is clicked. I don't see how that requires any kind of display or interaction on the command window. If it's just for debugging while implementing this function, then I don't see any problem with the current behavior. If pressing Enter in the command window is required to somehow get the tooltip to appear on the figure window, then that looks like a different problem from just getting the prompt to be redrawn. You may have run into a different problem and assumed that it's for the same reasons as what you describe here, while the example shown here doesn't seem to be a bug at all. It seems more likely to me that it's because you are calling an m file function that sends a signal to the Qt figure thread to draw a text box. Instead maybe the data cursor should be done entirely in libgui without making such a callback to the interpreter. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?50295> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |