jmestxr/ped

ped's Issues

Event titles not displayed entirely on Calendar

Event titles with more than 3 characters cannot be captured entirely on the Calendar on the GUI.

This can appear as an inconvenience in some cases. Consider one example of this case where the prefix of the titles of two events is the same:

Performing `undo` command more than once throws an exception

Performing another undo command (after the first time) results in an exception being thrown.

No suitable error message is reflected in the command box indicating that the undo command only undoes the previous command (add, delete, edit, recur) and hence the second (and subsequent) undo command performed does not perform anything.

Exception thrown as indicated in the command line:

Adding of events that overlap in time is allowed

The UG stated that adding two events that overlap in time is not allowed. However, the user is still able to do so if the two events do not overlap entirely in time.

Version number of app not updated

Upon launching the app using java -jar command, the wrong version number of the app is indicated and might cause confusion to users. The correct version number according to the jar release should be v1.3.1.

Format of time not stated clearly under `Add New Event` section in UG

It is not clear if the start time and end time of the add command should be in 24h format or 12h format, according to the UG. One has to try this in the app itself to determine the correct time format.

Invalid command given is able to execute

An invalid command is given but the app still treats it as a valid command.

In this case, typing in help test will cause the app to treat it as a valid help command.

This might cause confusion among users.

Adding of event where start time comes after end time is nonetheless allowed

Even though it is stated in the UG that start time of the event added should come before end time, it is not specified clearly if it is the user's responsibility to ensure this is the case. Even if this is so, it would be better if the app does not allow such an event to be added, in case the user makes an unintentional typo on the start/end time that causes the start time specified to be after the end time.

User Guide:

App:

Expected functionality of `next` command not described entirely

For next command, if count provided is larger than the actual number of upcoming events, the execution of the command still works and all upcoming events are displayed. This could have been stated in the UG to avoid confusion.

App not entirely optimized for CLI users

The app is supposed to be optimized for users who can type fast. There is no command supported to traverse the calendar and one has to do so by clicking the Calendar buttons using a mouse.

Default screen size of GUI not large enough

The default screen size of the GUI upon launching the app is not large enough, causing parts of the GUI window to be cut off. One has to resize the GUI manually to view cut-off parts of the GUI.

In this case, the part cut-off indicates the path to the local storage of the app where all the event data is stored (./data/scheduler/json). An experienced user who wishes to modify the event data in the local storage might not be able to locate the local storage easily (especially if he/she is not experienced in JAR files or Java).

Invalid date not handled by app

An invalid date value is not handled by the app, resulting in an exception thrown that is not caught. No relevant error message is displayed.

Event title not displayed entirely

Event title that is too long is not displayed entirely in the GUI. It also causes event date to be cut-off. Users cannot view events with long titles and their dates in entirety.

Typo in User Guide's `GUI` section

There is a small typo in the header of the Calendar subsection of the GUI section.

Target user for product not specified clearly in UG

The target user for the product is not specified clearly in the user guide.

Wrong example command given in UG's `Add New Event` section

The example command given in the UG: add n/booked tennis court /2023-02-01 /2023-02-02 does not work and correspond to the correct format.