octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debugging and the GUI Editor; Qt help needed


From: John W. Eaton
Subject: Re: Debugging and the GUI Editor; Qt help needed
Date: Thu, 28 Mar 2013 14:21:27 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11

On 03/28/2013 02:08 PM, Daniel J Sebald wrote:
On 03/28/2013 02:43 AM, John W. Eaton wrote:

It would be helpful if people could test these new features. There is no
need to report the problems I've listed above, but if you find other
things that don't work correctly, let me know. Or if you'd just like to
say, "Wow, these new features look awesome!" that would be fine too.

I haven't compiled and run yet, so I assume it looks awesome.

I looked at the code, though, e.g.,

http://hg.savannah.gnu.org/hgweb/octave/rev/389b09a914e2

and I would suggest that we try to not introduce callbacks in the way
you have done. The problem with the callbacks is it is connecting two
threads with functions. We should be using the Qt signal/slot mechanism
across threads. Otherwise there is a good chance we're unnecessarily
restricting capabilities and possibly making programming more difficult
down the road.

Then can you please provide an example that shows how to do that for one of these cases? I don't mind changing the way things are done if it really does make a difference, but I need some pointers here as I'm almost clueless about the proper way to do Qt programming. Just saying "use signals/slots" doesn't help me much.

jwe



reply via email to

[Prev in Thread] Current Thread [Next in Thread]