ClarkBattle <[email protected]> wrote: The problem is that in order to do it with buttons would require 42 > tiny buttons, which would probably be a resource hogging solution. > Although a keyboard would give me the iPhone-keyboard-bubble-like > behavior, i dont think that we can place a keyboard in a static > location within a Layout, using it like a View. >
If you have button anxiety, look at a perpetual calendar. You will see that there are a finite number of month configurations. One idea might be to include one image for each configuration, making the body of the calendar a single image instead of 28/29/30/31 buttons. Then instead of detecting which button was pressed, obtain the coordinates of the press instead, and from that you derive which square was pressed. If memory serves me correctly there are only 14 or so different possibilities. P. V. Nasby
-- 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
