Client side actions?
-
I REALLY like GUI-O.
Though I've read the documentation back and forth, it seems that I have missed something.Is there a way in the GUI-o app to execute a request like @quitapp in response to a button click without round-tripping to the IOT source? That is, completely on the client side.
I would like, in this simplest case, to be able to exit the app if the TCP or BLE source becomes unavailable by executing an app-side button push.
I guess that I don't see how interface events can be processed before transmission to the servicing IOT source.
Where am I confused?
Dave
-
@wittend Hi!
Thank you for your positive feedback and support! If you have some time, you can also post a review on Google Store
Back to your question... There is currently no (event) handling for created widgets done on the client side. You can exit the app by pressing the back button until the prompt appears. Confirming the prompt will exit GUI-O application (just swipe upwards from the bottom of the screen to show the navigation / back key).
You can also clear the GUI by navigating to "Quick connect" menu and tapping "Tap to reset home screen" entry. This will clear all widgets.
Does this help you? If not, we can discuss this further.
Best regards,
kl3m3n -
@kl3m3n - This confirms my understanding of the documentation.
This would be a convenience for me, especially while developing my app. But I have found the workarounds that you mention.I suspect that there would be situations where I would like to do something on the client side without round-tripping to the source. Like touching a point on a chart and seeing the nearest measured value. But at this moment I don't have a crucial need.
I do see how local callbacks on the client side might complicate the tool and conceivably create security issues.
Dave