On May 14, 2012, at 3:01 AM, blorecrafter wrote: > Is this a bug in Android/Monodroid or a gap in my implementation.
I have no idea. When it comes to things like this, unfortunately the "easy" solution is to rewrite the scenario in Java and see what Android/Java does. Mono for Android _should_ behave the same way (if it doesn't, that's a bug -- please file!), but for things like this the only way to know what's "right" is to see what Android/Java does (which may or may not be what the Android documentation states, assuming you can find any clear Android documentation...[0]). Not the best answer, I know... - Jon [0] Ha! _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
