Hi Eric, When you get the ACTION_DOWN event, are you returning true? If not, this is probably the issue. The framework will only deliver future touch events (ACTION_MOVEs and the ACTION_UP) to that View if its touch listener or onTouchEvent returns true.
jason On Sat, Nov 1, 2008 at 5:00 PM, Eric <[EMAIL PROTECTED]> wrote: > > Thus far I've been using Buttons in a TableLayout, and calling > setOnTouchListener() to catch both presses and releases. Now I'm > trying to switch to ImageButtons. They work OK, but I wind up with an > annoying white border around the image. Even when calling setPadding > (0, 0, 0, 0), I still get some white border above and below the image, > even though all the images for my buttons in that TableRow are of the > same height. > > I tried using an ImageView instead of an ImageButton. It displays > without the border, but the onTouchListener is only getting called for > ACTION_DOWN but not ACTION_UP. > > I also tried subclassing ImageButton but having the constructor force > the style to 0. Again, it displays without the border, but the > onTouchListener doesn't get called for ACTION_UP. > > I can't seem to find documentation on how styles work, but do they > somehow affect whether ACTION_UP gets passed to the touch listener? > Other than that, I can't figure out why ImageButton would get > ACTION_DOWN but ImageView wouldn't. > > Thanks, > Eric > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
