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.
The two functions at the end of guiMemoryOptimizer can be used to determine if the widgets on the tab you want to update are currently loaded into memory or visible on screen.
When a MQTT message arrives and you will want to update the gui accordingly, you need to know if the gui is loaded into memory and/or visible at this moment. These functions can then be called from the gui itself to check if an immediate update is needed/possible.
The other updates in guiMemoryOptimizer and guiBase change the behaviour of the panelindicators: when you click the middle panelindicator everything is the same as it was, you open the scene selector. But if you click on the partially visible indicators next to the current active panel this creates a opposite swipe gesture effect. So if you click on the right indicator, the next screen to the right swipes in view (if available) and vice versa for the left.
This is an addition to the swiping gestures so you can swipe and click.