Changed Event Desc Flag
closed
ClaraVR Resident
What: A CHANGED_DESCRIPTION bit field flag for the changed event.
Why: Running timers to get the most basic object properties seems to be fairly expensive.
How: Trigger this change event on every user input in the desc field on an obj or trigger it when the description field is "exited", if thats a feature.
Use cases: Using the description for a small configuration on many objects that may be identical, but require different configuration. Instead of having 20 timers on 20 objects, the object would just reset when the description changes. There can be a natural "debounce" / delay for the user input, or let creators decide the update rate of their following logic after the event has been triggered.
This flag can also be used for objects and systems that are supposed to stay in place for a long time without being touched and simply updated by a small description change, without needing to edit a notecard with a reader attached.
Additional idea: A flag for an object name + description and another 2 flags to filter it after the even has been triggered. Something like CHANGED_IDENTITY
Log In
ST33LDI9ITAL Resident
I think changed description would be more useful than name.. for a lot of cases.
Lucia Nightfire
We should not be adding anything else to changed until we get a means of filtering triggers. The more triggers added, the more changed runs and the higher script EPS goes in the region.
Vincent Nacon
There are plenty of scripts that can easily get bricked by this.
ST33LDI9ITAL Resident
Lucia Nightfire Meanwhile objects in regions running 1 sec or sub timers to compensate for lack of trigger eating up even more so..
I think the bigger issue though and related to this is that.. we don't have an easily accessible editable data store accessible from both lsl and gui. Because, here's the thing, alot of people use descrip to plop and manipulate data into.
Why? Because it's easy, quick, and accessible. From both lsl and gui. Can be picked up right away by other objects with llGOD.
Notecards are a thing, they trigger changed_inventory, can be read remotely, but aren't writable from lsl and also have their quirks. LSD is writable from lsl but not gui, not accessible remotely. So have to plop in some clunky menu or chat listen code or such for input. Also doesn't trigger changed.
So we need some sort of solution to this. Ultimately, a gui for LSD and changed event trigger, and remote LSD or making notecards editable from lsl.
Janet Rossini
I'd give this a +1, would be very convenient for customizing products. I see no significant concern about bricking scripts: what am I missing? this event would rarely fire and thus should not cause much trouble.
SL Feedback
Merged in a post from ST33LDI9ITAL Resident:
Title: Changed event for name and/or description
Details: CHANGED_NAME and/or CHANGED_DESC. Be nice to see either or both of these. Would keep from having to make timers for them, which really shouldn't be necessary.
Spidey Linden
closed
Hello, and thank you for your feature request.
Incoming suggestions are reviewed in the order they are received by a team of Lindens with diverse areas of expertise. We consider a number of factors: Is this change possible? Will it increase lag? Will it break existing content? Is it likely that the number of residents using this feature will justify the time to develop it? This wiki page further describes the reasoning we use: http://wiki.secondlife.com/wiki/Feature_Requests
This particular suggestion, unfortunately, cannot be tackled at this time. However, we regularly review previously deferred suggestions when circumstances change or resources become available.
We are grateful for the time you took to submit this feature request. We hope that you are not discouraged from submitting others in the future. Many excellent ideas to improve Second Life come from you, our residents. We can’t do it alone.
Thank you for your continued commitment to Second Life.
Bavid Dailey
I think overloading the description field to facilitate this one use of it is not a good idea.
Standign back a bit, you're askign for a object attribute that can be used for configuration, and which raises an event when changed. Phrased that way, I'd be all for it, especially if it had a decent text maximum size (description does not)
Lucia Nightfire
The changed() event does not need any new defacto triggers until we get trigger filtering capability. Adding more triggers without a filter will only increase script EPS in the regions.