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 for Bug 4680 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
The NSResponder class doesn't have the cancelOperation method. Perhaps this is by necessity, not sure.
The issue is that many of those methods are there as features that are not implemented directly by NSResponder but that might be implemented by some subclass, from the header file:
This category contains a large number of methods intended for use as key binding commands.
NSResponder does not implement any of them. NSTextView implements a certain subset of them (see the NSTextView.h header). Your responder subclasses can implement any that make sense. You can make up your own as well, but you should use these if the concepts map. If your view is key and uses key binding and the user types a key sequence which is bound to a command which is not implemented in your class, it is OK, nothing will happen by default.
I have not decided yet what is the right approach to bind these.