this doesn't make sense, i thought mutually exclusive action (check) groups are a common thing in an application ?? They are radio buttons for the menu, Why not support this in the GUI, and worse, why go from having a feature that is so common in development, to not having it? You know when people take key features out like this, it is those 'little' things that make developers just entering into your framework want to turn tail and go elsewhere...
I'm not trying to come off as lazy or anything, I understand it isn't too hard to add them manually from the code (which is easier than adding markup to the .ui) but still, keeping things separate (design, implementation) separate becomes an issue here. UI designers dont want to muck around in code where they don't belong, and coders don't want to muck around implementing code that should have been done in the UI by the designers in the first place... see where I'm going with this?? Hopefully one day this will be reconsidered for re-insertion.. If we can have signals/slots in the designer, then I'm sure it would be a walk in the park to put this back... :)