onTerminate is not called because your process is killed. At that point, it
doesn't matter, the kernel is going to clean up all your stuff.
Like I said, if you are getting a message about it not being closed, this is
because you created and use the object and released all references on it
before c
Thanks Dianne for your answers.
My problem regarding the database is that I need it during the
lifetime of the application. Now when you say that
Application.onTerminate() is not normally called, I have no place to
close it, other then open_and_close every time I need it.
Would that be a standar
onTerminate is -not- called under normal operation -- the process is just
killed. You are getting that message because you no longer have any
references on the database but nobody has closed it, and now the garbage
collector is eventually get around to it. You should close the database
when you a
Oh, also, when my process is killed while being in the background does
coming back from gallery restart the process jumping directly to
activity B? It's not in the documentation, that's why I need to ask
here.
Thanks.
On Sep 30, 3:52 pm, Dianne Hackborn wrote:
> Yes your process can be killed a
Ok, thanks.
Now, I use onTerminate to close the SqLite DB to avoid the error
saying that the database was opened but never closed. Is this error
something I need to be anal about or can I just ignore it. I know it
doesn't relate to my previous problem, but you mentioned that
onTerminate may NOT b
Yes your process can be killed at any time when it is in the background (and
onTerminate is NOT called).
On Wed, Sep 30, 2009 at 3:47 PM, gnugu wrote:
>
> Hi,
> When I start my application I prompt the user for the password and use
> it to instantiate my data adapter object that I will need thro
6 matches
Mail list logo
