search

COMP3122-2324-Project / Simpsyber

0 stars 0 forks source link

[FEATURE] Clarify or Remove Non-Functional Time Stop and Resume Button on HomePage #13

Open vincentforive opened 9 months ago

vincentforive commented 9 months ago

In the current design of the SimPsyber game, the time stop and resume button is present on all pages, but it does not perform any action when clicked under Home Page. This presence can be confusing for users, as it is unclear whether this is an intended feature or a bug. If the intention is to prevent gameplay modification from the home page, it may be more user-friendly to either remove the button from this context or provide a clear indication that it is disabled or not applicable.

https://github.com/COMP3122-2324-Project/Simpsyber/assets/84238772/6354cf5c-6714-41e8-925b-eb910648e4eb

Suggested Enhancement:

  1. Remove the Time Stop and Resume Button from the HomePage: If the button has no functionality in this context, removing it could prevent confusion.

  2. Disable the Button with a Tooltip Explanation: If there are scenarios where the button could be functional on the home page, disabling it and adding a tooltip explanation (e.g., "This feature is not available on the home page") could clarify its intended use.

SHEN22071 commented 8 months ago

I think this is a design flaw. When the timer is running and we switch from the Kanban interface to the Home interface, the timer stops, but the icon on the timer control button does not change to pause. However, we can still toggle the button on the Home interface. If the timer was paused before switching interfaces, accidentally switching to the play state on another interface can create the false impression that the timer is paused. When we switch back to the Kanban interface, we may not notice that the timer has started running again, potentially wasting a lot of time. Disabling the button is a good approach. Additionally, I suggest that when switching back to the Kanban interface from any other interface, the timer should always switch to the paused state.

madisunleung commented 8 months ago

I support the suggested enhancement idea. Unused features should not be accessible to avoid confusion. Furthermore, when users encounter pop-ups that require reading instructions or inputting data, it's uncertain whether the timer will continue running or pause. This inconsistency in user experience can be frustrating. It's essential to reevaluate this design flaw and determine when it's necessary to pause the timer. I believe that in any scenario requiring user input or reading, the timer should be paused to ensure a smoother and more predictable user experience.