Third party viewers achieve the custom message by using the transaction type
for object sale (5000)
On Mon, Feb 1, 2010 at 1:15 AM, Jacek Antonelli
wrote:
> I've been working on SNOW-436 ("Optional text for payments to show up
> in transaction history"), and at the moment I'm trying to figure out
It's funny because what if the other person IMs you first
On Wed, Jan 20, 2010 at 8:36 PM, Ardy Lay wrote:
> http://jira.secondlife.com/browse/VWR-2072
> New Feature -> UI -> IM -> Teleport (other person) Button
>
> http://jira.secondlife.com/browse/SNOW-402
> Adding Teleport button, in IM panel
The response message is ObjectProperties. Search the source for
_PREHASH_ObjectProperties and you see where a callback is set using
LLMessageSystem::setHandlerFuncFast. It's
LLSelectMgr::processObjectProperties.
You can either add a line in there to call your other function, or look into
somethin
Which BRANCH should I check out for the purpose of patching against it?
___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/SLDev
Please read the policies before posting to keep unmoderated posting privileges
custom client, which I think is an ideal option for allowing creators that
> need to preview their products realtime but without the expenses and weight
> added onto the asset servers.
> - Nexii Malthus
>
> On Sat, Jun 20, 2009 at 10:34 PM, Brandon Lockaby wrote:
>
>> H
Hi everyone. I know the aforementioned simulator isn't released yet, but I
heard about these changes recently and had to hop on the preview grid to
see.
It appears we are close to having HTTP for all asset uploads! It's
important to note that in several cases upload is no longer allowed via UDP,
issues and improvements (or post
> > further here, I'm happy to answer any questions).
> >
> > -Nyx
> >
> >
> >
> > Dahlia Trimble wrote:
> >
> > Many bots don't use "baked", or composite tex
Was browsing the SL JIRA and noticed a few people mentioning issues like
this "Version 1.23.1 (May 4th) viewer will not rez bots"
http://jira.secondlife.com/browse/VWR-13386
No surprise if there was no notice or documentation but does anyone know if
it is true that the requirements of what makes a
That does sound plausible if you can differentiate which content is cached
that way...
You say "static objects"... perhaps, if an object hasn't been changed in 2
days it could be placed in that category, something like that?
On Mon, Apr 20, 2009 at 3:04 PM, Laurent Laborde wrote:
> Friendly greet
My thoughts:
* Under the current circumstances a packet ID occupies 4 bytes
* While the packet ID's are below 256 (not for very long), you can save one
byte for every packet ID
* Once they get into the range of 256-65535, zero coding would save nothing
* Once they get into the range of 65536-167772
10 matches
Mail list logo
