NTLite doesn't recognize bad XML formatting in saved presets

garlin

Moderator
Staff member
I made a simple error when hand editing a preset, and added extra "<" by mistake:
<AutoIsoLabel>Win7 SP2 (ESU Ready)<</AutoIsoLabel>​

List view stopped displaying my file, and refresh didn't work either. You can import the file, NTLite saves a copy but still won't list it. So the XML parsing isn't warning you that your file is corrupted. The formatting error is my fault, but NTLite should complain instead of silently ignoring it.
 
Yeah, I've made that mistake before too, and wondered why the Preset I just saved doesn't show up in NTLike's list.

Perhaps the list could show ALL .xml's in the Preset folder, default them to red color, and then, only if they validate, turn them to black.
 
No, just .xml files containing the header "urn:schemas-nliteos-com". Other XML files could be unrelated configs.
 
I thought the only xml's in the Preset folder were all "presets." But if not, then whatever nuhi has to parse to make Presets show red or green.
 
You're right. I modify files directly in the Preset folder, because they're owned by Administrator. It's a pain to export, edit, and import when you can just do it as Administrator.
 
Thanks, added support for corrupted preset files in the next version, you can easily right-click - Edit (auto-elevated) as normal.
Will ping here when released.
 
I made a simple error when hand editing a preset, and added extra "<" by mistake:
<AutoIsoLabel>Win7 SP2 (ESU Ready)<</AutoIsoLabel>​

List view stopped displaying my file, and refresh didn't work either. You can import the file, NTLite saves a copy but still won't list it. So the XML parsing isn't warning you that your file is corrupted. The formatting error is my fault, but NTLite should complain instead of silently ignoring it.
Yeah, I've made that mistake before too, and wondered why the Preset I just saved doesn't show up in NTLike's list.

XML Validator Will save you from headaches.
 
XML Validator Will save you from headaches.
Agreed. But usually it's just a simple mistake on my part. (I forget to close a string with a caret.) And since NTLite clearly knows what validates and what doesn't (since it only displays valid xml), it seems easy enough to paint anything else in the Preset folder as red.

However, if you're suggesting using XML Validator to find mistakes, then I also agree. A good idea. (I am still thanking you for steering me onto WinMerge.)
 
Last edited:
However, if you're suggesting using XML Validator to find mistakes, then I also agree. A good idea. (I am still thanking you for steering me onto WinMerge.)

Also Notepad++ helps a lot because of the coloring feature.
 
I feel like a dinosaur using 'diff' from Cygwin.

cmon baggy get with the beat
yh_-we_0MNP2FsiATakMtM1WP0WREbm-s5YRvJXkoa1GZcg_NfAvcEamQ0Do87S9zLm6TmxDeb56zi18xETlaFft0kiRcf1TIlBAPlgzEt4MDMEk4pNDKxY8
 
Last edited:
Back
Top