|
From: | Dan Sebald |
Subject: | [Octave-patch-tracker] [patch #7990] Add builtin Qt equivalents of UI dialogs, i.e., , qterrordlg, qtinputdlg, etc. |
Date: | Wed, 03 Apr 2013 00:52:55 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15 |
Follow-up Comment #9, patch #7990 (project octave): I missed a comment: As for the eval/feval issue, that one doesn't seem like too much of a problem. If one builds Qt gui as part of Octave, then qterrordlg, etc. are built in. There is no way of messing up the path. I'm not real familiar with the fltk interface. But it should be possible to have fltk GUI ensure it can find the script files and make sure that location is part of the search path. If fltk can't find its supporting files, it could post a pop-up dialog "Cannot find supporting script files. The GUI will not function fully without them." After that if someone does try using a command without a script, Octave will give a fairly coherent error, e.g., "error: `gtkerrordlg' undefined". Keep thinking I guess... The callback flow is fine, it's just that Qt prefers to not use them: http://qt-project.org/doc/qt-4.8/signalsandslots.html _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/patch/?7990> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |