| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
using the Estate Tools.
* Could this be extended in the future to support .oar uploads too? Only time will tell!
|
| |
|
|
|
|
|
|
| |
every user's HUD
|
|
|
|
|
|
|
| |
* Implements the SendInitiateDownload method in IClientAPI
* Uses the ITerrainModule Interface to write a terrain file to disk then uses a FileStream to read the binary file from the disk and put it in a byte array. and save to the xFer list.
* It then tells the client to download the file and the client initiates an Xfer request.
|
|
|
|
|
|
|
| |
* Decouple sog and sop by removing the need to pass the sog to the sop when it is created - most of the code was doing this operation (and hence duplicating it) anyway
* Remove unused constructors
|
|
|
|
|
|
|
| |
It is required by group IM and also for a proper implementation of item
give, group notice attachments and offline IM.
|
|
|
|
|
|
| |
* Changed SendInstantMessage, dropped fromAgentSession and imSessionID as security precaution, see http://opensimulator.org/wiki/OpenSim_0.6_IClientAPI#Porting_Guide for details on porting.
* Removed unused usings from Framework.*
|
| |
|
|
|
|
| |
the verb at the front
|
|
|
|
|
|
| |
* These are assigned when the object is attached to the scene
|
| |
|
|
|
|
|
|
| |
Too many fixes to list.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
on-/offline updates, calling cards for friends.
This adds methods in the DB layer and changes the MessagingServer, so a full
update (incl. UGAIM) is necessary to get it working. Older regions shouldn't
break, nor should older UGAIM break newer regions, but friends/presence will
only work with all concerned parts (UGAIM, source region and destination
region) at this revision (or later).
I added the DB code for MSSQL, too, but couldn't test that.
BEWARE: May contain bugs.
|
|
|
|
|
|
|
|
|
|
| |
sending ImageNotFound to clients if avatar textures are missing
* Whilst this does automatically get the client to rebake, on crossing a region border the 'local' assets are left behind
* There may be a cunning solution (such as squirting the assets on region crossing, or having them fetched from the original region) but
instead I'm going to opt for the easy solution of keeping them in the asset database, for now
|
| |
|
|
|
|
|
|
| |
signature
|
| |
|
|
|
|
|
|
| |
real groups module can even be implemented.
|
| |
|
|
|
|
|
|
|
|
| |
Add rezzing time to objects. Add Object return and traffic fields to land
database. Add plumbing for auto return. Implement auto return.
Contains a migration. May contain nuts.
|
|
|
|
|
|
|
| |
* I believe this is reasonable since code outside the Linden client stack shouldn't be aware of the packet format being used
* I would love to have made the method protected, but the LoadBalancerPlugin is still calling it and resolving that would require more work
|
| |
|
|
|
|
| |
LLClientView
|
|
|
|
| |
descriptive of its actual function
|
| |
|
|
|
|
| |
descriptive of what it actually does
|
|
|
|
|
|
| |
Note: New file, run prebuild.
|
| |
|
|
|
|
| |
the new surface touch parameters in 1.21 viewers.
|
| |
|
|
|
|
|
|
|
| |
* I believe this was the cause of the remaining packet_out_of_order messages in the Linden client logs
* There were race conditions where multiple clientstacks would overwrite each other's sequence numbers
|
| |
|
| |
|
|
|
|
|
|
| |
* Initial implementation
* You'll only be able to seen green dots on regions on the map that have been updated.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
old way: each region module interested in chat from client had to
- subscribe to scene.EventManager.OnNewClient
- then in its OnNewClient delegate it would subscribe to
client.OnChatFromViewer to capture chat messages coming
new way: ChatModule is the only region module that uses the "old
way" approach but is now forwarding all client chat via
scene.EventManager.OnChatFromClient
- each region module interested in chat from client now only
subscribes to scene.EventManager.OnChatFromClient
this not only simplifies code, but also allows us to substitute
ChatModule with derived classes (ConciergeModule is going to be one
example).
Also, this changeset changes ChatFromViewer to ChatFromClient as it
doesn't necessarily have to be a viewer that is a chat source.
i've taken great care to only comment out those OnNewClient delegates
that were only used for getting at the client chat --- hope it's not
breaking anything.
|
|
|
|
|
|
|
| |
Thank you, idb, for a patch to implement the packet and plumbing for
the material settings.
|
|
|
|
|
|
| |
- Implemented llMapDestination.
|
|
|
|
|
|
|
|
|
| |
Estate/ Manager Owner Uses the Region/Estate Menu Region TAB,
and uses "Teleport Home All Users..." (Action Button), the
action will complete but no one will be teleported and all
users still function in the region ok.
|
| |
|
|
|
|
|
|
|
|
|
| |
* Updates to libomv r2243,
* Remove lots of unnecessary typecasts
* Improves SendWindData()
Thanks jhurliman.
* Will update OpenSim-libs in 10 minutes..
|
|
|
|
|
|
|
| |
* It seems kind of silly to be building a 256x256 array just to use two 16 float blocks.. but for now the layerdata routine requires it so we'll go along with that.
* We only fill a 32x16 area of the 256x256 float array with data.
* We use patches 0,0 and 0,1 for the first and second patch to determine the direction and magnitude of the wind.
|
|
|
|
|
|
|
|
| |
* A little wind wouldn't hurt anyone, right? This is the 'slightly breezy' setting.. hopefully you won't notice 'much' of a difference.
* It turns out the terrain patch routine is similar enough to the wind version that it can be used to hack together a breeze generator with a few mods.
* Not much configuration.. yet. You only get breeze updates in the general vicinity of your camera now to keep bandwidth usage down.. and we're not talking about 'much' movement at the moment.
* initial version... could use improvement I'm sure.
|
|
|
|
|
|
|
| |
* Force ClickAction persistence even if other object properties are not edited
* Thanks nlin!
|
|
|
|
|
| |
* Please don't break the build. *fingers crossed*
|
| |
|
|
|
|
|
|
|
| |
* This is a HUGE OMG update and will definitely have unknown side effects.. so this is really only for the strong hearted at this point. Regular people should let the dust settle.
* This has been tested to work with most basic functions. However.. make sure you back up 'everything' before using this. It's that big!
* Essentially we're back at square 1 in the testing phase.. so lets identify things that broke.
|