quote:
Originally posted by markee
quote:
Originally posted by CookieRevised
Hence why I like to suggest a hidden registry option for it, so that only the people who actually are used to scripts and know what they are doing, can turn this off.
In that way, people who aren't used to scripts, who are new to scripts and all the other 'beginners' would still see the normal default way as it is now...
This is why I suggested the "advanced" hyperlink/button to reveal a hidden area of the window with this option. I just feel this way it isn't as permanent as a registry setting
Either you are checking out scripts very regulary and thus a 'permanent' registry option is the best and most convenient, or either you don't regulary check scripts out and thus you can manually extract that script for that one time only.
quote:
Originally posted by markee
and doesn't affect other people who also use the same computer when they try to import a script.
the registry setting can perfectly be stored user specific.
Although both ways (registry option and your hidden link) wont prevent people from installing and thus running a script on a computer from sombody else as scripts are global and not user specific. So, your link isn't going to prevent that either. There's no difference in both methods regarding that.
quote:
Originally posted by markee
Even is someone was to try to create a script to make this user dependant it still wouldn't work because of plus not reading the registry for each event (unless this is made an exception to the rule).
I don't quit get that. The registry option can be read only once when the user signs in, it doesn't need to be read each time a script is imported as that wouldn't matter at all.
/ 
