Change Details

In many activities where we have to implement an option where a user can choose to either automatically switch to next level when a level is successfully completed, or manually trigger an event to move to next level. Example activities; 1. number_sequence and its derivatives 2. erase activity and its derivatives ([[ https://invent.kde.org/education/gcompris/-/merge_requests/58 | MR Link ]]) Here, we are using an integer value named 'mode' to store whether the activity should be running in Automatic / Manual trigger mode. This might lead to unexpected value in the variable 'mode', which might be difficult to debug later. We propose to add a enum structure in the core activity dedicated for this purpose. In all future activities to be implemented, this would make it easy for us to add this option. (Originally proposed by @jjazeix [[ https://invent.kde.org/education/gcompris/-/merge_requests/58#note_190874 | here ]]

In many activities where we have to implement an option where a user can choose to either automatically switch to next level when a level is successfully completed, or manually trigger an event to move to next level. Example activities; 1. number_sequence and its derivatives 2. erase activity and its derivatives ([[ https://invent.kde.org/education/gcompris/-/merge_requests/58 | MR Link ]]) Here, we are using an integer value named 'mode' to store whether the activity should be running in Automatic / Manual trigger mode. This might lead to unexpected value in the variable 'mode', which might be difficult to debug later. We propose to add a enum structure in the core activity dedicated for this purpose. In all future activities to be implemented, this would make it easy for us to add this option. Originally proposed by @jjazeix [[ https://invent.kde.org/education/gcompris/-/merge_requests/58#note_190874 | here ]]

In many activities where we have to implement an option where a user can choose to either automatically switch to next level when a level is successfully completed, or manually trigger an event to move to next level. Example activities; 1. number_sequence and its derivatives 2. erase activity and its derivatives ([[ https://invent.kde.org/education/gcompris/-/merge_requests/58 | MR Link ]]) Here, we are using an integer value named 'mode' to store whether the activity should be running in Automatic / Manual trigger mode. This might lead to unexpected value in the variable 'mode', which might be difficult to debug later. We propose to add a enum structure in the core activity dedicated for this purpose. In all future activities to be implemented, this would make it easy for us to add this option. (Originally proposed by @jjazeix [[ https://invent.kde.org/education/gcompris/-/merge_requests/58#note_190874 | here ]]