-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lua error add filepath to error message #4931
Comments
This is difficult, as the script is not there! |
can it be read from the widget settings in screen configuration ? IE, if screen 2 has widget looking for radio:\scripts\some_widget and this doesn't exist, then it can reference this screen or exact widget ? like "Screen2 Widget <some_widget> not found" |
Not exacly, Screen2, Widget 1 will use the script with the key "mylua", but it doesn't know which is the script which exports this key! |
Oh, I see. Well it may still be helpful to have the key name displayed by the error, and so long that the key name is unique for the widget, the user should be able to know which lua script is missing and which they need to reinstall I'm just trying to find some way to make the error messages more user friendly because during several updates this has been a common issue that many users will post or ask about the various lua errors |
Right the key should be displayed. I will check it is. On your screenshot it seems empty! |
When a lua script is outdated (or missing) and throws a system error such as "Lua widget key '' not found", it will be really helpful to have the file path of the script which is causing the error (or widget filepath that is missing)
Right now we can only tell people to delete the lua scripts one by one until the error goes away, and then to put them back on the radio except for the one which causes the error
This is a terrible way for people to have to deal with these errors.
Additionally we should consider to add a "Disable script" option to the error which can automatically disable the lua script by moving into a separate folder such as radio:/scripts_disabled
These errors are particularly frustrating to users after new ETHOS updates since they don't know which script is causing the error
The text was updated successfully, but these errors were encountered: