Android开发：多次点击增减按钮后仅保存最终数值的实现咨询

Great question! The problem you're facing is common with rapid button clicks—you don't want to flood your backend with unnecessary API calls for every single tap, just the final value once the user stops interacting. Here's a straightforward solution using a handler to debounce the save action:

Step 1: Declare Class-Level Variables #

First, add these variables to your Activity or Fragment to manage the delayed save:

private Handler handler = new Handler(Looper.getMainLooper());
private Runnable saveTemperatureRunnable;
private int temperature = 0; // Set your initial value here

Step 2: Modify Button Click Listeners #

Update your increment and decrement button listeners to update the UI immediately, cancel any pending save requests, and schedule a new save after a short delay:

Increment Button (btn_UP)

btn_UP.setOnClickListener(new View.OnClickListener() {
    @Override
    public void onClick(View v) {
        if (temperature < 32) {
            temperature++;
            // Update TextView right away for instant user feedback
            textViewTemperature.setText(String.valueOf(temperature));
            
            // Cancel any previously scheduled save to avoid duplicate calls
            if (saveTemperatureRunnable != null) {
                handler.removeCallbacks(saveTemperatureRunnable);
            }
            
            // Define the save action to run after the delay
            saveTemperatureRunnable = new Runnable() {
                @Override
                public void run() {
                    // Call your existing PHP API save method here
                    saveTemperatureToDatabase(temperature);
                }
            };
            
            // Schedule the save 500ms after the last click (adjust delay as needed)
            handler.postDelayed(saveTemperatureRunnable, 500);
        }
    }
});

Decrement Button (btn_DOWN)

btn_DOWN.setOnClickListener(new View.OnClickListener() {
    @Override
    public void onClick(View v) {
        if (temperature > 0) { // Adjust minimum value to match your requirements
            temperature--;
            textViewTemperature.setText(String.valueOf(temperature));
            
            if (saveTemperatureRunnable != null) {
                handler.removeCallbacks(saveTemperatureRunnable);
            }
            
            saveTemperatureRunnable = new Runnable() {
                @Override
                public void run() {
                    saveTemperatureToDatabase(temperature);
                }
            };
            
            handler.postDelayed(saveTemperatureRunnable, 500);
        }
    }
});

Step 3: Clean Up Pending Requests #

To avoid unnecessary API calls if the user leaves the screen before the delay completes, cancel the runnable in the lifecycle method:

@Override
protected void onDestroy() {
    super.onDestroy();
    if (saveTemperatureRunnable != null) {
        handler.removeCallbacks(saveTemperatureRunnable);
    }
}

How This Works #

• Every time the user clicks a button, we immediately update the temperature variable and the TextView so the user sees the change right away.
• We cancel any previously scheduled save request—this ensures only the last click's action will execute.
• We schedule a new save to run after 500ms (you can adjust this delay: shorter = faster save after last click, longer = more tolerance for rapid clicks).
• Once the user stops clicking for the full delay, the final temperature value is sent to your PHP backend.

Notes #

• Replace saveTemperatureToDatabase(temperature) with your existing code that sends the value to your PHP endpoint (use modern libraries like Retrofit or Volley instead of deprecated methods like AsyncTask).
• Test the delay value to find the sweet spot for your users' interaction patterns.

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