Changes:
[fix]-empty number fields become null in database instead of 0
[fix]-tabpanel hide did not hide in web output
[fix]-html in tab text not working
[enh]-media fields now working in web output
[enh]-possible to disable all the autosave with databaseManager.setAutoSave(…)
[enh]-data edits are possible to revert/cancelled without transaction databaseManager.rollbackEditedRecords()
[enh]-controller.focusFirstField() //does focus the first field from tab seq in the body part
[enh]-readOnly JS support on all web client form components
Is anyone playing around with this alpha? I did some playing around with it last night and ran into many strange errors in existing solutions.
On startup, I get an error that the onsolutionLoad method has an error, but cannot figure out why. In earlier versions (2.2.2) it worked fine.
Then I tried running the debugger. All of a sudden, the enable/disable button of the debugger was gone and I had to restart Servoy.
Then I ran a method with debugger on. When the method called another method, this new method was not opened, but the debugger seemed to go into the new method anyway. What was really odd was that the little yelloy arrow that displays on which line you are when stepping though a method was behaving as if it was in the new method, while the code show was still the previous method (i noticed because the arrow was jumping up because it was in a loop in the new method, but there was no loop in the code of the displayed method where the arrow was visually moving).
After some unexplained errors occured, opening the solution again, or opening another would not be of much help anymore. Even other, simplier solutions would start giving error after error and the only solution then would be a restart of Servoy Developer.
Has anyone experienced this behavior? Or is it working flawlessly for everyone and do I need to keep digging?
The editting record change was major in this preview, other than that there are no big changes compared to 2.2.x
Could you Mail us your .log.txt when you run into issues?
When the method called another method, this new method was not opened, but the debugger seemed to go into the new method anyway.
That is, when the other method is situated in an other module.
I’ve informed Johan about this.
Temp workaround >> manually open the submethod before running the main method.
Pffff, so it’s not me seeing things that are not there…
Jan, while trying to come up with a sample logfile, I stumbled onto something in my solution that might cause the problem, so I’m in debugging mode now.
One possible reason for the solution failing, while it didn’t before in earlier Servoy versions might be the following:
The application.getsolutionName() sometimes returns the name of the Module to which the method in which the function is called belongs, instead of the SolutionName of the overall/main solution. This problem was there as well in earlier version, but it seems to happen more often now (in the 3.0a12 version)