(Works for me) Bug(s) in Prefs/WBStartup
Posted: Tue May 17, 2022 3:54 pm
WBStartup 53.30 (18.02.2018)
Steps to reproduce:
- Start up WBStartup
- Double-click on an entry to bring up Information and enter STARTPRI=-127 in the tooltypes
- Save
1st bug
- Double-click again and there will be another entry in the tooltypes with STARTPRI=128 (never entered that)
(btw, sometimes when i enter two different tooltypes. e.g. TOOLPRI=-1, then that second tooltype shows up duplicated as well)
2nd bug
- Do the 1st bug steps and after they were saved, there is an erroneously set empty newline at the bottom
(even if the newline was deleted beforehand)
3rd bug (but that may have been a coincidence)
Have AmiUpdate installed, running and set in WBStartup
-Repeat the 1st bugs step a few times and you'll eventually get hit by an error window
AmiUpdate
Unexpected error parsing XML file at line 2727 column 1
Error code 5: unclosed token
Seems as if WBStartup erroneously reads programs XML settings?
(No XML settings were saved btw, it did report the error on reading them or so it seems...why it did that, is beyond me, though)
Steps to reproduce:
- Start up WBStartup
- Double-click on an entry to bring up Information and enter STARTPRI=-127 in the tooltypes
- Save
1st bug
- Double-click again and there will be another entry in the tooltypes with STARTPRI=128 (never entered that)
(btw, sometimes when i enter two different tooltypes. e.g. TOOLPRI=-1, then that second tooltype shows up duplicated as well)
2nd bug
- Do the 1st bug steps and after they were saved, there is an erroneously set empty newline at the bottom
(even if the newline was deleted beforehand)
3rd bug (but that may have been a coincidence)
Have AmiUpdate installed, running and set in WBStartup
-Repeat the 1st bugs step a few times and you'll eventually get hit by an error window
AmiUpdate
Unexpected error parsing XML file at line 2727 column 1
Error code 5: unclosed token
Seems as if WBStartup erroneously reads programs XML settings?
(No XML settings were saved btw, it did report the error on reading them or so it seems...why it did that, is beyond me, though)