|
|
|
[
Permlink
| « Hide
]
McCabe Maxsted added a comment - 31/Jan/08 12:49 AM
I support that. Right now, the wording is confusing and probably unintuitive. If you're attempting to do something you cannot do (like setting "allow anyone to copy" on an object containing no copy items) the viewer should warn you. Voting and adding components.
A corollary would likely be a dialog when you drop a non-copyable item into an "allow anyone to copy" object.
This is going to be difficult to do - because different types of things need different permissions most of the time within an object. Even something as simple as a little tip-jar I made - the main script had to be no-mod/copy/no-trans, the configuration card had to be mod/copy/no-trans. Holodecks have similar issues.
There are 8 basic combinations of the current set of primary permissions - some of which are disallowed, I think - things can't be no-copy/no-trans. Perhaps what we really need are "roles" - "freebie" - "resellable" - "unresellable". The whole mod/no-mod thing gets kind of confusing as well - but that's an inevitable result when you try to have a system flexible enough to actually do what people want. We definitely need some thinking on this - the dialog for when you drop a no-copy item into an open-copy item is definitely worth thinking about. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Normal
Add dialogs when setting object "allow anyone to copy" and nested items cannot be copied.
