Re: Using qt dialogs in Octave 4.0.0

[Pantxo]

Sergio wrote
> Hi Mike,
> First at all thanks for your answer.
> Some time ago (when octave had no official GUI interface) I worked to do
> some integration between qt libraries and octave. But I used pipes and
> don't work fine under Ms Windows. Now, with the new version of octave gui
> (qt based) I want to return to this work making some GUIs for m scripts
> files.
> This is my motivation, but I don't find information about how can do this.
> I try for this way because the qt library was distributed with the octave
> windows binaries but I'm not sure about what is the best way.
> You know where can I find some link about how can use some  ui*
> interpreter
> functions to create dialogs and interfaces directly from m-files?
> Thanks a lot.
> Sergio
> 
> 2015-07-08 4:39 GMT-03:00 Mike Miller <

> mtmiller@

> >:
> 
>> On Tue, Jul 07, 2015 at 14:32:22 -0300, Sergio wrote:
>> > I'm using Octave 4.0.0 under MS Windows 7 (64 bits), and I'm building a
>> GUI
>> > based in Qt for some parameters of m script. Basically I'm using Qt
>> Creator
>> > to build a dialog skeleton, then use uic command (from Octave binary
>> > distribution) to make the user interface header, and compile the dialog
>> > sources. Then use the header and the object file to make the call from
>> a
>> > oct file (the files are attached).
>>
>> That certainly seems like something someone may want to do, but there is
>> probably no good way to integrate such a Qt oct-file with the Octave GUI
>> currently.
>>
>> > I think the problem is because the second window don't have reference
>> to
>> > the handle of the main window of the GUI. In qt, this is simplement
>> taken
>> > from "this" keyword when a second dialog is created from the main
>> window.
>> > But in this escene, with octave and the GUI, how can access the handle
>> the
>> > main windows from a oct file?
>>
>> Probably what you're looking for is some API in the Octave library to
>> get a reference to the Octave GUI window, maybe even other subcomponents
>> of the GUI? That does not yet exist in a well-defined public header
>> file.
>>
>> I think the expectation is that most users will use the ui* interpreter
>> functions to create dialogs and interfaces directly from m-files without
>> the need to compile an oct-file that uses Qt.
>>
>> Not saying that what you're doing is wrong, but I don't think Octave's
>> GUI is written in a way to support it yet, possibly no Octave developers
>> anticipated that someone would want to do this.
>>
>> HTH,
>>
>> --
>> mike
>>
> Hi Sergio,
> 
> Can you bottom post (write at the bottom of quoted text) as I do and as is
> customary in octave mailing lists.
> 
> The uixx functions are currently undocumented but work pretty well. My
> advise would be to look at Matlab doc for uicontrol. Most of the uicontrol
> "style" I tested in octave actually work, they only need to be documented
> properly. If you have time to test and report what 
*
> works
*
>  here, you could help writing the documentation :-).  
> 
> Now about instantiating qt widgets directly from oct files, did you try to
> create widgets with NULL parent (parent = 0). That is currently what qt
> figures do as they are separate from the main GUI, see e.g. [1]. This may
> change in the future, if we want to handle some figure features from the
> main GUI, but there is currently no way to reference the main GUI window. 
> 
> Pantxo 
> 
> [1]
> http://octave.org/doxygen/4.0/dc/db6/classQtHandles_1_1FigureWindow.html
> _______________________________________________
> Help-octave mailing list

> Help-octave@

> https://lists.gnu.org/mailman/listinfo/help-octave





--
View this message in context: 
http://octave.1599824.n4.nabble.com/Using-qt-dialogs-in-Octave-4-0-0-tp4671460p4671490.html
Sent from the Octave - General mailing list archive at Nabble.com.