1. we add menu actions 'manual' and 'about', so
you can click actions to open manual and about dialog.
2. we introduce timer task management feature, so
you can add, delete timer tasks to auto run task.
3. other style improvement in gui...
add date calendar popup so that user can select
the date more easily
fix some file dialog title display issue
default max diff time change to 30 minutes
This commit fixes memory management issues in the
ALMainWindow class where config window and
task threads were not properly deleted after use,
leading to continuously increasing memory usage.
The fix ensures that all GUI components are
deleted after close and background threads are
correctly terminated.
: adjust default browser size to prevent page scale issues
Extract the reservation decode logic into a separate
function within LibChecker to improve code structure
and enable more structured return values for
decision-making.
Testing of the refactored LibChecker revealed that
page scaling could cause unexpected behavior.
Change the default browser size from
1280x720 to 1920x1080 to resolve this.
Update dictionary key retrieval to use the correct
key 'mode/run_mode' instead of the outdated 'run/mode'.
This aligns the code with the recent configuration changes.
We introduce a new LibOperator which is used to check
if a given user date is available for reserve or check-in.
This is ready for the upcoming feature: 'Auto Check-In'.
Refactor run mode processing logic to improve
adaptability for new operations.
Introduce a dedicated "passed" status to
distinguish passed users instead of classifying
them as failed.
The previous implementation only considered the case when more than one nearest time exists,
so we introduced the prefer_early flag to decide which one to be selected.But the comparsion
mistakenly omitted the edge case when the difference is 0.
previous time that you can select the next day is 19:00, this may be
tensive, because the time rested to modify the reserve date is limited.
So in current commit, we change this into 18:00.
The previous implementation directly replaced the current
in-memory state of system and user configurations during
file loading. This behavior did not align with user
expectations, as it could discard unsaved changes made in the UI.
The fix ensures that loading a configuration file only
updates the internal in-memory state of system and user
configurations, preserving any unsaved UI modifications.