• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: VWR-15236
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Won't Finish
Priority: Normal Normal
Assignee: Unassigned
Reporter: Ezian Ecksol
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
1. Second Life Viewer - VWR

Grey out/mark objects in inventory that aren't saved yet on asset server

Created: 21/Aug/09 01:56 AM   Updated: 24/Sep/09 04:13 AM
Component/s: Inventory, User Interface
Affects Version/s: 1.23
Fix Version/s: None

Issue Links:
Relates
 


 Description  « Hide
If we work on the prims or the scripts of a worn attachement, detach it and attach again immediatly, the changes are normally lost.

Somewhere once I read one has to wait minimum 10 seconds before attaching the item again, because the asset server needs some time to save it.

Unfortunetly, especially in the last weeks, 10 seconds are not enough. I had some cases of lost changes last weeks. Waiting 30 seconds is a safer approach. But I had one case even that wasn't enough.

My proposal: grey out or mark in any way detached (previouly worn) objects that are still unsaved, so we can see how long we have to wait to attach it again.

Or give us some other mechanism to make sure asset is saved.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Ezian Ecksol made changes - 21/Aug/09 01:56 AM
Field Original Value New Value
Summary Grey out/mark objects in inventory that aren't saved as asset Grey out/mark objects in inventory that aren't saved yet on asset server
Ezian Ecksol made changes - 21/Aug/09 01:56 AM
Link This issue Relates to VWR-6110 [ VWR-6110 ]
Ezian Ecksol made changes - 21/Aug/09 01:57 AM
Description If we work on the prims or the scripts of a worn attachement, detach it and attach again immediatly, the changes are normally lost.

Somewhere once I read one has to wait minimum 10 seconds before attaching the item again, because the asset server needs some time to save it.

Unfortunetly, especially in the last weeks, 10 seconds are not enough. I had some cases of lost changes last weeks. Waiting 30 seconds is a safer approach. But I had one case even that was enough.

My proposal: grey out or mark in any way detached (previouly worn) objects that are still unsaved, so we can see how long we have to wait to attach it again.

Or give us some other mechanism to make sure asset is saved.
If we work on the prims or the scripts of a worn attachement, detach it and attach again immediatly, the changes are normally lost.

Somewhere once I read one has to wait minimum 10 seconds before attaching the item again, because the asset server needs some time to save it.

Unfortunetly, especially in the last weeks, 10 seconds are not enough. I had some cases of lost changes last weeks. Waiting 30 seconds is a safer approach. But I had one case even that wasn't enough.

My proposal: grey out or mark in any way detached (previouly worn) objects that are still unsaved, so we can see how long we have to wait to attach it again.

Or give us some other mechanism to make sure asset is saved.
Ellla McMahon made changes - 21/Aug/09 04:07 PM
Link This issue Relates to SVC-114 [ SVC-114 ]
Ellla McMahon made changes - 21/Aug/09 04:08 PM
Link This issue Relates to SVC-381 [ SVC-381 ]
Ezian Ecksol made changes - 24/Sep/09 04:13 AM
Status Open [ 1 ] Resolved [ 5 ]
Resolution Won't Finish [ 2 ]