Can't form weak reference to a NSTextView about masonry HOT 9 CLOSED

Thanks for bringing this to my attention. I didn't know this limitation existed in Mac. I will have a think about it and try fix it for the next release.

from masonry.

Hi,

I went through some of my old projects and saw that it's really an edge case, where I use a NSTextView without wrapping it inside a NSScrollView. Maybe before you look further into this issue, you should consult with some other developers who are more familiar with OSX programming. For now I can wrap it inside a NSScrollView, even don't I really don't need the scroll view.

Just mentioning, cause this might not be an issue at all.

from masonry.

Cool closing for now. I'm not an mac developer so don't know what the appropriate solution is.
If any OSX devs want to chime in on an elegant solution we can reopen.

from masonry.

Would be nice if this worked for NSTextViews. I kinda need it and it seems silly to clutter the view hierarchy..

from masonry.

I agree, this would be a very nice bug fix, and wrapping in a scrollview seems very kludgy

from masonry.

+1

from masonry.

@cloudkite @kasperkronborg on mac you can't use weak references to NSTextView. Use assign instead. Here's a reference http://zpasternack.org/some-objects-dont-support-weak-references/

from masonry.

I think if Masonry did a check for isMemberOfClass and then used an assigned property that would be a solution, From the front end side though you either must use strong, or ensure it's added as a subview before assigning it, since it would otherwise not be retained.

from masonry.

@hamin That's what initially caused the issue. If you read my first post, I write that it is because you can't create weak references to NSTextView that Masonry crashes the app.

from masonry.