Re: assertion failure
Re: assertion failure
- Subject: Re: assertion failure
- From: Alex Zavatone <email@hidden>
- Date: Sun, 08 Apr 2018 13:58:02 -0500
Do you mind putting the program up on Github or something similar so any of us
can take a look?
Do you check for existence of the file before deleting, or check its properties
to see if it is deletable? I don’t know if this is required or not, just
submitting these as an option.
Cheers.
Alex Zavatone
> On Apr 7, 2018, at 5:06 PM, Steve Christensen <email@hidden> wrote:
>
> It's not uncommon to have a method throw an exception when you make a
> programming error so that you get immediate feedback. Not knowing offhand
> which method(s) were called, my guess would be that they're designed to
> always succeed if you specify the correct parameter values, so the assertion
> is letting you know that your parameters aren't correct.
>
> It's not like the case where, for example, you're trying to delete a file
> that may or may not be there. In general usage either of those cases is just
> as valid so the file system reports the error, if any, and lets your app
> decide what to do.
>
>
>> On Apr 7, 2018, at 1:18 PM, Alan Snyder <email@hidden> wrote:
>>
>> I understand that my program is doing it wrong. But is it normal to have an
>> assertion failure, rather than an error return?
>>
>>
>>> On Apr 7, 2018, at 12:04 PM, Rob Petrovec <email@hidden> wrote:
>>>
>>> It’s saying that you are doing it wrong. Utility windows cannot go full
>>> screen. You have yours set to go full screen. It shouldn’t be.
>>>
>>> —Rob
>>>
>>>
>>>> On Apr 7, 2018, at 10:24 AM, Alan Snyder <email@hidden>
>>>> wrote:
>>>>
>>>> I am getting an assertion failure notice on the console when running a
>>>> small test program:
>>>>
>>>> Assertion failure in -[AWTWindow_Panel _validateCollectionBehavior:],
>>>> /Library/Caches/com.apple.xbs/Sources/AppKit/AppKit-1504.83.101/AppKit.subproj/NSWindow.m:14741
>>>>
>>>> (This message is on 10.12.6, the details are different on 10.13.)
>>>>
>>>> When run under Xcode, there is more information: utility panels cannot be
>>>> fullscreen primary
>>>>
>>>> My question—does this represent a bug in AppKit that I should report, or
>>>> is it trying to help me by explaining that my program provided an
>>>> unsupported set of style bits when creating a window?
>>>>
>>>> Alan
>
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> 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:
>
> This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden