Re: QSettings deleted by singleton-cleanup mechanism

[Mike Miller]

On Wed, Jun 17, 2015 at 16:26:06 -0500, Daniel J Sebald wrote:
> On 06/17/2015 03:56 PM, John W. Eaton wrote:
>>
>> On 06/17/2015 03:43 PM, Daniel J Sebald wrote:
>>>
>>> Currently the GUI's QSettings are instantiated and deleted by the Octave
>>> worker thread using the singleton-cleanup mechanism. Can that be
>>> changed? Was there a reason to have the worker, which is in another
>>> thread, do this?
>>
>>
>> I haven't looked, but was this changed when we tried to make it possible
>> to open Qt plot widgets when Octave is started with --no-gui (the
>> command line interface but linked with the Qt libraries)?
>
>
> Oh, it probably was.  I think there are other ways that could be done, or it
> might not even be necessary to have a QSettings in that case if nothing is
> being used by it.  I'll investigate.

I looked into it a little bit. I think it was done that way far before
that more recent change.

Both the "welcome wizard" and the Qt plot backend need access to the
settings, so the settings definitely do need to be around and
accessible when the main window is not up yet (or ever).

-- 
mike