but how should the gui tools know about that
e.g. Uavcan GUI Tool? You would have to hardwire that info into UavcanGUITool for ALL nodes, and whenever there comes a new node it needs to be reconfigured. Or you have to provide a “plugin” mechanism to make that info available.
Along the same lines one could have argued that also min,max,default are inappropriate
(which I in fact find way to restrictive to be really useful)
the “hidden” flag does not add any complexity. It is, as you say, with no benefit to the protocol (and in fact should not affect the protocol at all). However, that’s exactly so with ANY data carried by any message, any data adds complexity and is of no benefit to the protocol. Like min, max, default are data. Like a hidden flag would be data.
your argument doesn’t make any sense to me
