2

I'm trying to debug an issue caused by the change of a next responder of the main NSWindow. I have an internal NSView and a chain of custom NSResponder, however even after debugging and sticking breakpoints all over every setNextResponder, I never stop on one of them and all I do is just changing the window's style.

How can I get what changed the next responder? Is it just because of the style change? I can't find it in the documentation. Is there something I'm missing? What are the operations that can mess up with the responders chain?

spenibus
  • 4,339
  • 11
  • 26
  • 35
Stan
  • 57
  • 5
  • You can actually answer your own question to help future visitors, it would be more visible than a comment. Consider also linking the documentation and quoting the relevant parts. – spenibus Oct 01 '15 at 20:59

1 Answers1

3

Using watchpoints I found out exactly that [super setStyleMask:NSBorderlessWindowMask]; was setting to nil the _nextResponder of the NSWindow instance. In the official documentation I found out that Some style mask changes cause the view hierarchy to be rebuilt. I hope might be useful to someone else...

Stan
  • 57
  • 5