| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
loop for consistency and readability.
|
| |
|
|
|
|
| |
NINJA joints stuff into its own method.
Now if ninja joints isn't active (which is the default) don't have to wade through a lot of massively indented irrelevant code.
|
| |
|
|
|
|
| |
out ifs and locks
This is to make it more readable.
|
| |
|
|
|
|
|
|
| |
region name exactly matches (not near matches)
This is to prevent situations where the first name returned by GridService.GetRegionsByName is not one that exactly matches the given region name, even when there is an exact match later on in the list.
Only the above two functions call this teleport method (the map uses a different routine) so this seems safe to change.
Addresses http://opensimulator.org/mantis/view.php?id=5606
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
authorization service rather than from the account.
This is to accomodate situations where the authorization service is being used by the hypergrid, where visitors have no user account.
See http://opensimulator.org/mantis/view.php?id=5517, this code is somewhat adapted/cleaned up from Michelle's patch
I'm a little ambivalent about this since visitors could put anything in firstname/lastname so it's not much of an auth measure.
It's up to the auth service to decide which data it actually uses.
Possibly we should be passing through other info such as agent circuit ip
|
| |
|
|
|
|
| |
When this setting is false and other defaults haven't been changed, scripts entering the simulator from another sim are automatically restarted but their state is not preserved.
When this setting is true, state that accompanies the script is reloaded (e.g. if a script had a variable i = 1 when leaving the source region, it will still have i = 1 on the destination region).
This setting does not affect crossings when regions are run in the same simulator. In this case, state is already preserved.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
scripts non-modifiable (but still copyable, etc).
Users should not be given the impression that they can modify these items.
This still does not solve the issue where library items cannot be dragged into prims or user inventory any time after they are initially seen.
Curiously, manually copying and pasting still appears to work.
On the surface, this seems to have something to do with library item caching on the client, since deleting the cache allows drag to work again once
Not sure what the exact problem is.
|
| |
|
|
|
|
|
| |
they use the defaults instead.
Some items had completely wrong permissions - this is easier than correcting them all.
The ability to set permissions in xml is retained since there are use cases for this (e.g. to create no-mod library scripts)
|
| |
|
|
|
|
|
|
| |
item xml files - always use PermissionMask.All instead (which was the existing default)."
There actually are uses for this. I will correct the perms instead since some entries appear to be wrong.
This reverts commit 667b54f5a2a04fa5a2859397868d270eab3913f1.
|
| |
|
|
|
|
| |
files - always use PermissionMask.All instead (which was the existing default).
Library items always need the same permissions, so it doesn't make sense to load them from the xml files. This just opens the door to permissions mistakes.
|
| |
|
|
|
| |
Fixed this by inspecting Shape.SculptEntry at various places instead of Shape.SculptType. Sculpties actually have a SculptType of Cylinder - only true mesh is SculptType.Mesh
This addresses http://opensimulator.org/mantis/view.php?id=5595
|
| |
|
|
| |
from XML properly.
|
| |
|
|
| |
Signed-off-by: Melanie <melanie@t-data.com>
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |\ |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Don't know of a good reason not to do this, seems to work fine.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
it once
Signed-off-by: root <root@grid00001.t-data.com>
|
| | | |
| | |
| | |
| | | |
the texture was changed
|
| | |/
|/|
| |
| | |
Signed-off-by: root <root@grid00001.t-data.com>
|
| | | |
|
| |/ |
|
| |
|
|
| |
everything, in order to avoid any deadlock issues.
|
| |
|
|
|
| |
This stops problems when we undo a few steps and start off down another path.
Surprisingly, apart from this now fixed problem, redo appears to be working too.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
I think (ha ha) this largely fixes undo, except for the fact that rotation a set of prims with 'edit linked parts' selected doesn't quite work properly (though this works fine if the checkbox isn't selected).
Also, the double undo bug for resize is still present.
Redo might be incredibly buggy, haven't even looked at that yet.
|
| |
|
|
| |
consistency
|
| | |
|
| |
|
|
| |
The only obviously broken things right now are the undo of the position of just a root prim (stays in place) and the fact that resizes need two undoes.
|
| | |
|
| |
|
|
|
| |
This isn't that great since I think I broke it a few commits earlier.
Undo of rotation of individual prims in a linkset is still broken
|
| |
|
|
| |
it actually does and is more consistent with other method names.
|
| |
|
|
|
|
| |
whole linkset.
However, what happens now is that undo just doesn't do anything when the root prim is selected on its own. This requires more code than just fiddling with undo states.
|
| |
|
|
| |
undo resize, rotation and position still needs fixing when only editing root prim of a linkset
|
| |
|
|
|
|
| |
This involves implementing a boolean in UndoState to signal whether the undo needs to be done for an entire group/linkset or just a single prim
Resizing individual components of linksets is still dodgy.
Resizing still has to be down twice, since for some reason the client is sending two multiobjectupdate packets on every resize except the very first. This applies to single prims and linksets. Need to look into this.
|
| |
|
|
| |
no functional effect - existing bugs still remain
|
| |
|
|
|
|
|
| |
Undo rotation and position appear to be working.
Resizing a single prim appears to be working, though the undo has to be done twice.
Resizing a group of prims still does not work properly - possibly because in the UndoState we don't store a knowledge of when we're resizing a whole group rather than individual prims.
This needs to be addressed.
|
| |
|
|
| |
remove OpenSim.Framework.UndoStack
|
| |
|
|
|
|
|
| |
own homebrew.
system stack also uses an array, so no performance penalty.
Also exposes undo count and adds a test assertion for correct undo count after resize
|
