|
From: | Daniel J Sebald |
Subject: | Re: eliminating GUI event listener class |
Date: | Mon, 08 Apr 2013 11:58:05 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16 |
On 04/08/2013 11:49 AM, Daniel J Sebald wrote:
On 04/08/2013 11:23 AM, John W. Eaton wrote:The only thing we are using the event listener object for is to handle cleaning up the GUI when we exit from Octave. I tried to switch that to using signals and slots but was not successful.
Something else I should say. I do think that the event listener isn't necessary. That is, most everything I can think of on the GUI side can be event driven by signals. However, going the other direction is a different issue. I think things that go to the Octave thread have to be queued in almost all cases. The issue there is that Octave can be busy for a long time and waiting for a response from the Octave thread should be avoided. I'll write back with more this afternoon.
Dan
[Prev in Thread] | Current Thread | [Next in Thread] |