(This is odd. I did not receive a copy of my post and therefore assumed it had not posted. Clearly it did as you were kind enough to reply)
Happily I found the solution. This list earlier helped me to understand a problem which appeared in recent Mac OS, where radio buttons would all work as an automatic group (clicking one would turn off all the others), which is a pity if one wanted multiple groups. This turned out to be a new "feature" of Mac OS likely to affect other control libraries; triggered when a number of conditions were met including having the same actions. Which, since these are generated by a control library, they all had. The solution to THAT issue was to wrap each radio button in its own parent NSView, and place the NSView in the dialog rather than the radio button. Of course this requires managing two controls: the NSView (e.g. for moving the control) and the NSButton (e.g. for checking the button). The problem was that HIDING the control was still being applied to the NSButton. The NSView was remaining "visible" (though having no visual aspect) and intercepting clicks if it happened to be on top. The solution is of course to hide the NSView instead of the NSButton. Converting to an NSTabView would be difficult because the higher level control library manages visibility and expects to be able to do so at the level of individual controls. But it may be prudent to always disable NSControl based controls when they are hidden. Hope this helps anyone who finds a similar issue. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
