You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 28, 2024. It is now read-only.
I was placing landscape items, and in raising some high, they would not respond to ctrl + z. I looked and they are NON-MOD objects. So i tested with mod objects and ctrl + z does work fine. Then i created a prim, set permissions to non-mod, sent it to a friend to test for me, same results, my non-mod prim did not respond to ctrl + z.
Actual Behavior
ctrl + z would not work on objects in edit
Expected Behavior
I expected the object to jump back into the place it was raised from as modifiable objects do.
Other information
yes, i repeated the same process using the Firestorm viewer ver 4.7.3.4323 with the same results. Ctrl + z does not work when editing non -mod objects for me.
Original Jira Fields
Field
Value
Issue
BUG-10855
Summary
" ctrl + z " not working on non-mod objects, but does work fine on modifiable objects.
Type
New Feature Request
Priority
Unset
Status
Accepted
Resolution
Accepted
Reporter
ZiaRose (ziarose)
Created at
2015-12-03T16:54:47Z
Updated at
2016-02-21T11:01:27Z
{
'Business Unit': ['Platform'],
'Date of First Response': '2015-12-03T11:44:25.044-0600',
'How would you like the feature to work?': '.',
"Is there anything you'd like to add?": 'yes, i repeated the same process using the Firestorm viewer ver 4.7.3.4323 with the same results. Ctrl + z does not work when editing non -mod objects for me.',
'ReOpened Count': 0.0,
'Severity': 'Unset',
'System': 'SL Viewer',
'Target Viewer Version': 'viewer-development',
'What just happened?': ' ctrl + z would not work on objects in edit',
'What were you doing when it happened?': 'I was placing landscape items, and in raising some high, they would not respond to ctrl + z. I looked and they are NON-MOD objects. So i tested with mod objects and ctrl + z does work fine. Then i created a prim, set permissions to non-mod, sent it to a friend to test for me, same results, my non-mod prim did not respond to ctrl + z. ',
'What were you expecting to happen instead?': 'I expected the object to jump back into the place it was raised from as modifiable objects do. ',
'Why is this feature important to you? How would it benefit the community?': '.',
}
The text was updated successfully, but these errors were encountered:
ObviousAltIsObvious commented at 2015-12-03T17:44:25Z, updated at 2015-12-03T17:50:21Z
Hi Zia! Unfortunately this isn't a bug, undo is disabled in the menu when your selection includes no modify objects.
It is still an interesting thing to ask for, as a new feature request!
As I understand it, undo is really a server side function. While we can move and rotate entire no-mod objects in world or on the attachment points, the server's undo history can contain operations we wouldn't be allowed to do without modify permission, like resizing the object or rearranging child prims.
It would be awesome if the system could permit undo on that limited set of operations, provided that permission checking wouldn't get too horrible. I think it comes down to the distinction between move and modify permission.
Steps to Reproduce
I was placing landscape items, and in raising some high, they would not respond to ctrl + z. I looked and they are NON-MOD objects. So i tested with mod objects and ctrl + z does work fine. Then i created a prim, set permissions to non-mod, sent it to a friend to test for me, same results, my non-mod prim did not respond to ctrl + z.
Actual Behavior
ctrl + z would not work on objects in edit
Expected Behavior
I expected the object to jump back into the place it was raised from as modifiable objects do.
Other information
yes, i repeated the same process using the Firestorm viewer ver 4.7.3.4323 with the same results. Ctrl + z does not work when editing non -mod objects for me.
Original Jira Fields
The text was updated successfully, but these errors were encountered: