Re: auto layout exception: Unable to create description in descriptionForLayoutAttribute_layoutItem_coefficient. Something is nil

2014-11-06 Thread Jonathan Mitchell 
Frame 13 indicates that you have a breaking constraint.
The framework bug (if such it be) is triggered on iOS 7.1 trying to log the 
breaking constraint.

12  Foundation  0x00010f2f420a NSLog + 148
13  UIKit   0x00010e86a097
-[UIView(UIConstraintBasedLayout_EngineDelegate)
engine:willBreakConstraint:dueToMutuallyExclusiveConstraints:] + 62

I would try and locate the breaking constraint and adjust my constrains 
accordingly.
The constraint may be breaking in all iOS builds, check the logs for layout 
warnings.

Obviously its is not desirable that the constraint issues crashes the app but 
if you can track it in the simulator I imagine that it is fixable.

Jonathan


> On 6 Nov 2014, at 01:41, Chuck Soper  wrote:
> 
> About a week ago, I turned on Auto Layout for xib file that contains a
> view. I added constraints and my subviews (some images and a label) were
> positioned exactly as I wanted. I thought that auto layout was great.
> Today, I discovered that the app crashes on iOS 7.1 using the simulator
> for an iPhone 5s. Console output is below. I'm using Xcode 6.1. Everything
> works fine on iOS 8.1. Xcode shows no warnings or errors for the
> constraints. 
> 
> I found two similar questions on Stack Overflow, but they didn't help me.
> http://stackoverflow.com/questions/26024906/unable-to-create-description-in
> -descriptionforlayoutattribute-layoutitem-coeffi
> http://stackoverflow.com/questions/14042016/ios-6-auto-layout-constraints-e
> rror-something-is-nil
> 
> Does anyone have thoughts how to solve this? If I can't find a solution, I
> may need to turn off auto layout and revert to using autoresizing.
> 
> Console output:
> 2014-11-05 11:26:32.602 SSP[20856:60b] *** Terminating app due to uncaught
> exception 'NSInvalidArgumentException', reason: 'Unable to create
> description in descriptionForLayoutAttribute_layoutItem_coefficient.
> Something is nil'
> *** First throw call stack:
> (
>   0   CoreFoundation  0x00011019c495
> __exceptionPreprocess + 165
>   1   libobjc.A.dylib 0x00010fa6599e
> objc_exception_throw + 43
>   2   CoreFoundation  0x00011019c2ad +[NSException
> raise:format:] + 205
>   3   Foundation  0x00010f432548
> descriptionForLayoutAttribute_layoutItem_coefficient + 145
>   4   Foundation  0x00010f4323bc
> -[NSLayoutConstraint equationDescription] + 216
>   5   Foundation  0x00010f432831
> -[NSLayoutConstraint description] + 297
>   6   CoreFoundation  0x00011015d1b9 -[NSArray
> descriptionWithLocale:indent:] + 345
>   7   Foundation  0x00010f2c414e
> _NSDescriptionWithLocaleFunc + 64
>   8   CoreFoundation  0x000110121244
> __CFStringAppendFormatCore + 7252
>   9   CoreFoundation  0x00011015f913
> _CFStringCreateWithFormatAndArgumentsAux + 115
>   10  CoreFoundation  0x0001101bfa5b _CFLogvEx + 
> 123
>   11  Foundation  0x00010f2f4276 NSLogv + 79
>   12  Foundation  0x00010f2f420a NSLog + 148
>   13  UIKit   0x00010e86a097
> -[UIView(UIConstraintBasedLayout_EngineDelegate)
> engine:willBreakConstraint:dueToMutuallyExclusiveConstraints:] + 62
>   14  Foundation  0x00010f4292ac -[NSISEngine
> handleUnsatisfiableRowWithHead:body:usingInfeasibilityHandlingBehavior:mutu
> allyExclusiveConstraints:] + 521
>   15  Foundation  0x00010f42a9b1 -[NSISEngine
> tryUsingArtificialVariableToAddConstraintWithMarker:rowBody:usingInfeasibil
> ityHandlingBehavior:mutuallyExclusiveConstraints:] + 353
>   16  Foundation  0x00010f2e226b -[NSISEngine
> tryToAddConstraintWithMarker:expression:integralizationAdjustment:mutuallyE
> xclusiveConstraints:] + 663
>   17  Foundation  0x00010f433180
> -[NSLayoutConstraint
> _addLoweredExpression:toEngine:integralizationAdjustment:lastLoweredConstan
> tWasRounded:mutuallyExclusiveConstraints:] + 275
>   18  Foundation  0x00010f2de1b0
> -[NSLayoutConstraint
> _addToEngine:integralizationAdjustment:mutuallyExclusiveConstraints:] + 204
>   19  UIKit   0x00010e85d591
> -[UIView(UIConstraintBasedLayout)
> _layoutEngine_didAddLayoutConstraint:roundingAdjustment:mutuallyExclusiveCo
> nstraints:] + 362
>   20  UIKit   0x00010e85d738
> -[UIView(UIConstraintBasedLayout)
> _tryToAddConstraintWithoutUpdatingConstraintsArray:roundingAdjustment:mutua
> llyExclusiveConstraints:] + 30
>   21  UIKit   0x00010e85d858
> -[UIV

Re: Closing window on Yosemite crashes (isFlipped)

2014-11-06 Thread Allan Odgaard 

On 30 Oct 2014, at 17:26, Fritz Anderson wrote:

I haven’t encountered this myself. This is stream-of-consciousness, 
adding the presence of convertRect:toView: in the trace as the 
immediate caller…


Thanks for your thoughts on the issue.

I haven’t pinpointed the exact cause of the crash, but I have learned 
that majority of the time, the crash happens if the window contains a 
WebView and that window has been previously closed (more than once).


So as a workaround I now recreate the window once it has been closed, 
rather than re-use it, and since I did this, I have only seen two 
crashes related to the isFlipped: (compared to thousdands from earlier 
versions).

___

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

best way to implement unlock features in app

2014-11-06 Thread sqwarqDev 
Apologies in advance. I'm sure this has been asked a million times before, but 
my google-fu has let me down, and that which I can find is all iOS related. No 
good for me as this concerns an OS X, non-App store app.

I have a reasonably well-developed free OS X app (i.e., by well-developed I 
mean I've got a stable user base), and I'm now wanting to add extra features 
that require purchasing a licence. This seems a common model, but I can't find 
any guidance on exactly how do I generate and test for valid licence keys at 
run time? 

I'm assuming that I enable the added features by checking for a bool that tells 
me whether a valid licence key exists in a plist file, but how do I check that 
the licence key in the plist is actually a valid one without "phoning home" 
every launch and scouring a database (that would seem to me to be both an 
expensive and flawed method, but i can't figure out how else it is done)?

Any help or pointers to previous answers to a similar question much appreciated.


Phil



___

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

Subclassing NSView in Yosemite?

2014-11-06 Thread Alex Hall 
Hello list,
I've subclassed NSView before, doing all my setup in init withFrame, and it 
works fine. Now, though, I'm using Swift in Xcode 6.1 to build a project 
against 10.10, and I'm getting an error that I need to implement 
initWithCoder:NSCoder.

The problem is that the documentation says nothing about this, so I'm not sure 
which initializer is called when. That is, where do I put all my setup to 
ensure it gets called? I'd rather not do it twice, since I'm afraid one or the 
other initializer could get called when I don't expect it and set things up as 
though the app had just launched.

I can't find much of anything on this initWithCoder requirement, so I'm at a 
loss as to where to set things up, and even what to pass the initializer for an 
NSCoder. I'd appreciate any links or other resources, or just explanations, 
anyone can provide. Thanks. Oh, here's the page I'm looking at, among many 
others on Google:
https://developer.apple.com/library/mac/documentation/Cocoa/Reference/ApplicationKit/Classes/NSView_Class/index.html#//apple_ref/doc/uid/2014-SW10

--
Have a great day,
Alex Hall
mehg...@icloud.com

___

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

Re: best way to implement unlock features in app

2014-11-06 Thread Bill Cheeseman 

> On Nov 6, 2014, at 9:00 AM, sqwarqDev  wrote:
> 
> I have a reasonably well-developed free OS X app (i.e., by well-developed I 
> mean I've got a stable user base), and I'm now wanting to add extra features 
> that require purchasing a licence. This seems a common model, but I can't 
> find any guidance on exactly how do I generate and test for valid licence 
> keys at run time? 


One answer, which I prefer, is to contract with a commercial e-commerce 
provider. I use eSellerate, a Digital River company, but others like Kagi are 
also available. They handle credit card, PayPal and similar processing and 
foreign currency exchange for you, and they normally produce the license keys 
and issue them for you. In the case of eSellerate, they provide OS X frameworks 
that you incorporate into your application to allow in-app purchase over the 
Internet and/or an Internet "Buy Now" button that you can incorporate in your 
website. You can choose from a variety of ways to have your application check 
the vailidity of a user's key, including online validity checks that are 
completely invisible unless the key is invalid or has been blackballed  (these 
systems seem to handle the user being offline occasionally just fine). They 
charge varying fees, perhaps something like 8% for an application with a modest 
customer base. I am delighted to pay this fee for the service I get -- I have 
no interest in figuring out how to implement a registration key issuing and 
monitoring framework myself.

You normally do have to write some code to integrate the e-commerce provider's 
software into your application, if you support in-app purchase. The eSellerate 
software comes with a very detailed programmer's guide and example code that 
makes the process reasonably easy.

-- 

Bill Cheeseman - b...@cheeseman.name

___

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

Re: best way to implement unlock features in app

2014-11-06 Thread sqwarqDev 

> On 6 Nov 2014, at 21:31, Bill Cheeseman  wrote:
> 
> 
> One answer, which I prefer, is to contract with a commercial e-commerce 
> provider.


Thanks, Bill. I had looked at Kagi in the past, but I didn't realise e-commerce 
providers would actually help with incorporating all the necessary the code. 
That's a weight off. 

Like yourself, I'm equally not worried about paying the commission, and it 
sounds like good value for money.

Thanks for the tip. 


Phil


___

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

Re: best way to implement unlock features in app

2014-11-06 Thread Allan Odgaard 

On 6 Nov 2014, at 15:00, sqwarqDev wrote:

[…] I can't find any guidance on exactly how do I generate and test 
for valid licence keys at run time?


I wrote this post about the general principles of a secure license key 
scheme: 
http://sigpipe.macromates.com/2004/09/05/using-openssl-for-license-keys/


Today you shouldn’t rely on openssl (as it’s deprecated on OS X). If 
you do not need to encrypt a payload (as in my post) then I suggest 
making the license be just a serial number followed by a signature on 
that number (maybe include a short hash of the owner name) — this 
should give a shorter license key and is also a more commonly supported 
operation of crypto libraries (generating a digital signature).

___

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

Re: best way to implement unlock features in app

2014-11-06 Thread sqwarqDev 
> On 6 Nov 2014, at 22:35, Allan Odgaard  wrote:

> I wrote this post about the general principles of a secure license key 
> scheme: 
> http://sigpipe.macromates.com/2004/09/05/using-openssl-for-license-keys/

Ahh nice. Thanks. That's the kind of nitty gritty I've been looking for and 
struggling to find. I'll probably go more towards Bill's suggestion in the end, 
but I love getting an understanding of this low level stuff works. 

I didn't understand this bit though:

> If you do not need to encrypt a payload (as in my post) then I suggest making 
> the license be just a serial number followed by a signature on that number 
> (maybe include a short hash of the owner name) 

If anyone can link me to a tutorial on how to create these signatures and 
hashes, that'd be really useful.

TIA


___

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

Re: Subclassing NSView in Yosemite?

2014-11-06 Thread David Duncan 

> On Nov 6, 2014, at 6:29 AM, Alex Hall  wrote:
> 
> Hello list,
> I've subclassed NSView before, doing all my setup in init withFrame, and it 
> works fine. Now, though, I'm using Swift in Xcode 6.1 to build a project 
> against 10.10, and I'm getting an error that I need to implement 
> initWithCoder:NSCoder.

NSView conforms to NSCoder, which is where this initializer comes from. It is 
generally used for unarchiving from a nib(xib) or storyboard.

> The problem is that the documentation says nothing about this, so I'm not 
> sure which initializer is called when. That is, where do I put all my setup 
> to ensure it gets called? I'd rather not do it twice, since I'm afraid one or 
> the other initializer could get called when I don't expect it and set things 
> up as though the app had just launched.
> 
> I can't find much of anything on this initWithCoder requirement, so I'm at a 
> loss as to where to set things up, and even what to pass the initializer for 
> an NSCoder. I'd appreciate any links or other resources, or just 
> explanations, anyone can provide. Thanks. Oh, here's the page I'm looking at, 
> among many others on Google:
> https://developer.apple.com/library/mac/documentation/Cocoa/Reference/ApplicationKit/Classes/NSView_Class/index.html#//apple_ref/doc/uid/2014-SW10
>  
> 

Typically you don’t call -initWithCoder:, except to call super implementations. 
Swift will take care of the latter for you, so you would just need to decode 
whatever information you need. Of course if your view doesn’t support any 
additional archiving above and beyond what NSView does, and you will never use 
it in a nib or storyboard, you can just leave the implementation empty.

> 
> --
> Have a great day,
> Alex Hall
> mehg...@icloud.com
> 
> ___
> 
> 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/david.duncan%40apple.com
> 
> This email sent to david.dun...@apple.com

--
David Duncan

___

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

Re: Subclassing NSView in Yosemite?

2014-11-06 Thread Kyle Sluder 
On Nov 6, 2014, at 6:29 AM, Alex Hall  wrote:
> 
> Hello list,
> I've subclassed NSView before, doing all my setup in init withFrame, and it 
> works fine. Now, though, I'm using Swift in Xcode 6.1 to build a project 
> against 10.10, and I'm getting an error that I need to implement 
> initWithCoder:NSCoder.
> 
> The problem is that the documentation says nothing about this, so I'm not 
> sure which initializer is called when. That is, where do I put all my setup 
> to ensure it gets called? I'd rather not do it twice, since I'm afraid one or 
> the other initializer could get called when I don't expect it and set things 
> up as though the app had just launched.

Read the Resource Programming Guide. -initWithCoder: is primarily called when 
unarchiving a view from a nib.

It’s kind of annoying that Swift makes you implement this method for all views, 
regardless of whether they’ll be in a nib or not, but it’s the only way the 
language can back up its safety guarantees.

--Kyle Sluder
___

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

Re: NSImage glowing

2014-11-06 Thread Alex Kac 
Thank you guys. This has helped a lot. I have a much better understanding of 
this now.

> On Nov 5, 2014, at 7:40 PM, Lee Ann Rucker  wrote:
> 
> 
> On Nov 5, 2014, at 5:53 PM, Wim Lewis  wrote:
> 
>> 
>> On Nov 5, 2014, at 3:43 PM, Alex Kac  wrote:
>>> BUT, in this case I’m just trying to get the glow on selected images, so 
>>> when I look at the code below all I see is that we’re getting the bitmap 
>>> and drawing it. I’m not understanding how that gets a glow.
>> 
>> 
>> It’s applied by NSButtonCell, which knows that if it’s in the selected state 
>> and its image is marked as a template image (or some set of conditions like 
>> that), then it should apply the glow when drawing.
>> 
>> I take it you’re trying to get this effect in some place other than inside a 
>> button? It’s not unreasonable to use an NSCell instance elsewhere— that’s 
>> essentially what cells are for, to abstract away some of the drawing 
>> behavior from the control view that uses them.
>> 
>> I think NSButtonCell uses NSSetFocusRingStyle() to provide the actual 
>> effect, but there may be additional magic in there.
> 
> If it's the blue that toolbar buttons apply to template images, it's not 
> using that - I don't know what it is, but they were only fuzzy in the first 
> OS that used them, and even then they used something else. There's also an 
> etched effect it gets, depending on which OS you're in. I sent Alex a sample 
> app that puts everything together.
> 
> But yes, for fuzzy blue around an icon, all you have to do is call 
> NSSetFocusRingStyle before drawing it. This doesn't change the icon colors, 
> though.
> ___
> 
> 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/alex%40webis.net
> 
> This email sent to a...@webis.net

Alex Kac - President and Founder
Web Information Solutions, Inc.

"I am not young enough to know everything."
--Oscar Wilde





___

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

Re: best way to implement unlock features in app

2014-11-06 Thread Allan Odgaard 

On 6 Nov 2014, at 16:53, sqwarqDev wrote:


I didn't understand this bit though:

If you do not need to encrypt a payload (as in my post) then I 
suggest making the license be just a serial number followed by a 
signature on that number (maybe include a short hash of the owner 
name)


If anyone can link me to a tutorial on how to create these signatures 
and hashes, that'd be really useful.


The blog post does give a step-by-step example of creating a hash of the 
owner name and then encrypting that with a private key (which is 
basically what a signature is).


Apple’s recommended API for the latter is documented here: 
https://developer.apple.com/library/mac/documentation/security/Conceptual/SecTransformPG/SigningandVerifying/SigningandVerifying.html


For creating a hash, you should probably use the CommonCrypto API. 
Googling for this returned a blog post by Mike Ash: 
https://www.mikeash.com/pyblog/friday-qa-2012-08-10-a-tour-of-commoncrypto.html


___

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

Vibrancy + Floating Group Row bug?

2014-11-06 Thread Seth Willits 

Some subviews of table view cells underneath a floating group row, in a vibrant 
table view have strange drawing:
http://sethwillits.com/temp/upshot/upshot_EnYMpCzT.png

Any thoughts?


(In the case of the pink text field, if I leave the text color as Control Text 
Color, then its boundaries aren't visible when under the group row.)


--
Seth Willits




___

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

Re: Vibrancy + Floating Group Row bug?

2014-11-06 Thread Seth Willits 
On Nov 6, 2014, at 12:20 PM, Seth Willits  wrote:

> Some subviews of table view cells underneath a floating group row, in a 
> vibrant table view have strange drawing:
> http://sethwillits.com/temp/upshot/upshot_EnYMpCzT.png
> 
> Any thoughts?
> 
> (In the case of the pink text field, if I leave the text color as Control 
> Text Color, then its boundaries aren't visible when under the group row.)


 Further experimentation shows if I subclass NSImageView and NSTextField and 
implement -allowsVibrancy to return YES, then their bounds are no longer 
visible in the group row.

However, the selected row's selection drawing still is, even if it's also a 
custom subclass which returns YES from -allowsVibrancy.
http://sethwillits.com/temp/upshot/upshot_AEyLyuSa.png

I can't seem to find any way to cure that, which in a real-world app where the 
group row :\

--
Seth Willits



___

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

Re: Closing window on Yosemite crashes (isFlipped)

2014-11-06 Thread Graham Cox 
Looks like an object is not removing itself as an observer of window 
notifications prior to deallocation. The notification center holds on to weak 
references, so these can become stale if not purposely removed, usually by a 
call to -removeObserver: as part of the -dealloc method (with ARC you would 
still need a -dealloc method, just not call [super dealloc]). But dealloc might 
be too late anyway.

With a bunch of related objects, such as a document, a window and the views in 
it, the exact order of destruction can mean that correctly untangling things 
from the notification center becomes tricky, and also may change from one OS 
release to another. Forgetting to -removeObserver: (or doing it in the wrong 
place) might work due to destruction order, then crash in a different OS 
version. I've run into this a few times. Usually finding where I'm calling 
-removeObserver: and making that happen earlier has led to a solution.

--Graham





On 31 Oct 2014, at 3:26 am, Fritz Anderson  wrote:

>> Application Specific Information:
>>  objc_msgSend() selector name: isFlipped
>>  Performing @selector(_close:) from sender _NSThemeCloseWidget 
>> 0x6119c560
>> 
>>  Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
>>  0   libobjc.A.dylib  0x7fff897530dd objc_msgSend + 29
>>  1   com.apple.AppKit 0x7fff8afb7d79 -[NSView 
>> convertRect:toView:] + 212
>>  2   com.apple.AppKit 0x7fff8b094b0e -[NSView(NSInternal) 
>> _updateLayerTreeRenderer] + 935
>>  3   com.apple.AppKit 0x7fff8b1c1548 -[NSView(NSInternal) 
>> _pauseLayerTreeRenderer] + 144
>>  4   com.apple.CoreFoundation 0x7fff830bacbc 
>> __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
>>  5   com.apple.CoreFoundation 0x7fff82fac1b4 _CFXNotificationPost + 
>> 3140
>>  6   com.apple.Foundation 0x7fff903acea1 -[NSNotificationCenter 
>> postNotificationName:object:userInfo:] + 66
>>  7   com.apple.AppKit 0x7fff8b0c70f4 -[NSWindow 
>> _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 4151


___

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

Re: Closing window on Yosemite crashes (isFlipped)

2014-11-06 Thread Allan Odgaard 

On 6 Nov 2014, at 23:40, Graham Cox wrote:

Looks like an object is not removing itself as an observer of window 
notifications prior to deallocation […]


The crash happens when I re-use the window with the WebView, i.e. no 
(major) objects are released.


The crash (almost) disappeared when I started to release the window (and 
the contained WebView) and then re-create it the next time it was needed 
(rather than just orderOut/orderFront the window).

___

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