0.0.5dev and Earlier: Egg does not hatch if initial CALMenu scene is exited. #11

Closed
opened 2021-11-09 20:52:31 -04:00 by ZAdamMac · 1 comment
ZAdamMac commented 2021-11-09 20:52:31 -04:00 (Migrated from github.com)

Presumably this happens because we do not actually initialize or start the RTC without saving the output of the menu. Needs investigation.

Presumably this happens because we do not actually initialize or start the RTC without saving the output of the menu. Needs investigation.
ZAdamMac commented 2021-11-09 21:05:35 -04:00 (Migrated from github.com)

This is to do with line 392 of the current version of the calendar menu. This line is only reached if exiting via the set button, meaning that we never later evaluate for evolution.

The RTC is running and was validly set prior to the menu ever being drawn. This flag should be set regardless of how the menu is exited, as either condition SHOULD TECHNICALLY be valid. It merely exists to ensure that the evolution timer is not running before the user has had a chance to set the time (i.e., to force the egg stage)

This is to do with line 392 of the current version of the calendar menu. This line is only reached if exiting via the set button, meaning that we never later evaluate for evolution. The RTC is running and was validly set prior to the menu ever being drawn. This flag should be set regardless of how the menu is exited, as either condition SHOULD TECHNICALLY be valid. It merely exists to ensure that the evolution timer is not running before the user has had a chance to set the time (i.e., to force the egg stage)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
zadammac/PETI#11
No description provided.