Yes, but as I said the Settings screen/.skin is generic for all new versions of my plugin.
The settings screen/.skin as designed can handle 4 input units, 2 Numeric +/- and 4 boolean true/false options.
Obviously not all plugins will have that many, but the idea is the capacity is there and the standard is the same, so when a user goes to one of my settings screens it will be familiar.
If you look at my iDrive skins I have also used that format for setting the WiFi Manager settings.
And because El C named his settings .skin wifiman_settings.skin it has made it easy for me to add a button to pluginmanager that pulls the plugin selected in the list, add _settings to it's name and it goes to the settings skin of that plugin (if one exists).
It's all about making it easy and consistent for the user, and the more than can be doen whilst in RR the better.
ok i understand , must admit not looked at your new idrive yet ,
finally Q??? on this matter , i'm by far not a vb coder, so this may be a dumb Q???/
can the cmds for the settings screens and file ext , screen have both Load and Menu options allowing the skinner a bit more freedom
this is 1 thing that restricts the skinning process in many PI's
Riderunner / Genesis
Plugin Breaker in test BassRR Plugin Player, Wifiman_NET
New Home for Genesis & BassRR :adding to site ,, Hellfyre night
Bassrr Beta Release :Version 1.3.7
Movie_info Release :Version 3.1.0
Wifiman_NET:Version 1.0.0
Every Future, Needs A Beginning
I can add commands that will use menu instead of load.
But I'm not sure how a menu will like then loading a menu on top.
Or whether a menu can har OSK pop up from it.
Both of which will need to happen in this case.
Posting Permissions
LinkBack URL
About LinkBacks
Reply With Quote
Bookmarks