Michael Cortez wrote: >> Any time you are parsing a number from a string you should sanity check >> with exception handling around just that operation, or use a TryParse() >> function. I have to run now otherwise I'd fix it, maybe I will get to it >> later this evening. >> > > Ayup! > > This the code for reading wearable assets was submitted by someone else, > I have yet to run into this particular error (I don't have any wearables > that exhibit it.) If the wearable is copy'able I could use a copy of it > (dropped on Bot Ringo) so I can try to understand why the number isn't > where the decoder is expecting it. >
I will see if I can get a copy of one of the outfits from the bot owner (I just work here). Running 10 bots with 10 similar but different outfits, and it seems that all 10 had the same error. Would it be easier to change the line to spit debugging output if it has an error? John _______________________________________________ Libsecondlife-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/libsecondlife-dev
