new behavior for "New Script" button?

1.12 seems to have introduced a new behavior: when you click the "New Script" button, you get a "New Script" item in the object's inventory immediately, and it immediately starts running and says, "Hello, Avatar!" at you. If you want to actually edit it, you have to open it manually to do so.

Was there any specific reason for this change (say, preventing content loss or something)? It's pretty annoying, adding another step to the process of making a new script, and adding needless chatter.

If it's really necessary to add the new script to the object immediately (unlike before, where the script was only truly created the first time it was saved), then I'd appreciate it if the annoying llSay and touch event could be removed from the default script. It might also be nice to set the new script not-running so that it's not taking up valuable sim resources, although that could lead people to be confused as to why their script isn't working when they forget to set it running (happens to me all the time).

At face value, this looks like an utterly pointless change. If it was accidental or without any specific reason, reversing the change would be appreciated.

The interesting part is, I read the release notes, and was under the impression that scripts, when first created, were set to "not running":



Which, btw... I am NOT a fan of. Cuz everytime I create a new script, I have to remember to start it, as opposed to it starting when I save the first time, harumph.


- d.

Having an unsaved script open in an editor window led to an exploit? And instead of just fixing the exploit, someone decided to work around it, making the software harder to use?

Gee.

This mystical philosophy is referred to as 'The Linden Way', and has a long and colorful history which has left a plethora of nerfed features and ham fisted tools in its wake.

Then how about making the default "new script" not do anything?

default
{
  state_entry()
  {
    # llOwnerSay("Hello Avatar");
  }
}

At least, PLEASE change it so the script is saved, and the window for it still left open.

How often do you click "new script" without the intent of immediately editing it? Never.


- d.

What was the exploit? Now that it's fixed, it seems like it might be possible for you to share more with us. If we knew more about what the limitations are here, we might be able to suggest better ways of making the UI work while still avoiding the exploit.

Was the exploit perhaps that you could start a new script in one object, select another with the editor, then save, and it let you stuff a script into an object you didn't own/control? Maybe in that case, immediately opening newly-created scripts is still a workable solution... if so, I know I'd sure appreciate that. In fact, it'd make even more sense than the prior model, because we'd actually see the new script in the inventory of the item, unlike before, where it wasn't created until we saved for the first time.

Would it be possible to make it so that new scripts are set not-running (so that we don't get greeted by over-eager new scripts all the time), but then are automatically set to running the first time they're saved?