ACTION_UP事件无法识别，如何用OnTouchListener实现按钮触摸状态上报？

Hey there, let's troubleshoot why your ACTION_UP event isn't firing in your touch listener setup. I've dealt with this exact issue a few times, so here are the most likely fixes to get your events working properly:

1. Make Sure You're Returning true for ACTION_DOWN #

The biggest culprit here is usually the return value of the onTouch method. If you return false when handling ACTION_DOWN, Android assumes you don't care about any subsequent touch events (including ACTION_UP).

To fix this, ensure you return true at the end of onTouch, or specifically for ACTION_DOWN and ACTION_UP events. For example:

@Override
public boolean onTouch(View v, MotionEvent event) {
    int action = event.getAction();
    // Your existing switch case for button IDs here...
    
    // Keep the touch event stream alive by returning true
    return action == MotionEvent.ACTION_DOWN || action == MotionEvent.ACTION_UP;
    // Or just return true to consume all touch events for this view
    // return true;
}

2. Remove Conflicting OnClickListener #

If your buttons have both an OnTouchListener and an OnClickListener, the ACTION_UP event might be intercepted by the click listener. Android triggers the click event right after ACTION_UP, which can prevent your touch listener from processing it.

Either delete the OnClickListener entirely, or return true in onTouch when handling ACTION_UP to consume the event and block the click listener from firing.

3. Validate Your onControl Method Logic #

Double-check that your onControl method is actually handling the ACTION_UP event correctly. It's easy to accidentally only code for ACTION_DOWN. Add debug logs to confirm if the event is reaching onControl at all:

private void onControl(String controlTag, View v, MotionEvent event) {
    Log.d("TouchDebug", "Received action: " + event.getAction() + " for tag: " + controlTag);
    switch (event.getAction()) {
        case MotionEvent.ACTION_DOWN:
            sendToServer(controlTag, "TOUCH_START");
            break;
        case MotionEvent.ACTION_UP:
            sendToServer(controlTag, "TOUCH_END");
            break;
    }
}

If the log doesn't show ACTION_UP, the issue is in the onTouch method or event propagation. If it does show up, your server-sending logic might be the problem.

4. Check for Parent Layout Event Interception #

Sometimes a parent view (like a ScrollView or custom layout) might override onInterceptTouchEvent and steal the ACTION_UP event. If your buttons are inside a scrollable layout or a custom view, verify that the parent isn't intercepting touch events meant for your buttons.

You can test this by temporarily moving the button to a simple layout (like a LinearLayout) to see if ACTION_UP starts working.

Here's a revised version of your full code incorporating these fixes:

private View.OnTouchListener handleTouch = new View.OnTouchListener() {
    @SuppressLint("ClickableViewAccessibility")
    @Override
    public boolean onTouch(View v, MotionEvent event) {
        int action = event.getAction();
        switch (v.getId()) {
            case R.id.Abtn:
                onControl("BA", v, event);
                break;
            case R.id.Bbtn:
                onControl("BB", v, event);
                break;
            case R.id.Xbtn:
                onControl("BX", v, event);
                break;
            // Add other button cases here
        }
        // Ensure we keep receiving touch events
        return true;
    }
};

private void onControl(String controlTag, View v, MotionEvent event) {
    switch (event.getAction()) {
        case MotionEvent.ACTION_DOWN:
            // Logic to send touch start data to server
            sendToServer(controlTag, "TOUCH_ACTIVE");
            break;
        case MotionEvent.ACTION_UP:
            // Logic to send touch end data to server
            sendToServer(controlTag, "TOUCH_INACTIVE");
            break;
    }
}

// Example server send method
private void sendToServer(String tag, String state) {
    // Your network call logic here
}

内容的提问来源于stack exchange，提问作者Ido