Shoutbox

That's true but it is not hard to write something small to convert it and it shouldn't effect the runnig of any script (unless they have been silly and edit the reg key for some reason).

I dont see how this should be so hard. In the registry just have a list of all the scritps and have two fields: one called users_enabled which will have a comma seperated list of all the users this script is enabled for and then users_show which has a comma seperated list of all the users this script will appear for.

Whenever a new user is signed in they are added to both these fields. They can then go to the Msg+ GUI and when they remove a script there name gets removed from user_show and user_enabled for that script and when they disable it, there name gets removed from user_enabled and re-added if they re-enable.

Alternately you could have the email address of the user and then under that you have scripts and under that have all the scripts. In scripts you have 2 default keys, status which either true or false which declares wheteher its enabled disabled. Rather then deleteing the folder for the script, you would have a key called "deleted" or something, the reason for this is you could easily integrate a settings function into Msg+ scripting which works like so, setting("setting_name", "setting_value");. This way, if the user deletes the script, then reinstalls there settings remain. And this settings function would make things easier for those who dont understand the registry aswell as others.





Sorry if thats hard to understand, if you need clarification, just ask.

/-- Thanks, Malekith

quote:

---

Originally posted by vikke
Edit: It's not ridiculous, you don't seem to know anything about how scripts work. Some scripts may need to run when Messenger starts to apply their features. The best solution I've come up with is to create a new object for Messenger Plus!, called Registry or something.

---

er what? I dont know how scripts work? pft whatever, did you even read what i wrote, thats why i said to have two different options "global" or "user", so existing scripts could use global (the option would have to default to this) and new scripts could use "user" if they wanted to have per account options

quote:

---

Originally posted by vikke
Also, you cannot run 2 scripts at the same time with different settings (if it's not programmed that way, some are).

---

many scripts store their settings in a xml file inside the script directory so they are self contained, but if scripts use the registry they would either have to use the "global" option (which if they didnt specify a <userLevel> then it would automaticly be assumed to be a global script( or add an email key inside their settings and store it under that

edit:
the script wouldn't even have to specify an email address, plus could just return the regkey/email in the MsgPlus.ScriptRegPath property (if the userLevel is set to "user")

quote:

---

Originally posted by SpunkyLoveMuff
Any changes would mean editing all existed scripts wouldn't it?

---

no, see above