Replies: 1 comment 2 replies
-
|
I don't think I want to disable them by default, users like to see it when they configure streams to know its working, and I would leave it on -- I'll think more about the best way to handle your alternative idea. Would a all detections off toggle on the live view that is stored in browser session be sufficient? That is how we handle the other user UI preference type settings, otherwise it gets a bit weird -- sure if you switch browsers you'd have to toggle it but a global toggle that lasts in local storage should be fine I think. I worry about settings polution or creating too much overhead, users settings vs system settings vs stream settings, etc. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Matt!
I have a small UI/UX suggestion regarding the Live View dashboard to help keep the interface clean.
Currently, the object detection overlays (the red bounding boxes and labels) are enabled by default on all camera cards. While it's awesome to see the AI working in real-time, when you have a dashboard full of active cameras, having all these boxes constantly flashing makes the screen very visually polluted and a bit overwhelming to monitor.
The current behavior uses the "eye" icon to hide/disable these overlays per camera.
Proposed Change:
Could you reverse this default behavior? It would be much cleaner if the detection overlays were disabled by default across all streams in the Live View. The "eye" icon would then serve to enable the overlays only on specific cameras when a user actively wants to check or debug the detections.
(Alternative idea: Perhaps a global toggle in the Settings could allow users to choose their preferred default state for Live View overlays).
This small tweak would make the main dashboard much cleaner and easier to monitor for standard viewing!
Thanks again for everything!
Beta Was this translation helpful? Give feedback.
All reactions