| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
The item ID is the one required for any script manipulation on the command line, so I think it's somewhat more useful to show this bearing in mind the limited space available
|
| |
|
|
|
|
|
|
| |
engine in the current region.
Also added synonym of "scripts show"
|
|
|
|
| |
module is disabled.
|
|
|
|
| |
user knows why they are waiting.
|
|
|
|
| |
out that prim's local id in the error message.
|
| |
|
|
|
|
| |
It's never possible for SOG to have no RootPart, except in the first few picosends of the big bang when it's pulled from region persistence or deserialized
|
|
|
|
|
| |
The only times when ParentGroup might be null is during regression tests (which might not be a valid thing) and when scene objects are being constructed from the database.
At all other times it's not possible for a SOP not to have a SOG parent.
|
|
|
|
|
|
| |
Apart from one obvious bug, this was failing because attempting to serialize the script from inside the script (as part of saving the attachment as an inventory asset) was triggering an extremely long delay.
So we now don't do this. The state will be serialized anyway when the avatar normally logs out.
The worst that can happen is that if the client/server crashes, the attachment scripts start without previous state.
|
| |
|
|
|
|
| |
OpenSim.Tests.Common instead
|
| |
|
|
|
|
|
|
|
|
|
| |
Adding ability to place script engine assemblies outside
the codebase directories.
Uses new [XEngine] option: ScriptEnginesPath = "path_to_assemblies"
Signed-off-by: Melanie <melanie@t-data.com>
|
| |
|
| |
|
|
|
|
|
|
| |
Revert "Reverting this for now, but this needs to go in again."
This reverts commit c0d9ab941dd1ab88f00f6d4f2a53a4fe5c605e57.
|
|
|
|
|
|
| |
Revert "Another stab at http://opensimulator.org/mantis/view.php?id=4858. Eliminated more nested locks."
This reverts commit ffbae52a130376ecaa04d7d475709985c62c06ed.
|
|
|
|
| |
more nested locks.
|
|
|
|
| |
Eliminated the nested locks of m_Scripts and m_PrimObjects.
|
|
|
|
|
|
| |
know what"
This reverts commit f798679b8005e532f933553007cca989112f4a1d.
|
|
|
|
| |
this is, you should test it. If you don't, don't use it.
|
|
|
|
| |
region anyway
|
|
|
|
| |
due to unhandled file lock exception. Attempt to resolve by wrapping several instances of file create / read logic in using statements and added some error handling for locked file exceptions. If it is IDisposable, it must be disposed! The close statements are unnecessary but harmless so I have left those in. The end of the using block will close and dispose automagically.
|
| |
|
| |
|
|
|
|
| |
the script hasn't yet saved state, or can't save state because of a loop
|
|
|
|
| |
compiling it
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
Send continuous touch() events if the left mouse button is held down while moving over an object
This conforms with Linden Lab practice
Thanks Revolution
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Signed-off-by: Melanie <melanie@t-data.com>
|
|
|
|
|
|
| |
CRs cleaned from patch
Signed-off-by: Melanie <melanie@t-data.com>
|
| |
|
| |
|
|
|
|
|
|
|
| |
It was used. By the API, which is dynamically loaded. So it didn't complain
until it hit Bamboo
This reverts commit 33d5018e94e52cb875bf43bced623bdc6aa41ef0.
|
| |
|
|
|
|
| |
not in a funky debug window.
|
|
|
|
|
|
| |
Committed from my other box where git is not configured properly
Signed-off-by: Melanie <melanie@t-data.com>
|
|
|
|
|
|
| |
Change the reader to wrap old-style definitions in new style wrappers.
Change importer to not check irrelevant data that can't be reconstructed
This removes the last bit of knowledge of XEngine's .state files from core.
|
|
|
|
| |
rez from inventory.
|
|
|
|
|
| |
Add Engine=xxx attribute and check for it's presence. Ignore state data
written bby another engine
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
internally
|
|
|
|
|
|
| |
all scripts are loaded from the same thread, rather than launching a
new one for each script. This is only marginally slower, but avoids the
race condition that led to script engine failure.
|
| |
|