(about keeping menus on errors)
Quote:
Originally Posted by geek1011
The issue with that is it makes reloading a bit more complicated, but I'll consider it for later.
|
I can see how that could be messy. And ironically, debugging was made even more frustrating because sometimes it didn't reload without a reboot anyway. A reload option would also have been nice for the debug cycle. A reload (or reload/cancel) from the error dialog would be perfect, but no idea if that's possible, and if it actually reloaded after every usb eject, it wouldn't be needed.
Quote:
|
Are you sure you included the trailing colon? If so, what was the exact error message?
|
I actually converted it from the old nickel_misc:web_browser format, and then read the docs, changed it to nickel_browser without the trailing colon, read the docs again, and then added the colon.
So I've tried it all ways, although it is possible it didn't reload on some of the attempts and I didn't notice. Also possibly an early error made it stop reloading and it took a reboot to clear that.
The error was something like parse error in field 5 unexpected end of line.
edit: I'm sure the last version I tested before I got it working had the trailing colon and so it had a reboot immediately before I gave up on the line I pasted.