
|
If you were logged in you would be able to see more operations.
|
|
|
| Last Triaged: |
06/Nov/08 01:08 PM
|
| Source Version: |
1.20.12
|
| Linden Lab Issue ID: |
DEV-17710
|
| Patch attached: |
Patch attached
|
| Linden Lab Internal Branch: |
featurettes/featurettes-7
|
Hiya,
as a pretty busy builder and scripter, I here and then have to go through
dozens of scrips in an object, just to change all the script permissions
one by one, if for instance the object originally was no-copy, no-mod, trans-ok,
and I want it to be copy, mod, trans-ok before giving it to a friend or releasing
it as a freebie. This means going through all prims of the object, and
setting the permissions of each single script, seperately.
I'd VERY much appreciate an automated function for that.
Where to place it:
TOOLS -> in the same category as RESET ALL SCRIPTS IN OBJECT.
What's it supposed to do:
Display a permissions-dialog to select copy/mod/trans permissions.
Thereafter, for all prims of the object, examine the contents, and for all
scripts found, IF YOU ARE the script creator OR the script already IS
all-perms, set the permissions of those scripts to the permissions
you selected at the start of this feature.
That would greatly speed up and simplify maintenance of complexely
scripted objects for us scripters/builders, especially if we release the
same product several times with additional features and different
permissions. AKA a cheap 'personal edition' with no.copy no-mod trans-ok'
vs. a 'sim owner edition' with 'copy-ok, mod-ok, no-trans'. Also it would
allow transfer of your own created works to your friends EASILY and
without setting all script permissions by hand, if you want them to have
a full perms copy. In any case, it's a feature I sorely miss.
Regards,
-Yina Yao
|
|
Description
|
Hiya,
as a pretty busy builder and scripter, I here and then have to go through
dozens of scrips in an object, just to change all the script permissions
one by one, if for instance the object originally was no-copy, no-mod, trans-ok,
and I want it to be copy, mod, trans-ok before giving it to a friend or releasing
it as a freebie. This means going through all prims of the object, and
setting the permissions of each single script, seperately.
I'd VERY much appreciate an automated function for that.
Where to place it:
TOOLS -> in the same category as RESET ALL SCRIPTS IN OBJECT.
What's it supposed to do:
Display a permissions-dialog to select copy/mod/trans permissions.
Thereafter, for all prims of the object, examine the contents, and for all
scripts found, IF YOU ARE the script creator OR the script already IS
all-perms, set the permissions of those scripts to the permissions
you selected at the start of this feature.
That would greatly speed up and simplify maintenance of complexely
scripted objects for us scripters/builders, especially if we release the
same product several times with additional features and different
permissions. AKA a cheap 'personal edition' with no.copy no-mod trans-ok'
vs. a 'sim owner edition' with 'copy-ok, mod-ok, no-trans'. Also it would
allow transfer of your own created works to your friends EASILY and
without setting all script permissions by hand, if you want them to have
a full perms copy. In any case, it's a feature I sorely miss.
Regards,
-Yina Yao |
Show » |
made changes - 30/Aug/07 08:24 AM
| Field |
Original Value |
New Value |
|
Link
|
|
This issue is duplicated by SVC-593
[ SVC-593
]
|
made changes - 02/Sep/07 12:05 PM
|
Link
|
This issue is duplicated by SVC-593
[ SVC-593
]
|
|
made changes - 02/Sep/07 12:05 PM
|
Link
|
|
This issue Relates to SVC-593
[ SVC-593
]
|
made changes - 21/Dec/07 11:09 PM
|
Workflow
|
jira
[ 14937
]
|
jira-2007-12-19
[ 18161
]
|
made changes - 22/Dec/07 12:39 AM
|
Workflow
|
jira-2007-12-19
[ 18161
]
|
jira-2007-12-21
[ 19815
]
|
made changes - 23/Dec/07 01:00 AM
|
Workflow
|
jira-2007-12-21
[ 19815
]
|
jira-2007-12-22a
[ 50100
]
|
made changes - 21/Feb/08 05:25 AM
|
Key
|
MISC-626
|
VWR-5082
|
|
Project
|
4. Second Life Misc Issues - MISC
[ 10000
]
|
1. Second Life Viewer - VWR
[ 10003
]
|
made changes - 21/Feb/08 05:26 AM
|
Component/s
|
|
Permissions
[ 10028
]
|
|
Component/s
|
|
User Interface
[ 10033
]
|
made changes - 08/Jul/08 11:16 AM
made changes - 08/Jul/08 11:17 AM
|
Source Version
|
|
1.20.12
|
|
Patch attached
|
|
[Patch attached]
|
made changes - 10/Jul/08 08:37 AM
|
Linden Lab Issue ID
|
|
DEV-17710
|
made changes - 10/Jul/08 08:40 AM
|
Last Triaged
|
|
10/Jul/08 08:40 AM
|
made changes - 12/Aug/08 03:49 PM
|
Summary
|
'Set permissions of scripts in object' feature, similar to 'recompile all scripts in object', in Tools tab.
|
'Set permissions on selected task inventory' feature, similar to 'recompile all scripts in object', in Tools tab.
|
made changes - 12/Aug/08 07:10 PM
|
Link
|
|
This issue is duplicated by VWR-8634
[ VWR-8634
]
|
made changes - 01/Sep/08 02:17 PM
made changes - 11/Sep/08 01:28 PM
|
Last Triaged
|
10/Jul/08 08:40 AM
|
11/Sep/08 08:40 AM
|
made changes - 15/Sep/08 07:10 AM
|
Link
|
|
This issue is duplicated by MISC-1546
[ MISC-1546
]
|
made changes - 18/Sep/08 05:54 PM
made changes - 18/Sep/08 05:54 PM
|
Link
|
|
This issue Relates to VWR-8049
[ VWR-8049
]
|
made changes - 26/Sep/08 10:17 PM
made changes - 27/Sep/08 07:08 PM
|
Comment
|
[ A small technical detail about the patch to this issue:
in indra/newview/llviewermenu.cpp, the patch initializes the "queue" variable, but does not use it. Shouldn't it call method "queue_action()" with this value and two error messages, mostly for consistency with the "reset scripts in selection" feature? It's probably just a matter of programming style though.
For the same consistency reasons, it would perharps be safer IMHO to return "false" if "queue" is NULL.
]
|
|
made changes - 06/Nov/08 01:12 PM
|
Assignee
|
|
Coco Linden
[ Coco Linden
]
|
made changes - 06/Nov/08 01:13 PM
|
Last Triaged
|
11/Sep/08 08:40 AM
|
06/Nov/08 01:08 PM
|
made changes - 11/Nov/08 03:00 PM
|
Status
|
Open
[ 1
]
|
Fix Pending
[ 10001
]
|
|
Linden Lab Internal Branch
|
|
featurettes/featurettes-7
|
made changes - 13/Nov/08 11:07 AM
|
Workflow
|
jira-2007-12-22a
[ 50100
]
|
jira-2008-11-14
[ 64600
]
|
made changes - 13/Nov/08 11:29 AM
|
Workflow
|
jira-2007-12-22a
[ 64600
]
|
jira-2008-11-14
[ 72423
]
|
made changes - 13/Nov/08 04:59 PM
|
Workflow
|
jira-2008-11-14
[ 72423
]
|
jira-2008-11-14a
[ 97021
]
|
made changes - 13/Nov/08 05:14 PM
|
Workflow
|
jira-2008-11-14
[ 97021
]
|
jira-2008-11-14a
[ 102453
]
|
made changes - 13/Nov/08 05:23 PM
|
Workflow
|
jira-2008-11-14
[ 102453
]
|
jira-2008-11-14a
[ 105965
]
|
made changes - 13/Nov/08 05:37 PM
|
Workflow
|
jira-2008-11-14
[ 105965
]
|
jira-2008-11-14a
[ 111155
]
|
made changes - 13/Nov/08 06:07 PM
|
Workflow
|
jira-2008-11-14
[ 111155
]
|
jira-2008-11-14a
[ 121574
]
|
made changes - 13/Nov/08 06:33 PM
|
Workflow
|
jira-2008-11-14
[ 121574
]
|
jira-2008-11-14a
[ 131417
]
|
made changes - 13/Nov/08 06:52 PM
|
Workflow
|
jira-2008-11-14
[ 131417
]
|
jira-2008-11-14a
[ 138672
]
|
made changes - 12/Jun/09 08:28 AM
|
Fix Version/s
|
|
1.23 Release Candidate
[ 10433
]
|
made changes - 15/Jun/09 04:52 PM
|
Status
|
Fix Pending
[ 10001
]
|
Resolved
[ 5
]
|
|
Fix Version/s
|
|
1.23
[ 10470
]
|
|
Resolution
|
|
Fixed
[ 1
]
|
|