Re: Passing variables up to the GUI

[Daniel J Sebald]

On 04/12/2013 10:14 PM, Daniel J Sebald wrote:

> On the GUI side and interface, there is a bit more work. I suppose there
> would need to be two queues, maybe one for the user input commands, and
> one for the "callback" commands. The GUI needs to queue up the command
> and also what object wants the data. The object that wants the data has
> to know what it asked for and how to interpret it. Maybe it asks for
> "x". Or maybe it asks for "size(x)". Or maybe "x(1:10,21:30)".

Followup thought.  Maybe the thing to do is instead of attempting the 
"corefeval" function first, is to just create some octave_value object 
on the core side, say a small matrix, and see if that can be sent over 
by reference using

emit octave_result (qobject, ovres);

to some hunk of code on the GUI side that will just toss up a dialog 
showing the contents of the object.  I'll just place it in one of the 
existing callback functions.  It will create some annoying, odd dialogs 
randomly appearing, but it would just be proof of concept.  I'll try 
that late next week sometime.

Dan