Re: Delays in awaking iOS app
On Fri, 31 Jan 2014 15:09:37 +0700, "Gerriet M. Denkmann" said: >The real problem is: iOS 7 ignores the first tap (if it comes too soon after >applicationDidBecomeActive: - "too soon" meaning: less than about a second). >Whereas iOS 6 records and processes all taps. I've noticed often, just in my ordinary iOS 7 life, that there is a problem with the system's handling of the showing and removal of the snapshot image (taken when the app was backgrounded and displayed as the app is reactivated). It takes a _very_ long time for this image to be replaced by the real interface, and meanwhile the app is not responsive because you're not _in_ the app: you're tapping on the snapshot. I wonder if that's what you're experiencing. m. -- matt neuburg, phd = m...@tidbits.com, http://www.apeth.net/matt/ Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.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
Re: Mismatched viewWillAppear/viewDidDisapper calls possible?
On Mon, 27 Jan 2014 20:15:37 -0800, Rick Mann said: >Should it ever be possible for there to be a mismatch between -viewWillAppear: >and -viewDidDisappear:? I suppose it is possible, since the docs say the >Appear methods aren't called in a popover in some circumstances (which I think >is really bad). Certainly sometimes +viewWillAppear:+ or +viewWillDisappear:+ arrives without the corresponding +viewDidAppear:+ or +viewDidDisappear:+. I filed a bug on this a couple of years ago and was told that this was working as expected: nothing in the contract guarantees that "will" will be followed by "did", they told me, though I tried to argue that the contract is right there in the name. As you say, it's really bad; please, please file a bug. The guy giving the WWDC videos on this topic a frighteningly cavalier attitude about this; he seems impervious to any understanding of the fact that we need coherent reliable order and sequence for these events. m. -- matt neuburg, phd = m...@tidbits.com, http://www.apeth.net/matt/ Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.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
Re: Animation on gesturing
On Sat, 25 Jan 2014 20:49:42 -0500, Eric Dolecki said: >The yahoo weather app does it for the iPad, you slowly swipe without releasing >and an animation is slowly moved through... It can be forward or reverse. How >exactly are they achieving that? Same goes for the iOS pull to refresh >animation for the stretched little do dad. See the section in my book on interactive custom animations. Here's some source code: https://github.com/mattneub/Programming-iOS-Book-Examples/blob/master/bk2ch06p296customAnimation2/ch19p620customAnimation1/AppDelegate.m m. -- matt neuburg, phd = m...@tidbits.com, http://www.apeth.net/matt/ Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.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
Re: Mismatched viewWillAppear/viewDidDisapper calls possible?
On Feb 3, 2014, at 10:42 , Matt Neuburg wrote: > On Mon, 27 Jan 2014 20:15:37 -0800, Rick Mann said: >> Should it ever be possible for there to be a mismatch between >> -viewWillAppear: and -viewDidDisappear:? I suppose it is possible, since the >> docs say the Appear methods aren't called in a popover in some circumstances >> (which I think is really bad). > > Certainly sometimes +viewWillAppear:+ or +viewWillDisappear:+ arrives without > the corresponding +viewDidAppear:+ or +viewDidDisappear:+. I filed a bug on > this a couple of years ago and was told that this was working as expected: > nothing in the contract guarantees that "will" will be followed by "did", > they told me, though I tried to argue that the contract is right there in the > name. As you say, it's really bad; please, please file a bug. The guy giving > the WWDC videos on this topic a frighteningly cavalier attitude about this; > he seems impervious to any understanding of the fact that we need coherent > reliable order and sequence for these events. m. Done: 15970823 -- Rick signature.asc Description: Message signed with OpenPGP using GPGMail ___ 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: NSArrayController - Remove and immediately deallocate objects
I need to quickly deallocate the objects because they will freed up other objects. If these latest objects don't get deallocated they receive some message when they should not. So I really need to deallocate the objects in the right order. Regards -- Leonardo > Da: Graham Cox > Data: Mon, 3 Feb 2014 10:10:18 +1100 > A: Leonardo > Cc: Cocoa Developers > Oggetto: Re: NSArrayController - Remove and immediately deallocate objects > > > On 2 Feb 2014, at 5:50 am, Leonardo wrote: > >> At this point the boxes should receive the dealloc message, but they do not >> receive that immediately, as I expected. > > Your expectation is wrong. Maybe the only 'fix' you need is to change it. > > >> I have been looking for a solution > > > What's the problem? > > --Graham > > ___ 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: NSArrayController - Remove and immediately deallocate objects
On Feb 3, 2014, at 11:49 AM, Leonardo wrote: > I need to quickly deallocate the objects because they will freed up other > objects. If these latest objects don't get deallocated they receive some > message when they should not. So I really need to deallocate the objects in > the right order. This sounds like a design problem in your object model. If the objects shouldn't be receiving another message, then they should unregister from it somehow. In other words, instead of triggering the cleanup when the objects are dealloced, they may need an explicit call like -cleanUp or -close or something. Then you can call that on them when they're removed, and they can do the cleanup immediately even if the actual dealloc isn't immediate. —Jens ___ 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: Mismatched viewWillAppear/viewDidDisapper calls possible?
Date: Mon, 03 Feb 2014 10:42:47 -0800 From: Matt Neuburg To: Rick Mann Cc: "cocoa-dev@lists.apple.com Dev" Subject: Re: Mismatched viewWillAppear/viewDidDisapper calls possible? Message-ID: Content-Type: text/plain; charset=us-ascii On Mon, 27 Jan 2014 20:15:37 -0800, Rick Mann said: Should it ever be possible for there to be a mismatch between -viewWillAppear: and -viewDidDisappear:? I suppose it is possible, since the docs say the Appear methods aren't called in a popover in some circumstances (which I think is really bad). Certainly sometimes +viewWillAppear:+ or +viewWillDisappear:+ arrives without the corresponding +viewDidAppear:+ or +viewDidDisappear:+. I filed a bug on this a couple of years ago and was told that this was working as expected: nothing in the contract guarantees that "will" will be followed by "did", they told me, though I tried to argue that the contract is right there in the name. As you say, it's really bad; please, please file a bug. The guy giving the WWDC videos on this topic a frighteningly cavalier attitude about this; he seems impervious to any understanding of the fact that we need coherent reliable order and sequence for these events. m. -- matt neuburg, phd = m...@tidbits.com, http://www.apeth.net/matt/ Done: 15971784 ___ 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
"App quit recording" notifications
At least a couple apps I have let me know that they've quit doing what they were told to do in the background (e.g., Fog of World tells me that it quit recording, and I should launch it again). I assume they're posting local notifications when -applicationWillTerminate:. Is this correct, or is there something else they might be doing? -- Rick signature.asc Description: Message signed with OpenPGP using GPGMail ___ 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: Delays in awaking iOS app
On 4 Feb 2014, at 01:35, Matt Neuburg wrote:
> On Fri, 31 Jan 2014 15:09:37 +0700, "Gerriet M. Denkmann"
> said:
>> The real problem is: iOS 7 ignores the first tap (if it comes too soon
>> after applicationDidBecomeActive: - "too soon" meaning: less than about a
>> second).
>> Whereas iOS 6 records and processes all taps.
>
> I've noticed often, just in my ordinary iOS 7 life, that there is a problem
> with the system's handling of the showing and removal of the snapshot image
> (taken when the app was backgrounded and displayed as the app is
> reactivated). It takes a _very_ long time for this image to be replaced by
> the real interface, and meanwhile the app is not responsive because you're
> not _in_ the app: you're tapping on the snapshot. I wonder if that's what
> you're experiencing. m.
My test app has a UILabel (called lastLine) at the bottom, and a button ("Tap
Me") below it.
In applicationWillResignActive: I do:
rootViewController.lastLine.text =
@"#";
In applicationDidBecomeActive: I do:
rootViewController.lastLine.text = @"Now!";
I start the app on iPad
Put the iPad to sleep.
Wake the iPad.
"slide to unlock" (now I see "#" getting changed to "Now!" after a
fraction of a second)
When I see either: (A) "Tap Me" or: (B) "Now!" I tap the button 4 times.
In case (A) only 3 button hits get recorded.
In case (B) all 4 button hits get recorded.
The button hits are spaced by about 0.2 seconds.
This seems to imply that when the applicationDidBecomeActive there is a time of
about 0.2 seconds, where it LOOKS responsive, but really it is NOT.
Maybe what I see is just (as you suggested) the "snapshot image", not the real
test app.
In a real app the following happens:
applicationDidBecomeActive
I see an obviously functioning button and tap it.
Nothing happens.
After about a second I realise something is wrong and tap the button again.
Now I get the expected reaction.
I curse the app, because the button is unreliable.
None of these problems occur with iOS 6.
Kind regards,
Gerriet.
___
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
