Not sure if it happens every time, but if I choose NO when asked to save the changes on a method, the changes are saved anyway…
OSX.2.8, 1.2rc8
Not sure if it happens every time, but if I choose NO when asked to save the changes on a method, the changes are saved anyway…
OSX.2.8, 1.2rc8
Can’t reproduce it on XP.
It doesn’t save the method..
Do you have a test case?
Johan,
Can the reason be that, when we ‘verify’ a method, the results are saved? I know that I had issues with disabled menus and lost all my changes due to forced restarts all the time.
The (temporary) solution you gave us, OS X users, about 3 weeks ago was saving the changes with every ‘verify’…
IT2BE:
Johan,Can the reason be that, when we ‘verify’ a method, the results are saved?
It could be. I’ll try to reproduce the problem.
Verify does save the method to the database now yes.
After a verify you can only go back to a previous change with undo and verify again.
You shouldn’t loose any code anymore with the current builds..
(except the one that you didn’t verify/save and somehow servoy get’s killed)