Description:
In the current implementation, the user has to scroll to the top of the screen to stop the active time segment using the main "Stop" button. This is inconvenient, especially in a long list of time segments. To enhance usability, the "Continue" or "Start" button should dynamically change to a "Stop" button when a segment is active. This allows users to stop the active segment directly from the list, without needing to scroll up.
Acceptance Criteria:
When a segment is currently running (active), its associated "Continue" or "Start" button changes to a "Stop" button.
Clicking the "Stop" button in the segment row immediately stops the active segment, updates the segment end time, and recalculates the duration.
The main timer at the top is also stopped when the inline "Stop" button is clicked.
The button should revert to "Continue" after the segment is stopped.
Example Scenario:
User starts a segment from the list or from the main timer.
The "Continue" button for the active segment changes to a "Stop" button.
User clicks the inline "Stop" button in the segment row.
The segment is immediately stopped, the end time is recorded, and the duration is updated.
The button changes back to "Continue" to indicate that the segment can be resumed (like just now).
Benefits:
Improved user experience by reducing the need to scroll up to stop an active segment.
Provides a more intuitive interface for users familiar with inline actions.
Description: In the current implementation, the user has to scroll to the top of the screen to stop the active time segment using the main "Stop" button. This is inconvenient, especially in a long list of time segments. To enhance usability, the "Continue" or "Start" button should dynamically change to a "Stop" button when a segment is active. This allows users to stop the active segment directly from the list, without needing to scroll up.
Acceptance Criteria:
Example Scenario:
Benefits: