Add container visibility tracking functionality to Virtual Terminal helper #661
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…elpers - Implement methods to add, remove, and get the shown state of tracked containers in VirtualTerminalClientStateTracker. - Introduce a method to set the shown state of tracked containers in VirtualTerminalClientUpdateHelper.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes
Adds the ability for the tracker to manage container visibility. Without this functionality, showing or hiding a container requires using the send_hide_show_object() method, which sends a message to all connected clients instructing them to hide or show the specified container. With this new capability, the tracker can handle container visibility in a more efficient and centralized way, allowing it to run in a continuous loop without repeatedly sending messages to clients and overloading the bus, just as it already does with other objects managed by the tracker.
How has this been tested?
I have tested it by dynamically hiding and showing containers that contain different objects—for example, using a button to show or hide a container.