Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
I have an NSSearchFieldCell with an NSCancelButtonCell inside it. On Yosemite, I can successfully do something in the `Activated` event, whilst on Mavericks, it's not getting called.
Marius, can you post an example? I think we should try it in Xcode, because this sounds like an apple behavior change and not XM.
Just add any Activated handler to that piece. I don't know how to do things in Xcode.
Add an NSSearchField access the CancelButtonCell then add activated handler.
See that it's not called on Mavericks, but called on Yosemite.
I took a look at this issue and we are clearly setting the Target/Action in a macOS version independent manor.
Some research uncovered http://stackoverflow.com/questions/7365625/objective-c-nsbutton-setaction-not-working and that there were a number of responder changes in Yosemite.
I bet your Cells were not in the responder chain in the case where it was not working. Without an example I can't verify this concretely, but it fits what I've been able to find/prove.