There is a good bug in the signature calculations in setTextureCrop(int[] crop) function

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Make the the crop array like so eg. {anynumber,anynumber,11, -15}
2. After the calculation is done signature is -4. So be for now.
3. Now the bad thing comes when we pass for the same texture a new crop array 
like eg {anothernumber,anothernumber,11,-15}. BAAAM the signature is the same 
but the crop has another left,bottom values and that is bad cause the crop is 
not applied at all.

So the normal flow should be like applying the new crop. It seems like the 
signature calculation method lacks, for now the negative number and |= is the 
bad part.

Please share your thoughts on this.

Thanks.

Original issue reported on code.google.com by [email protected] on 20 Jul 2012 at 11:46