Skip to main content

Topic: Themes for CUI/WSH show “SCRIPT ERROR” instead of buttons+progress bar (Read 1431 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
Themes for CUI/WSH show “SCRIPT ERROR” instead of buttons+progress bar
I seem to be having script issues with every Column UI theme that I attempt to install, despite not missing any components and following provided instructions (e.g. those provided with http://moosss4.deviantart.com/#/d5a121z).
The progress bar, the shuffle and replay buttons are all replaced by portions of a severe "SCRIPT ERROR" black-on-white image, depending on the element's size. I am new to foobar and am absolutely unfamiliar with its plugin ecosystem and scripting; am I missing some basic customization fact?

  • MordredKLB
  • [*][*][*]
Themes for CUI/WSH show “SCRIPT ERROR” instead of buttons+progress bar
Reply #1
I seem to be having script issues with every Column UI theme that I attempt to install, despite not missing any components and following provided instructions (e.g. those provided with http://moosss4.deviantart.com/#/d5a121z).
The progress bar, the shuffle and replay buttons are all replaced by portions of a severe "SCRIPT ERROR" black-on-white image, depending on the element's size. I am new to foobar and am absolutely unfamiliar with its plugin ecosystem and scripting; am I missing some basic customization fact?

Those are almost assuredly WSH Panel Mod panels. First I'd update to the latest version of WSHPanelMod. If that doesn't work you're going to have to look at the console and see what the errors are and try and fix them yourself.

  • Falstaff
  • [*][*][*][*][*]
Themes for CUI/WSH show “SCRIPT ERROR” instead of buttons+progress bar
Reply #2
let me add:
- first, update to the last version of WSH Panel Mod (except if the config provides the components to use)
- then check File>Preferences>Tools>WSH Panel Mod page, be sure to untick the 'Safe Mode' option
- and only after that, check the Console to see what is the line # in error and if you're not able to fix it by yourself, post this erreor message with line # to the config creator, it will surely help you because we don't like to leave bugs in our WSH jscript

HTH

EDIT: to view console, use Menu VIEW>Console
  • Last Edit: 11 September, 2012, 12:15:56 PM by Falstaff

Themes for CUI/WSH show “SCRIPT ERROR” instead of buttons+progress bar
Reply #3
Thanks to you both for the help despite having posted to the wrong thread.
Updating the WSH mod to the latest version caused the placeholders to change from "script error" to "aw crashed! :(", I guess that is a form of improvement. ;)

It also caused six WSH error windows of this format and varying first string to pop-up on startup:
Code: [Select]
"Scripting Engine Initialization Failed ({9D361AF4-DE5B-430C-A260-C24930CBE8A6}, CODE: 0x800401f3): Invalid class string".

(I suppose that would be one for every panel that failed to load.) Unfortunately a quick search for this kind of error didn't yield much. I checked the console but once again (as it did before upgrading the WSH mod) there is nothing but the standard report on load times.
The skins that I tried were mostly updated versions of legacy ones, so I suppose that weird issues are not to be unexpected; however, most comments e.g. on DeviantArt are not reporting any issue, which makes me guess that I am indeed missing something.

Anyway, I'll close the off-topic here and avoid bringing on the issue in the WSH thread (time is a-tickin'!). I reckon that I will be using the vanilla-ugly (but functional) UI until, hopefully, Windows 8 stirs the skin authors a bit.
Thanks again for the help. :)
  • Last Edit: 12 September, 2012, 12:17:02 AM by Neo-neostrobomantula