Page 2 of 2

Re: File database is locked

Posted: Fri Mar 22, 2019 4:34 am
by polinom
CintaNotes Developer wrote:Thanks a lot! According to the log, database disconnect never happens.
Most probably this is because the program is kept on screen and is never minimized to tray.
When the program is on screen, it keeps database locked to prevent database reconnection freeze when the user switches back to it.


Why can this happen? When I made a log, the program was minimized to tray.

Re: File database is locked

Posted: Fri Mar 22, 2019 11:07 am
by CintaNotes Developer
polinom wrote:Why can this happen? When I made a log, the program was minimized to tray.


I'm perplexed as well. From the log alone, I'd say that notebook disconnect is simply turned off. Are you sure that the cintanotes.settings file
that you attached earlier is really the one that is in effect?

Could you please try the same on a separate portable instance of CN?

Re: File database is locked

Posted: Fri Mar 22, 2019 9:28 pm
by polinom
CintaNotes Developer wrote:
polinom wrote:Why can this happen? When I made a log, the program was minimized to tray.


I'm perplexed as well. From the log alone, I'd say that notebook disconnect is simply turned off. Are you sure that the cintanotes.settings file
that you attached earlier is really the one that is in effect?

Could you please try the same on a separate portable instance of CN?


When I saved the database to the Yandex disk folder, the path to the database automatically changed in the cintanotes.settings file. I think CN takes the settings from this file. Tomorrow I will try to install a portable version of the program.

Re: File database is locked

Posted: Sat Mar 23, 2019 10:06 am
by CintaNotes Developer
Ok will be waiting for the results!

Re: File database is locked

Posted: Sat Mar 23, 2019 6:56 pm
by polinom
All is still, there is no access to the database. I enclose a log: https://yadi.sk/i/5FvLGBhGeyKg9w

Re: File database is locked

Posted: Mon Mar 25, 2019 2:40 pm
by CintaNotes Developer
Thanks for the log! I was finally able to reproduce the issue. Indeed in some cases the code setting the disconnection timeout can be skipped.
Will releasea fix soon!