How to See Error Messages?
-
When HISE encounters an error running user scripts, the application bravely continues, but often doesn't display the information on the Console. Is there a way to get information about these errors? I see information in the documentation about a debugger, but it's a little scant. Thank you, kindly.
-
@clevername27 What kind of errors? I don't think I've found a situation where there is a script error and it isn't reported in the console.
You can enable the debug logger through project preferences, I've never used it. You can also enable it through scripting for use in your compiled project which can be useful when sending your plugin to beta testers.
-
@d-healey Thank you for your response, David. In my own experience, errors are often not reported — execution continues, but whatever function was executing fails. A common example is errors in LAF functions simply cause all styling in the LAF to fail. But it could be anything (e.g., variables, properties, methods, members, references and/or functions that have not been properly declared, initialised or accessed). Or bugs in HISE itself (e.g., incorrect project folder directory, xml file reading errors). I spend most of my time in HISE debugging these situations — the only way to locate the issue to successfully comment out code until everything executes as expected. In other words, the errors are likely caught by the HISE code, and handled correctly such that code can reasonably continue executing — but the step of communicating the errors simply hasn't been implemented. In some cases, depending on other code execution, errors may appear that previously did not. Some of this may be related to JUCE, though I'm guessing it has robust error-checking. (I'm not complaining about this, simply clarifying in regard to my question.)
-
@clevername27 Could you put together some example snippets we could examine?
-
@d-healey Thank you. Sure, just see our threads on reading an XML file, and the project file directory string not resolving.
-
@clevername27 If I remember correctly the project folder wildcard did resolve correctly within HISE. It was only in the exported plugin that it failed, or are you referring to a different issue?
With the XML there is no script error. It works as it should, it's just that it seems to be designed for a very specific XML file layout which makes it useless.
-
@d-healey Thank you again for your replies, David. I don't think pursuing this particular issue will be fruitful.
EDIT—to explain myself, my HISE script is over 15,000 lines at this point. The difficulty of extracting examples is part of the price I pay for this. It's a scripting language, and probably not intended for that stuff (although HISE seems to have no problem with it, as a nod to its quality). I have the non-reporting of issues constantly, and I can't imagine it's not something everyone deals with. It's possible, of course, that I'm not doing something correctly…sort of. This was the case in the IDE of all the open files not being saved when you explicitly choose to save…ok, I understand what I need to do, but that's still a major bug (which aren't limited to strict parameters of code execution). And of course, without the consistent help of people like you on the forum (in this case, I think it literally was you), I'd be lost. So, I don't want to argue with you, but instead gratefully accept your expertise and generosity.