You are trying to access it before any animation / transition takes place.
From the docs:
"The transition coordinator object associated with a currently active
transition or nil if no transition is in progress.”
(https://developer.apple.com/library/ios/documentation/UIKit/Reference/UIViewContro
> On Jun 22, 2016, at 1:36 PM, Alex Zavatone wrote:
>
>
> On Jun 22, 2016, at 1:59 PM, David Duncan wrote:
>
>>
>>> On Jun 22, 2016, at 11:54 AM, Alex Zavatone wrote:
>>>
>>>
>>> On Jun 22, 2016, at 10:51 AM, Alastair Houghton wrote:
>>>
On 22 Jun 2016, at 16:38, Alex Zavatone wrote
I have an application that has the requirement that the accesses to the server
be single threaded, i.e. the second request cannot go through until the first
request has completed. I am using NSURLSession and NSURLSessionDataTask. I have
set the Maximum Concurrent Host number in the configuration
The simplest way to do what you're asking is to not send another request until
your completion handler finishes.
--
Gary L. Wade (Sent from my iPhone)
http://www.garywade.com/
> On Jun 28, 2016, at 12:52 PM, Jim Adams wrote:
>
> I have an application that has the requirement that the accesses t
Unfortunately, with a multi threaded system, I cannot figure out a way to do
that. Ideas appreciated.
My network calls could come from any thread. I could see putting the request
into a queue, but how to I make the completion handler run on that same queue
so it remains blocked?
> On Jun 28, 2
I agree with Gary, but if something about your structure makes that difficult,
there’s also a queue suspend/resume approach:
let queue = dispatch_queue_create("", DISPATCH_QUEUE_SERIAL)
dispatch_async(queue) {
dispatch_suspend(queue)
myFirstNetworkCall({ (let result) in
dispatch_
Try using a mutex on your array of requests, when adding and removing them, and
only pull a request off the array when you're done with your completion handler
or when you have nothing in progress such as when you first start.
--
Gary L. Wade (Sent from my iPhone)
http://www.garywade.com/
> On J
I'm trying to implement the kind of chrome hiding that the Photos app on iOS
does: tap the image, and the status, nav, and tool bars (and background) fade
to black.
One of the animations available is to slide up. My view has (from top to
bottom): the status bar, nav bar, our main content view,
In the past I’ve used NSOperation for this — wrap each request in an async
NSOperation that only signals completion to its queue when its DataTask
completion handler is complete. Then you can blast a bunch of them at a
serial queue and they will come out serially until they are done.
On Tue, Jun 2
That may work, too, but it sure sounds like an awfully heavy way to do it.
--
Gary L. Wade (Sent from my iPhone)
http://www.garywade.com/
> On Jun 28, 2016, at 2:16 PM, Peter Tomaselli wrote:
>
> In the past I’ve used NSOperation for this — wrap each request in an async
> NSOperation that only
> On Jun 28, 2016, at 12:52 PM, Jim Adams wrote:
>
> I have an application that has the requirement that the accesses to the
> server be single threaded, i.e. the second request cannot go through until
> the first request has completed.
That’s pretty unusual. I take it this is a restriction o
Would a dispatch queue get what he's looking for?
On Jun 28, 2016, at 3:11 PM, Gary L. Wade wrote:
> The simplest way to do what you're asking is to not send another request
> until your completion handler finishes.
> --
> Gary L. Wade (Sent from my iPhone)
> http://www.garywade.com/
>
>> On Ju
Based on his desire to do this serially, he would need a serial queue, and he's
using asynchronous requests, so succeeding calls from his completion handler
with a simple array in queue pattern is simpler than shoehorning it all into
dispatch queues.
--
Gary L. Wade (Sent from my iPhone)
http://
> On 2016 Jun 28, at 13:16, Jim Adams wrote:
>
> the second request cannot go through until the first request has completed …
> with a multi threaded system, I cannot figure out a way to do that. Ideas
> appreciated.
dispatch_semaphore
Documentation is currently here:
https://developer.appl
I have not a lot of Cocoa experience here, so I am legitimately asking this
question, no snark intended: what’s the advantage to building a home-made
“serial” “queue” as opposed to just using an actual serial operation queue?
Haven’t you just described the first few steps one would take were one
When you try to mix synchronous (one request at a time) and asynchronous calls
(the task is set up and a completion handler is called after the original set
up calls) together like this, you have to start doing lots of extra management
across queues. This pattern can apply across other asynchron
Smarter people that we are have already spent the time to figure it out. Learn
the way they did it and profit from their work and experience.
There is a benefit to learning how to create the wheel. That time is not now.
Learn the wheel that we have.
On Jun 28, 2016, at 7:03 PM, Peter Tomase
17 matches
Mail list logo
