On Jan 19, 8:26 am, mort <[email protected]> wrote: > Only a blind shot: Did you check whether another instance of frustrum > is used? Like e.g. an accidental "float[][] frustrum = ..." in the > function or maybe even an if block or something similar, so a local > instance is used instead of the class member, parameter, or whatever > was intented.
There are only 4 occurrences of "new" in the file, the 4 at the top declaring the class fields. Also, hitting F3 on the "frustum" on line 180 in eclipse takes you to the field declaration as expected. I'm as sure as I can be that it's not a variable scope error. > However, I once had very similar troubles, though with an Array > instance instead of a native array. One day I added lots of additional > checks and Log.d to find the error, but after this, the error just > vanished without any of the checks becoming active. No idea what > happened there... Ah yes, the venerable heisenbug, scourge of programmers everywhere... Thanks to all for their thoughts, it at least appears that this is not embarrassingly obviously my fault, so I'm taking that as a step forward! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
