Skinning error fall back page

[Hairy]

I've ment to post this suggestion several times before, but a recent post in the Plugin/Skin support forum has spurred me on.

As always I make the suggestion completely ignorant to whats involved in actually doing it.

It would be good if skins could have a self contained error section. That is, graphics and formatting to display a page if and when GB detects a unrecoverable skinning error. It could display the background and a simple message explaining that GB had experienced an error in it's skinning environment and to check for skin and/or plugin compatibility. It would be great if there was also an exit and restart app button. Sometimes skinning errors can cause GB to crash requiring a forced shutdown, I think this would be a much softer landing.

Cheers

[psycik]

I think things changed a bit with pvrx2 - I'm sure there used to be a bit more fall back.

So yes I think if should be something that gets looked at.

When calling a render from a plugin i don't think we always know the state of the skin helper - which is the bit the has loaded the skin.xml file - I could be wrong, but it also could just be a matter of not catching an error.

I know in some of my stuff I do catch the error, but the only message we're given back from gbpvr is an "Object reference not found" it would be nice it we can be given some idea of what was missing, ten we could potentially ad a popup with a skin error.

[herrmannj]

I'v seen trat JavaWiz provide a helper with its dlls.

From my understanding the code below provides a fallback:


// Create the skin sub directory and copy the skin files is needed.
// Note that the populateSkinDirectoryIfNeccessary routine will not overwrite the files if they already exist in the
// destination skin.
WizInfo.populateSkinDirectoryIfNeccessary(getSkinSubdirectory());

[Hairy]

Cheers psycik

When calling a render from a plugin i don't think we always know the state of the skin helper - which is the bit the has loaded the skin.xml file - I could be wrong, but it also could just be a matter of not catching an error.

I know in some of my stuff I do catch the error, but the only message we're given back from gbpvr is an "Object reference not found" it would be nice it we can be given some idea of what was missing, ten we could potentially ad a popup with a skin error.

I think this lands firmly in the "completely ignorant of whats involved" part for me

I know from my dalliances with xmls (I've been known to remove commas and inverted commas and even double up on alpha levels for colours :eek Stuff like this can sometime cause GB to hard crash (and even with addon plugin compatibility you can be dumped back to the main menu). I just thought that for a slightly more user friendly experience it would be cool if GB was able to display a skinning error page. In a more general global way, not to go as far as what the fault was but for of a soft landing when it does experience one. But as I said I've no idea on the feasibility.

It's good to learn more about what's involved, so thank for the response, appreciate it.

Cheers