# \[IGN-15086\]Suggestion for our beloved Designer's Tag Browser **URL:** \ **Category:** Ignition\ **Tags:** designer\ **Created:** [December 10, 2025, 2:46pm UTC](https://forum.inductiveautomation.com/t/ign-15086-suggestion-for-our-beloved-designers-tag-browser/112731 "2025-12-10T14:46:36Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![SBL\_MC](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sbl_mc/32/56813_2.png) [@SBL\_MC](https://forum.inductiveautomation.com/u/SBL_MC)\ **Post date:** [December 10, 2025, 2:46pm UTC](https://forum.inductiveautomation.com/t/ign-15086-suggestion-for-our-beloved-designers-tag-browser/112731/1 "2025-12-10T14:46:36Z")
For safety reasons, I have suggestion: We have to click inside the tick box to change the state of a BOOL instead of anywhere in the value column. Or at least have the option to do so? I selected the row above my INT to show this. If your mouse pointer is just inside the blue area when intending to click the INT, it sets the bool to true. Can cause unwanted things to happen. Read/Write of course, need to be enabled to change the INT. Thoughts? 😊 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/b/3b8d82687c192c03231f36911cb72b9bd7e20720.png) ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [December 11, 2025, 3:32pm UTC](https://forum.inductiveautomation.com/t/ign-15086-suggestion-for-our-beloved-designers-tag-browser/112731/2 "2025-12-11T15:32:56Z")
You can put it in the ideas portal: > **[Inductive Automation Feedback](https://ideas.inductiveautomation.com/)** > > Give feedback to the Inductive Automation team so we can make more informed product decisions. Powered by Canny. ---
**Author:** ![Brian\_Seater](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/brian_seater/32/82110_2.png) [@Brian\_Seater](https://forum.inductiveautomation.com/u/Brian_Seater)\ **Post date:** [December 11, 2025, 4:39pm UTC](https://forum.inductiveautomation.com/t/ign-15086-suggestion-for-our-beloved-designers-tag-browser/112731/3 "2025-12-11T16:39:55Z")
Here’s an exiting idea for adding a confirmation to Boolean tag click. [https://ideas.inductiveautomation.com/ignition-features-and-ideas/p/tag-browser-boolean-checkbox](https://ideas.inductiveautomation.com/ignition-features-and-ideas/p/tag-browser-boolean-checkbox) ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [December 11, 2025, 4:57pm UTC](https://forum.inductiveautomation.com/t/ign-15086-suggestion-for-our-beloved-designers-tag-browser/112731/4 "2025-12-11T16:57:37Z")
> [@Brian\_Seater](#): > > adding a confirmation Eeewwww! Please, no! ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [December 11, 2025, 5:11pm UTC](https://forum.inductiveautomation.com/t/ign-15086-suggestion-for-our-beloved-designers-tag-browser/112731/5 "2025-12-11T17:11:57Z")
Yeah I don't like the confirmation either, but requiring a click on the actual checkbox instead of anywhere in that column seems reasonable. ---
**Author:** ![Brian\_Seater](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/brian_seater/32/82110_2.png) [@Brian\_Seater](https://forum.inductiveautomation.com/u/Brian_Seater)\ **Post date:** [December 11, 2025, 5:17pm UTC](https://forum.inductiveautomation.com/t/ign-15086-suggestion-for-our-beloved-designers-tag-browser/112731/6 "2025-12-11T17:17:43Z")
Requiring the click on the actual checkbox would be a huge help. I partially agree that adding a confirmation could get annoying pretty quickly, but the current “single click and it changed” is honestly pretty scary. One errant click and you just accidently changed a tag, and if it’s an OPC tag you just wrote a new value to a machine. All the other tag types require multiple actions to edit - double click, make the change, and hit enter. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [December 11, 2025, 5:21pm UTC](https://forum.inductiveautomation.com/t/ign-15086-suggestion-for-our-beloved-designers-tag-browser/112731/7 "2025-12-11T17:21:14Z")
> [@Brian\_Seater](#): > > you just wrote a new value to a machine. There is already a designer connection mode feature, that defaults to read-only, to catch errant writes from the designer. The OP's formulation is a nice middle ground, and matches the behavior of real UI checkboxed that are bidirectionally bound to tags. ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [December 11, 2025, 6:30pm UTC](https://forum.inductiveautomation.com/t/ign-15086-suggestion-for-our-beloved-designers-tag-browser/112731/8 "2025-12-11T18:30:44Z")
> [@pturmel](#): > > There is already a designer connection mode feature, that defaults to read-only, to catch errant writes from the designer. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/c/1cc2cce4ab0fd8c4cec3ad6335d685bcbb9fec1f.png) ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [December 11, 2025, 6:45pm UTC](https://forum.inductiveautomation.com/t/ign-15086-suggestion-for-our-beloved-designers-tag-browser/112731/9 "2025-12-11T18:45:20Z")
I'm on board with narrowing the click target to just the actual checkbox enough that I made it an actual feature ticket.