On Apr 5, 2018, at 15:27 , Tom Doan <t...@estima.com> wrote: > > I checked and none of my stopModalWithCodes are being fired, so the result > code has to be coming off the system dialog. I did a kludge where I used 100 > and 101 for my own stop codes, and continued on 0 and 1, and that seemed to > work around this
This does sound like a bug, but it’s hard to know. Using different stop codes seems like a rational way to approach the problem. Other possibilities you might investigate: 1. Close the modal window before using the NSOpenPanel, then reopen it with a new modal session afterwards. 2. Display the NSOpenPanel as a sheet on the modal window, rather than a separate window. Is Carbon involved here in any way? This code looks like it was Carbon once, at least. _______________________________________________ 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
