Craig said: It's nice to know the developers completely ignored the comments about the extra button click when this was pushed to the dev server. The same comments were posted there. :-/ Asking for feedback doesn't mean it has to be accepted. But if there is a reason it has to be this way, please communicate why. Until then, I have to agree with Craig. If suggestions are not or cannot be implemented, it would be polite to communicate why. You asked for feedback. We ask for the same. In the meantime, I am in total agreement about this. Hiding simple set up options in drop down menus is clunky, slow and keeps GMs from quickly reading the state of the token. It makes sense for long lists like "Represents", but it is pointless to have for checkboxes. To show the needless complexity of this, look at the token bar dropdown menu. It has a sub-dropdown of its own! A drop down should communicate info: Represents, Token bar text overlay, bar location. These tell you info even if they are not open. To hide categories of options and controls in a drop down, particularly when they are important for troubleshooting, is detrimental to the usefulness of the interface.