Home » U++ Library support » U++ Core » Xmlize problem with Nulls
| Xmlize problem with Nulls [message #44455] |
Fri, 13 March 2015 13:25  |
 |
koldo
Messages: 3432
Registered: August 2008
|
Senior Veteran |
|
|
Now when a Null EditNotNull field is Xmlized, an error is set in the xml file, so when the xml file is opened a "invalid Value type" error is thrown so xml file is not opened.
The reason is that EditFields get data from Scan(), and it returns "error" type and an error message ("Null value not allowed.") when field is Null (or out of max/min limits, with "Number must be between %d and %d." message).
IMHO if an EditMinMaxNotNull or EditNotNull field is saved in a xml, the original data should be saved instead of an error. Other way could be to ignore ERROR type values when opening a xml file, instead of throwing an error.
What do you think?
Best regards
Iñaki
[Updated on: Fri, 13 March 2015 13:31] Report message to a moderator |
|
|
|
|
|
|
|
|
|
| Re: Xmlize problem with Nulls [message #44487 is a reply to message #44484] |
Mon, 16 March 2015 17:32  |
|
koldo
Messages: 3432
Registered: August 2008
|
Senior Veteran |
|
|
Thank you Mirek
That is true. My problem was that a new variable was not initialized by default, so it was saved inadvertedly in invalid state so XML file was in fact corrupted.
Best regards
Iñaki
|
|
|
|
Goto Forum:
Current Time: Sat Apr 26 08:47:32 CEST 2025
Total time taken to generate the page: 0.02966 seconds
|
Members
Pages
Help
Register
Login
Home
