> 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. -- Mike C. _______________________________________________ Libsecondlife-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/libsecondlife-dev
