aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/OpenSim/Region/Framework/Scenes/SceneObjectGroup.Inventory.cs (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'master' into careminster-presence-refactorMelanie2010-04-191-1/+11
|\
| * All scripts are now created suspended and are only unsuspended when the objectMelanie2010-04-191-0/+8
| | | | | | | | | | | | is fully rezzed and all scripts in it are instantiated. This ensures that link messages will not be lost on rez/region crossing and makes heavily scripted objects reliable.
| * Partially implement share with group option for object inventory itemsJustin Clark-Casey (justincc)2010-04-051-1/+3
| | | | | | | | | | | | If serverside permissions are off then this works as expected. Previously, it was impossible for more than one person to edit such items even if permissions were off. If serverside permissions are on then this works as expected if the object was created by an avatar who had the required group active. However, if the group for the object is later set then the contained item is still not editable. This may be linked to a wider bug where the object is still not modifiable by the group anyway
* | Some merge fixupsMelanie2010-01-261-2/+2
| |
* | Merge branch 'master' into careminsterMelanie2010-01-261-5/+5
|\ \ | |/
| * Fix a problem where llDie() calls were sometimes leaving dead objects behind.Justin Clark-Casey (justincc)2010-01-251-2/+6
| | | | | | | | | | | | | | | | | | | | When an object was deleted, the remove script instance call was aggregating the scripting events as normal. This would queue a full update of the prim before the viewer was notifed of the deletion of that prim (QuitPacket) On some occasions, the QuitPacket would be sent before the full update was dequeued and sent. In principle, you would think that a viewer would ignore updates for deleted prims. But it appears that in the Linden viewer (1.23.5), a prim update that arrives after the prim was deleted instead makes the deleted prim persist in the viewer. Such prims have no properties and cannot be removed from the viewer except by a relog. This change stops the prim event aggregation call if it's being deleted anyway, hence removing the spurious viewer-confusing update.
* | Convert some remaining legacy lock()s for m_parts in SceneObjectGroup to ↵CasperW2009-12-271-11/+13
|/ | | | ReaderWriteLockSlim, hopefully fixes a native crash
* Remove the old (Remoting) region crossing code. Fix the new code toMelanie2009-11-261-64/+35
| | | | | | | | | | pass script state and assembly again properly. Reintroduce respecting tht TrustBinaries flag. Changes the interregion protocol! No version bump because it was broken anyway, so with a version mismatch it will simply stay broken, but not crash. Region corssing still doesn't work because there is still monkey business with both rezzed prims being pushed across a border and attached prims when walking across a border. Teleport is untested by may work.
* Remove GetAssemblyName and friends from the SE interface. It's now handledMelanie2009-11-261-88/+5
| | | | internally
* Minor: Change OpenSim to OpenSimulator in older copyright headers and ↵Jeff Ames2009-06-011-1/+1
| | | | LICENSE.txt.
* * Make it possible to store creator strings in user inventory items as well ↵Justin Clarke Casey2009-04-081-1/+1
| | | | | | | | | as UUIDs * All existing functionality should be unaffected. * Database schemas have not been changed.
* Mantis#3218. Thank you kindly, TLaukkan (Tommil) for a patch that:Charles Krinke2009-02-221-1/+1
| | | | | | | | | * Added log4net dependency to physxplugin in prebuild.xml. * Added missing m_log fields to classes. * Replaced Console.WriteLine with appropriate m_log.Xxxx * Tested that nant test target runs succesfully. * Tested that local opensim sandbox starts up without errors.
* Fix region crossing for unscripted prims, avoid costly SEHMelanie Thielker2009-02-191-1/+3
|
* Make in-code provisions for the tests. Tests would fail because the Melanie Thielker2009-02-181-1/+14
| | | | | | | | required file system objects are not present in the test harness. This makes the main code ignore the failure, therefore the test succeeds. Not elegant and maybe a unit test guru has a better way. Marked as a TODO
* Fix the windows sharing violations on script crossingsMelanie Thielker2009-02-181-13/+46
|
* Fixes the problem of attachment offset after crossings/TPs. Hopefully it ↵diva2009-02-101-1/+1
| | | | fixes mantis #3126, as well as other random displacements. The problem was that the new object at the receiving region was being marked as attachment before AttachObject was called. That made its AbsolutePosition be the position of the avie, and that was what was being given to AttachObject.
* Moved prim crossing out of OGS1 and into RESTComms and ↵diva2009-02-091-3/+80
| | | | | | | | | | LocalInterregionComms. This breaks interregion comms with older versions in what concerns prim crossing. In the process of moving the comms, a few things seem to be working better, namely this may address mantis #3011, mantis #1698. Hopefully, this doesn't break anything else. But I'm still seeing weirdnesses with attchments jumping out of place after a cross/TP. The two most notable changes in the crossing process were: * Object gets passed in only one message, not two as done before. * Local object crossings do not get serialized, as done before.
* This changeset is the step 1 of 2 in refactoringDr Scofield2009-02-061-0/+401
OpenSim.Region.Environment into a "framework" part and a modules only part. This first changeset refactors OpenSim.Region.Environment.Scenes, OpenSim.Region.Environment.Interfaces, and OpenSim.Region.Interfaces into OpenSim.Region.Framework.{Interfaces,Scenes} leaving only region modules in OpenSim.Region.Environment. The next step will be to move region modules up from OpenSim.Region.Environment.Modules to OpenSim.Region.CoreModules and then sort out which modules are really core modules and which should move out to forge. I've been very careful to NOT BREAK anything. i hope i've succeeded. as this is the work of a whole week i hope i managed to keep track with the applied patches of the last week --- could any of you that did check in stuff have a look at whether it survived? thx!
generated by cgit v1.1 at 2024-12-21 08:01:30 +0000