-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 08 November 2002 01:50, Kaleb Pederson wrote:
> I'm using a global QSettings object throughout my application. For some
> reason, when the program closes, the destructor on my QSettings object is
> not getting called. As it is the destructo
On Thursday 07 November 2002 10:14 pm, Boudewijn Rempt wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> It might be my Java heritage, but I've never trusted destructors...
> Couldn't you just connect the LastWindowClosed signal to the save method?
> Why I personally to is to write the s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 08 November 2002 07:42, Kaleb Pederson wrote:
> On Thursday 07 November 2002 10:14 pm, Boudewijn Rempt wrote:
> >
> > It might be my Java heritage, but I've never trusted destructors...
> > Couldn't you just connect the LastWindowClosed signa
On Fri, 2002-11-08 at 01:50, Kaleb Pederson wrote:
> I'm using a global QSettings object throughout my application. For some
> reason, when the program closes, the destructor on my QSettings object is not
> getting called. As it is the destructor that actually writes everything to
> disk (in o
On Friday 08 November 2002 12:44 am, you wrote:
> On Fri, 2002-11-08 at 01:50, Kaleb Pederson wrote:
> > I'm using a global QSettings object throughout my application. For some
> > reason, when the program closes, the destructor on my QSettings object is
> > not getting called. As it is the destr
On Fri, 2002-11-08 at 10:34, Greg Fortune wrote:
> On Friday 08 November 2002 12:44 am, you wrote:
> > The reason you're having problems is most likely because there is no
> > such thing as a destructor in Python. I assume that you, like many
> > before you, are treating the __del__() method as a d
On Friday 08 November 2002 01:59 am, Fredrik Juhlin wrote:
> On Fri, 2002-11-08 at 10:34, Greg Fortune wrote:
> > On Friday 08 November 2002 12:44 am, you wrote:
> > > The reason you're having problems is most likely because there is no
> > > such thing as a destructor in Python. I assume that you,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 08 November 2002 15:38, you wrote:
>
> I agree that it shouldn't be the only way to go. I would definitely
> prefer to have a function that I can call that would write to disk. The
> source code reveals, however, that a sync() call is only
>> I agree that it shouldn't be the only way to go. I would definitely
>> prefer to have a function that I can call that would write to disk.
The
>> source code reveals, however, that a sync() call is only done in the
>> destructor.
>
>I've never had a problem with lost settings, so I guess the
>On Fri, 2002-11-08 at 01:50, Kaleb Pederson wrote:
>> I'm using a global QSettings object throughout my application. For
some
>> reason, when the program closes, the destructor on my QSettings
object is >not
> getting called. As it is the destructor that actually writes
everything >to
>> disk
On Friday 08 November 2002 07:42, Kaleb Pederson wrote:
On Thursday 07 November 2002 10:14 pm, Boudewijn Rempt wrote:
>
>
> Hmmm... What I do is to create a Python class with the settings as
member
> variables. That makes it easier. But still, the Qt documentation says:
>
> A typical usage patter
Am Freitag, 8. November 2002 16:38 schrieb Kaleb Pederson:
...
> >
> >Maybe I was just lucky, and have the QSettings object call the
>
> destructor.
>
> >Anyway, it's one part of my application where I've never had
> > problems.
>
> Maybe. My settings had been working great for the last couple m
12 matches
Mail list logo
