Re: [opensource-dev] Library Refresh viewer

Checking in to see if anyone is seeing problems with the new libraries. Crash reports have been mostly quiet and as expected. No lurking horrors yet? m ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSo

Re: [opensource-dev] someone get the blindfold off me please - where in the sourcecode is the spot where a "parcel full" message is created?

Lance, Do you think it could be a server version problem? Not working then works on a different logon region. Or was corrected with today's server deploys. Nicky > > From: Lance Corrimal >To: opensource-dev@lists.secondlife.com >Sent: Wednesday, August 6, 2014 4

Re: [opensource-dev] someone get the blindfold off me please - where in the sourcecode is the spot where a "parcel full" message is created?

Am Mittwoch, 6. August 2014, 23:27:58 schrieb Henri Beauchamp: > You probably changed something else in the non-working build, which > broke the process_alert_core() function... Nope, nothing. I'm thinking that the "parcel full" message gone missing was one of the many effects of a ban list not

Re: [opensource-dev] someone get the blindfold off me please - where in the sourcecode is the spot where a "parcel full" message is created?

On Wed, 06 Aug 2014 21:51:44 +0200, Lance Corrimal wrote: > > Would any of you believe that this change fixed this problem? > > http://dolphinsource.eregion.de/dolphinviewer3-beta/commits/9d50f4af1158b493 > > 64cfb0d38090c7947db56f03 > > > > *facepalm* > > > > How is one supposed to apply logic

Re: [opensource-dev] someone get the blindfold off me please - where in the sourcecode is the spot where a "parcel full" message is created?

Am Mittwoch, 6. August 2014, 21:45:52 schrieb Lance Corrimal: > Well i'll be damned. > > Would any of you believe that this change fixed this problem? > http://dolphinsource.eregion.de/dolphinviewer3-beta/commits/9d50f4af1158b493 > 64cfb0d38090c7947db56f03 > > *facepalm* > > How is one supposed

Re: [opensource-dev] someone get the blindfold off me please - where in the sourcecode is the spot where a "parcel full" message is created?

Well i'll be damned. Would any of you believe that this change fixed this problem? http://dolphinsource.eregion.de/dolphinviewer3-beta/commits/9d50f4af1158b49364cfb0d38090c7947db56f03 *facepalm* How is one supposed to apply logic to stuff like that. Cheers LC Am Mittwoch, 6. August 2014, 21:1

Re: [opensource-dev] someone get the blindfold off me please - where in the sourcecode is the spot where a "parcel full" message is created?

Hi, the part that I really don't get is where I see that that part of the code has not been changed in my viewer (comparing with viewer-release) but still behaves so differently... Cheers LC Am 06.08.2014 um 20:38 schrieb Henri Beauchamp: > On Wed, 06 Aug 2014 17:49:24 +0200, Lance Corrimal wrot

Re: [opensource-dev] someone get the blindfold off me please - where in the sourcecode is the spot where a "parcel full" message is created?

On Wed, 06 Aug 2014 17:49:24 +0200, Lance Corrimal wrote: > Am Dienstag, 5. August 2014, 16:11:11 schrieb Darien Caldwell: > > I'd suspect that the viewer simply makes a rez request to the Server, and > > the server makes the determination it can't be completed, and why. LIkely > > the server just

Re: [opensource-dev] someone get the blindfold off me please - where in the sourcecode is the spot where a "parcel full" message is created?

additionally i found this: fail Can't create object because \nthe parcel is full. This is the exact notification i get when i try to rez an object on a parcel that is full, the other one being the one i posted previously. Not sure about Viewer 1 but they seem to have different wording, you

Re: [opensource-dev] someone get the blindfold off me please - where in the sourcecode is the spot where a "parcel full" message is created?

Am Dienstag, 5. August 2014, 16:11:11 schrieb Darien Caldwell: > I'd suspect that the viewer simply makes a rez request to the Server, and > the server makes the determination it can't be completed, and why. LIkely > the server just sends back the error message via some sort of generic > callback.