No takers?
> On 4 Nov 2015, at 22:19, 2551 <2551p...@gmail.com> wrote:
>
> I have an OSX app built on 10.11.1, deployment target 10.9. The app builds
> and runs without any AutoLayout issues or warnings from Xcode. I have
> ambiguities turned on.
>
> The problem is when I try to run the app
It's definitely encountering unsatisfiable constraints. It's trying to log the
problem, but getting an exception while composing a description string for one
of the constraints.
This is happening when the view is being added to its window. You've truncated
the stack trace so we can't tell why
I add a Spotlight Index Extension in my iOS app.
How can I run that extension?
___
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)list
> On 5 Nov 2015, at 20:33, Ken Thomases wrote:
> It's trying to log the problem, but getting an exception while composing a
> description string for one of the constraints.
Ahh, right. That’s what the ‘Unable to create description’ bit means. Thanks.
> You've truncated the stack trace
Full
> On Nov 5, 2015, at 6:50 AM, 2551 <2551p...@gmail.com> wrote:
>
>> or set a breakpoint on -[NSView(NSConstraintBasedLayout)
>> engine:willBreakConstraint:dueToMutuallyExclusiveConstraints:].
>
> Not sure I’m still following along. Are we talking symbolic breakpoint here?
> I tried that, but
I subclass NSTableView to catch -rightMouseDown
In -rightMouseDown I call [self clickedRow] which always returns -1 in a row or
not in row
What should I be doing to get the clicked row?
-rags
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.
> On Nov 5, 2015, at 12:35 PM, Raglan T. Tiger wrote:
>
> In -rightMouseDown I call [self clickedRow] which always returns -1 in a row
> or not in row
Yeah, you’re getting control before the base class has had a chance to set the
clickedRow property. (Have you tried calling the superclass met
We just added the first Swift file to our internal .framework, but now the
build is completely broken, with Xcode complaining “Umbrella header
‘OTCommon.h’ not found.”
/Users/dstenmark/Library/Developer/Xcode/DerivedData/OpenTable-aylpkukwtinirqbvfkphthelbglb/Build/Intermediates/OpenTable.build/
iOS 9.1, iPhone 5S, ObjC
I'm getting the following runtime warning due to multiple simultaneous
UIAlertControllers presenting at the same time:
Warning: Attempt to present on
which is already presenting
I know only one alert view controller can be presenting at a time, so the way I
thought
> On Nov 5, 2015, at 2:37 PM, Carl Hoefs wrote:
>
> iOS 9.1, iPhone 5S, ObjC
>
> I'm getting the following runtime warning due to multiple simultaneous
> UIAlertControllers presenting at the same time:
>
> Warning: Attempt to present on
> which is already presenting
>
>
> I know only on
You should present next UIAlertController when first one has been dismissed
(when UIAlertAction handler is called).
Tomek
> Wiadomość napisana przez Carl Hoefs w dniu
> 05.11.2015, o godz. 23:37:
>
> iOS 9.1, iPhone 5S, ObjC
>
> I'm getting the following runtime warning due to multiple simul
>
>
> I am building a program that requires me to look at airports. I have a site
> that one can browse by US State and a link for other countries. I’d like
> these links to show first. Then people can pick the airports they are most
> likely to use. I don’t really want to display the whol
That's the way. You should never need more than one presented at a time.
Sent from my iP6+
> On Nov 5, 2015, at 5:44 PM, Tomasz Muszyński wrote:
>
> You should present next UIAlertController when first one has been dismissed
> (when UIAlertAction handler is called).
>
> Tomek
>
>> Wiadomość
I don't want more than 1 alert presented at a time, of course, but they get
generated asynchronously. I thought dispatch_get_main_queue() would nicely
serialize any that occur. Thus David's comment that I'm just getting the
requests issued in a serialized fashion.
I'm not certain how to have a
Make a queue.
Sent from my iPhone
> On Nov 5, 2015, at 6:10 PM, Carl Hoefs wrote:
>
> I don't want more than 1 alert presented at a time, of course, but they get
> generated asynchronously. I thought dispatch_get_main_queue() would nicely
> serialize any that occur. Thus David's comment that
A queue of what? I would think that if only a single alert view can be
presented at a time, then iOS would serialize them and present them when
earlier ones complete. Is there no system-level solution to this?
-Carl
> Make a queue.
>
> Sent from my iPhone
>
>> On Nov 5, 2015, at 6:10 PM, Carl Hoe
Pretty sure the WWDC 2015 video on NSOperations tackles a similar scenario in a
quite elegant way. That might be worth investigating.
Peter
> On Nov 5, 2015, at 6:42 PM, Carl Hoefs wrote:
>
> A queue of what? I would think that if only a single alert view can be
> presented at a time, then iOS
It was working that way on UIAlertView, but on UIAlertController it has changed
and you need to serialize presentations manually.
tm
> Wiadomość napisana przez Carl Hoefs w dniu
> 06.11.2015, o godz. 00:42:
>
> A queue of what? I would think that if only a single alert view can be
> presented
Thanks for the tip, I'll look into it.
(As a general thought, though, it would appear that UIAlertController
should be a singleton app-wide, and it should manage its own serialized
presentation. Any other solution seems like external plumbing to fix a
design problem.)
-Carl
> Pretty sure the WWDC
A queue of content to be in each alerts.
I think we've all had this issue.
If there is more than one alert, then have a little number within the alert so
that you know it's alert #n of nn alerts.
And then each OK or Cancel button displays the next alert until they are gone.
Add the alert conte
20 matches
Mail list logo
