On Mon, Mar 9, 2009 at 4:51 PM, kbeal10 <kbea...@gmail.com> wrote: > > I agree, having more than 2 threads seems to break from the > traditional paradigm, which is part of the reason it didn't seem like > a good answer. > > Since I wouldn't be able to have a ViewGroup in it's own thread, I > suppose the best solution is to create a SurfaceView that handles > drawing all of the dice. This is the way I had started, but liked the > idea of each die being a View in order to handle onTouchEvents. > Instead, the dice would simply be Drawables. Selecting one would mean > getting the coords of the onTouchEvent, and determining if that is on > top of a die.
That's a lot better - now develop the game, test it, release it, and (ahem, ahaha, mwuahahaha, ahem) profit ;) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
