Do plugins need to support the "Slick" skin now?

[fla]

I've noticed some users struggling to get plugins working because they are set to use the "Slick" skin and many plugins only supply a "Blue" skin.

• Is the default PVRX2 skin on a new install the "Slick" skin?
  
• Isn't the "Blue" skin the only required skin for plugins?
  
• Did I miss the policy change? (I don't follow the forums that much except to help XSuite users)
  

[sub]

As far as I'm aware, building blue skins only should be enough, since the fallback mechanism should take care of the screens that dont have dedicated slick skin files. Most of the built in screens dont have any slick skin files, and just rely on the fallback mechanism.

I'm not sure if you might be encountering some problem with the old legacy plugins though?

[fla]

In a legacy plugin if the current skin is Slick:

Code:

PluginHelperFactory.getPluginHelper().GetSkinRootDirectory()
"C:\\Program Files\\Devnz\\GBPVR\\skin\\Slick\\"

PluginHelperFactory.getPluginHelper().getStandardSkinDirectory()
"C:\\Program Files\\Devnz\\GBPVR\\skin\\blue\\"

When the current skin is blue they both return the same thing.

Would this be the proper way to implement a fallback mechanism in a legacy plugin?

Code:

string skinDir = PluginHelperFactory.getPluginHelper().GetSkinRootDirectory() + getSkinSubdirectory();
if (!System.IO.Directory.Exists(skinDir))
{
    skinDir = PluginHelperFactory.getPluginHelper().getStandardSkinDirectory() + getSkinSubdirectory();
}

Otherwise what's the proper way to create a GBPVR.Public.SkinHelper instance in a legacy plugin since GetSkinRootDirectory() returns a non-existing directory by default in PVRX2?

[sub]

Would this be the proper way to implement a fallback mechanism in a legacy plugin?

To be honest, I dont know. Its not something I've tested.

It might just be a matter needing a 'slick' subdirectory created in the old legacy .\skin directory.

[fla]

Thanks.