databaseManager.setAutoSave(false): how does it work?

Classic Servoy
1

I tried to use databaseManager.setAutoSave(false) in rc2 running on MacOS X 10.4.7, but I could not understand how it works.

I put it in a start up method for the application, however records were still saved without issuing any saveData command.

I then set auto save to false in an on load method, but records continued to be saved.

Anybody could explain to me how to set auto save to false and make it work?

2

I haven’t used it (yet) but from what I read in the sample you should be able to use it like you do. What happens when you call it onRecordSelect? Just to see what happens… Are you sure you never trigger a commit or saveData()?

Don’t know if it is applicable here but controller.saveData() does exactly the same as databaseManager.saveData(). In fact the last is better in its place since the first also saves ALL data and not only that of the frontmost controller.

3

I’m also finding that setAutoSave(false) isn’t working as advertised, and I’ve uploaded a sample solution to the support system demonstrating the problem. Also having problems with onRecordSave event - have reported that too.