Skip to content

Conversation

@Manuel-Pol
Copy link
Collaborator

Fix of the bug reported in issue #250

The bug was fixed by changing the method GlobalContext.load(). Now, in the GlobalContext.load() function, if a new speedMultiplier is not provided, the previous value is kept, ensuring the pause/resume state remains consistent.

Rename of the "Switching Table" to "Forwarding Table"

Renamed "Switching Table" to "Forwarding Table" to align with terminology used in official documentation and texts.

Closes #250

Manuel-Pol and others added 3 commits May 28, 2025 17:14
… multiplier keep the same, so consistency between pause/resume button and the state of the motion in the simulator is maintained.refactor: change 'switching table' to 'forwarding table'.
@Manuel-Pol Manuel-Pol merged commit e76ac0e into main May 28, 2025
3 checks passed
@Manuel-Pol Manuel-Pol deleted the fix-pause-button-and-set-forwarding-table branch May 28, 2025 22:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Pause/Resume button inconsistent state when making 'New' network

3 participants