Re: Defer opening documents until app is fully inited
On Sep 20, 2014, at 08:51:32, Jerry Krinock wrote: > I’m surprised that works. I think I was in a similar situation about 4 years > ago. > > http://www.cocoabuilder.com/archive/cocoa/293279-very-simple-demo-modal-dialog-causes-later-modal-session-to-crash.html?q=applicationWillFinishLaunching+Krinock#293279 I knew that looked familiar; I found the cocoa-dev thread earlier. :) > To summarize, what worked for me is to > > • Create my dialogs or whatever in an doEarlyChores method. > • Override -application:openFile: to invoke the doEarlyChores method and > return NO. > • Also invoke the doEarlyChores method early in > -applicationDidFinishLaunching. > • Put a lockout in doEarlyChores so it will only do its chores once. I ended up going at it from the other direction. If we haven't fully initted yet, I save off the files in application:openFiles: and open them later. -- Steve Mills office: 952-818-3871 home: 952-401-6255 ___ 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: Writing, then reading JSON
Well, thank you to anyone who spared any thought for this problem. After I
added the test below, with reconstitutedStructureDict and reconstitutedProj, I
discovered that everything started working and the files could be written to
and read from disk without error. Then I was able to go back and delete the
“reconstituted” test lines, and everything still works. I have no explanation.
--
Charles
On Sunday, September 21, 2014 at 19:10, Charles Jenkins wrote:
> Just as a test, I changed my writer method to immediately try to interpret
> the JSON data and reconstitute the project’s data:
>
> let structureDict = theProject.getStructureDictionary()
> let jsonData = NSJSONSerialization.dataWithJSONObject( structureDict,
> options: nil, error: outError )
> if let reconstitutedStructureDict =
> NSJSONSerialization.JSONObjectWithData( jsonData!, options: nil, error:
> outError ) as? NSDictionary {
> var reconstitutedProj =
> DocumentNode.readFromWrapperViaStructureDictionary( parentWrapper:
> theFileWrapper!, dictionary: reconstitutedStructureDict )
> }
>
> All this works: reconstitutedStructureDict is a copy of structureDict, and
> reconstitutedProj is a copy of theProject. And the JSON file that gets
> written out appears okay, so my problem seems to be that
> NSFileWrapper.regularFileContents isn’t returning usable data.
>
> —
>
> Charles Jenkins
>
>
> On Friday, September 19, 2014 at 11:45 AM, Charles Jenkins wrote:
>
> > My document structure is a file wrapper containing a bunch of RTF documents
> > and a file called structure.json which describes how they relate to one
> > another.
> >
> > I write out the structure file like this:
> >
> > let structureDict = theProject.getStructureDictionary()
> > let jsonData = NSJSONSerialization.dataWithJSONObject( structureDict,
> > options: nil, error: outError )
> >
> > writeFileToWrapper(
> > parentWrapper: theFileWrapper!,
> > filename: structureFileName,
> > data: jsonData,
> > err: outError
> > );
> >
> >
> > I’m not including the bodies of getStructureDictionary() or
> > writeFileToWrapper() because they seem to work just fine. The
> > structure.json file appears in my output package, and if I open it using
> > TextWrangler, I see exactly the JSON content I expect, stored in UTF8
> > encoding.
> >
> > The thing is, my app can’t read it back in. Here’s the function that’s not
> > working:
> >
> > override func readFromFileWrapper(
> > parentWrapper: NSFileWrapper!,
> > ofType typeName: String!,
> > error outError: NSErrorPointer
> > ) -> Bool
> > {
> > if let fw = parentWrapper.fileWrappers[ structureFileName ] as?
> > NSFileWrapper {
> > if let data = fw.regularFileContents? {
> > let debug: String = NSString( data: data, encoding:
> > NSUTF8StringEncoding )
> > let obj: AnyObject? = NSJSONSerialization.JSONObjectWithData( data,
> > options: nil, error: outError )
> > if let structureDict = obj as? NSDictionary {
> > var proj = DocumentNode.readFromWrapperViaStructureDictionary(
> > parentWrapper: parentWrapper, dictionary: structureDict )
> > theProject = proj
> > theFileWrapper = parentWrapper
> > return true
> > }
> > }
> > }
> > return false;
> > }
> >
> >
> > I expect I’ll find bugs in readFromWrapperViaStructureDictionary() if I
> > ever call it, but I never get that far.
> >
> > With Swift and Xcode, stepping line-by-line through code it a bit confusing
> > because the current line indicator bounces all around, sometimes appearing
> > on lines of code already executed. But to be best of my belief, my problem
> > is that obj can’t be converted to an NSDictionary. I inserted the debug:
> > String to see what’s read from the file, and it comes back as garbage.
> >
> > Is calling regularFileContents the wrong way to read up my JSON file?
> >
> > —
> >
> > Charles Jenkins
> >
>
___
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: Writing, then reading JSON
On Sep 22, 2014, at 10:07 AM, Charles Jenkins wrote: > Well, thank you to anyone who spared any thought for this problem. After I > added the test below, with reconstitutedStructureDict and reconstitutedProj, > I discovered that everything started working and the files could be written > to and read from disk without error. Then I was able to go back and delete > the “reconstituted” test lines, and everything still works. I have no > explanation. This is my favorite resolution to a mailing list problem in a while. Having run into plenty of “I have no explanation” issues myself over my career, I usually find that these most elusive mysteries betray their meanings after a good cup of coffee, a pizza, a distracting gaming session, or a long bike ride. To quote Nigel Tufnel from Spinal Tap: “…best leave it….unsolved.” Keep your chin up. You’ll figure it out. Cheers, Brad ___ 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: Writing, then reading JSON
This is bad. Do you/we have any idea why this magically started working?
Sent from my iPad
On Sep 22, 2014, at 1:07 PM, Charles Jenkins wrote:
> Well, thank you to anyone who spared any thought for this problem. After I
> added the test below, with reconstitutedStructureDict and reconstitutedProj,
> I discovered that everything started working and the files could be written
> to and read from disk without error. Then I was able to go back and delete
> the “reconstituted” test lines, and everything still works. I have no
> explanation.
>
> --
>
> Charles
>
>
> On Sunday, September 21, 2014 at 19:10, Charles Jenkins wrote:
>
>> Just as a test, I changed my writer method to immediately try to interpret
>> the JSON data and reconstitute the project’s data:
>>
>>let structureDict = theProject.getStructureDictionary()
>>let jsonData = NSJSONSerialization.dataWithJSONObject( structureDict,
>> options: nil, error: outError )
>>if let reconstitutedStructureDict =
>> NSJSONSerialization.JSONObjectWithData( jsonData!, options: nil, error:
>> outError ) as? NSDictionary {
>> var reconstitutedProj =
>> DocumentNode.readFromWrapperViaStructureDictionary( parentWrapper:
>> theFileWrapper!, dictionary: reconstitutedStructureDict )
>>}
>>
>> All this works: reconstitutedStructureDict is a copy of structureDict, and
>> reconstitutedProj is a copy of theProject. And the JSON file that gets
>> written out appears okay, so my problem seems to be that
>> NSFileWrapper.regularFileContents isn’t returning usable data.
>>
>> —
>>
>> Charles Jenkins
>>
>>
>> On Friday, September 19, 2014 at 11:45 AM, Charles Jenkins wrote:
>>
>>> My document structure is a file wrapper containing a bunch of RTF documents
>>> and a file called structure.json which describes how they relate to one
>>> another.
>>>
>>> I write out the structure file like this:
>>>
>>>let structureDict = theProject.getStructureDictionary()
>>>let jsonData = NSJSONSerialization.dataWithJSONObject( structureDict,
>>> options: nil, error: outError )
>>>
>>>writeFileToWrapper(
>>> parentWrapper: theFileWrapper!,
>>> filename: structureFileName,
>>> data: jsonData,
>>> err: outError
>>>);
>>>
>>>
>>> I’m not including the bodies of getStructureDictionary() or
>>> writeFileToWrapper() because they seem to work just fine. The
>>> structure.json file appears in my output package, and if I open it using
>>> TextWrangler, I see exactly the JSON content I expect, stored in UTF8
>>> encoding.
>>>
>>> The thing is, my app can’t read it back in. Here’s the function that’s not
>>> working:
>>>
>>> override func readFromFileWrapper(
>>>parentWrapper: NSFileWrapper!,
>>>ofType typeName: String!,
>>>error outError: NSErrorPointer
>>> ) -> Bool
>>> {
>>>if let fw = parentWrapper.fileWrappers[ structureFileName ] as?
>>> NSFileWrapper {
>>> if let data = fw.regularFileContents? {
>>>let debug: String = NSString( data: data, encoding:
>>> NSUTF8StringEncoding )
>>>let obj: AnyObject? = NSJSONSerialization.JSONObjectWithData( data,
>>> options: nil, error: outError )
>>>if let structureDict = obj as? NSDictionary {
>>> var proj = DocumentNode.readFromWrapperViaStructureDictionary(
>>> parentWrapper: parentWrapper, dictionary: structureDict )
>>> theProject = proj
>>> theFileWrapper = parentWrapper
>>> return true
>>>}
>>> }
>>>}
>>>return false;
>>> }
>>>
>>>
>>> I expect I’ll find bugs in readFromWrapperViaStructureDictionary() if I
>>> ever call it, but I never get that far.
>>>
>>> With Swift and Xcode, stepping line-by-line through code it a bit confusing
>>> because the current line indicator bounces all around, sometimes appearing
>>> on lines of code already executed. But to be best of my belief, my problem
>>> is that obj can’t be converted to an NSDictionary. I inserted the debug:
>>> String to see what’s read from the file, and it comes back as garbage.
>>>
>>> Is calling regularFileContents the wrong way to read up my JSON file?
>>>
>>> —
>>>
>>> Charles Jenkins
>
> ___
>
> 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/zav%40mac.com
>
> This email sent to z...@mac.com
___
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: NSButton checkbox type with the disable color is not visible in Yosemite
You can file a bug with Apple, it’ll probably get marked as a duplicate of rdar://17986405 "A radio button where we set the cell to NSBackgroundStyleDark is drawing in black when its window is not key, and the correct white when it is." On Sep 21, 2014, at 8:41 PM, Appa Rao Mulpuri wrote: > Hello List, > > I have a background view with the black color. And on top of it, I’ve placed > a Checkbox with the attributed title with the white color. In enabled mode, > text is visible with the white color, but if I make the button to disabled > mode (with setEnabled:NO) the text is not visible, only button with checkbox > is displaying. Though text is there and because of black background it is not > visible. Its happening only in Yosemite. > > Any way to solve this? I have tried it with by sub-classing and overriding > the setEnabled: method, but no luck. > > Thanks, > Apparao Mulpuri > This email and any attachments are confidential, and may be legally > privileged and protected by copyright. If you are not the intended recipient > dissemination or copying of this email is prohibited. If you have received > this in error, please notify the sender by replying by email and then delete > the email completely from your system. Any views or opinions are solely those > of the sender. This communication is not intended to form a binding contract > unless expressly indicated to the contrary and properly authorised. Any > actions taken on the basis of this email are at the recipient's own risk. > ___ > > 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://urldefense.proofpoint.com/v1/url?u=https://lists.apple.com/mailman/options/cocoa-dev/lrucker%2540vmware.com&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=yJFJhaNnTZDfFSSz1U9TSNMmxGyib3KjZGuKfIhHLxA%3D%0A&m=FYSlR23jRwPyK%2B1l%2F132yRiVrCJFFqZ3QXM%2FPsAXd3E%3D%0A&s=3c813723827d2055838e88eedec31ae96c75f9e3f021fd6eb77ac035d47165e8 > > This email sent to lruc...@vmware.com ___ 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
Building .ipa in XC6.01
We're having a hard time building an IPA file in XC6. From what I have read online, it seems to be a bug. We can make a .pkg file or an XCarchive file from our app. Any confirmation this really is a bug? Seems really unusual for such an important feature. We have already tried to add the LSRequiresiPhoneOS key in the Plist but that didn't do anything for us. Any other tips or related links appreciated. ___ 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
Multiple Today Widgets
Would there be any issue with creating an app that contains multiple Today Widgets? I've actually done it, and it works on the simulator and on my phone. But now with XC6, I can't build an archive so I am wondering if it is related to the .IPA build problem, or Apple won't allow multiple widgets for distribution? I see no technical reason why it would not. Thanks, Chris ___ 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: Updating iPad to 8.0 final
> On Sep 18, 2014, at 10:36, Rick Mann wrote: > > I have an iPad, 3rd gen, Wi-Fi + Cellular (AT&T). It's model A1430. I > downloaded the appropriate .ipsw file (iPad3,2_8.0_12A365_Restore.ipsw), but > iTunes refuses to update it, saying "The iPad “XXX” could not be updated > because the firmware file is not compatible." Are you sure you got the right image? I believe that iPad3,2 was the Verizon model, while iPad3,3 was the AT&T model. -- Clark Smith Cox III clarkc...@gmail.com ___ 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: Updating iPad to 8.0 final
On Sep 22, 2014, at 16:23 , Clark S. Cox III wrote: > >> On Sep 18, 2014, at 10:36, Rick Mann wrote: >> >> I have an iPad, 3rd gen, Wi-Fi + Cellular (AT&T). It's model A1430. I >> downloaded the appropriate .ipsw file (iPad3,2_8.0_12A365_Restore.ipsw), but >> iTunes refuses to update it, saying "The iPad “XXX” could not be updated >> because the firmware file is not compatible." > > > Are you sure you got the right image? I believe that iPad3,2 was the Verizon > model, while iPad3,3 was the AT&T model. It's very confusing. I know for certain it's an AT&T model. In the end, it appears my iPad is already at 8.0 final, although I don't know when that could have happened. Was b5 the same as final? -- Rick Mann rm...@latencyzero.com ___ 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: Updating iPad to 8.0 final
> On Sep 22, 2014, at 16:28, Rick Mann wrote: > > > On Sep 22, 2014, at 16:23 , Clark S. Cox III wrote: > >> >>> On Sep 18, 2014, at 10:36, Rick Mann wrote: >>> >>> I have an iPad, 3rd gen, Wi-Fi + Cellular (AT&T). It's model A1430. I >>> downloaded the appropriate .ipsw file (iPad3,2_8.0_12A365_Restore.ipsw), >>> but iTunes refuses to update it, saying "The iPad “XXX” could not be >>> updated because the firmware file is not compatible." >> >> >> Are you sure you got the right image? I believe that iPad3,2 was the Verizon >> model, while iPad3,3 was the AT&T model. > > It's very confusing. I know for certain it's an AT&T model. In the end, it > appears my iPad is already at 8.0 final, although I don't know when that > could have happened. Was b5 the same as final? No. Beta 5 was 12A4345d, while the final GM is 12A365. -- Clark Smith Cox III clarkc...@gmail.com ___ 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
-[UIApplication statusBarFrame] changes in iOS 8
I tried to find some documentation of a change, but can't It seems that the statusBarFrame returned in iOS 8 is different than in iOS 7. In landscape mode on iPad, I get a size of 20, 1024 in iOS 7, and 1204, 20 in iOS 8. Any suggestions on the best way to handle this? -- Rick Mann rm...@latencyzero.com ___ 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
crashing on "-[UIViewController presentViewController:animated:completion:] " on ios 8
Hi all, Getting a bunch of crash on presentViewController in iOS 8, has anyone run into similar issue? here is the stacks trace. Thread : Crashed: com.apple.main-thread 0 libobjc.A.dylib0x34043f46 objc_msgSend + 5 1 UIKit 0x2a0f2739 -[UIPresentationController runTransitionForCurrentState] + 444 2 UIKit 0x2a107a0b -[UIViewController _presentViewController:presentationController:animationController:interactionController:completion:] + 822 3 UIKit 0x2a10899f -[UIViewController _presentViewController:withAnimationController:completion:] + 2850 4 UIKit 0x2a10a4ab __62-[UIViewController presentViewController:animated:completion:]_block_invoke + 258 5 UIKit 0x29f07243 -[UIViewController presentViewController:animated:completion:] + 194 6 MyApp 0x00136441 -[LeftMenuViewController tableView:didSelectRowAtIndexPath:] (LeftMenuViewController.m:362) 7 UIKit 0x29f3d7c7 -[UITableView _selectRowAtIndexPath:animated:scrollPosition:notifyDelegate:] + 918 8 UIKit 0x29fef0df -[UITableView _userSelectRowAtPendingSelectionIndexPath:] + 194 9 UIKit 0x29ea11bd _applyBlockToCFArrayCopiedToStack + 308 10 UIKit 0x29e1d10b _afterCACommitHandler + 458 11 CoreFoundation 0x269505cd __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 20 12 CoreFoundation 0x2694dc8b __CFRunLoopDoObservers + 278 13 CoreFoundation 0x2694e093 __CFRunLoopRun + 914 14 CoreFoundation 0x2689c621 CFRunLoopRunSpecific + 476 15 CoreFoundation 0x2689c433 CFRunLoopRunInMode + 106 16 GraphicsServices 0x2dc4a0a9 GSEventRunModal + 136 17 UIKit 0x29e86809 UIApplicationMain + 1440 18 MyApp 0x000d9013 main (main.m:14) My code looks like this. GlobalSettingsViewController *c = [[GlobalSettingsViewController alloc] initWithGroupDataSource:self.dataSource]; navigationController = [[UINavigationController alloc] initWithRootViewController:c]; UIViewController *vc = UIApplication sharedApplication] delegate] window] rootViewController]; [vc presentViewController:navigationController animated:YES completion:nil]; ___ 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: -[UIApplication statusBarFrame] changes in iOS 8
> On 23 Sep 2014, at 9:20 am, Rick Mann wrote: > > I tried to find some documentation of a change, but can't It seems that the > statusBarFrame returned in iOS 8 is different than in iOS 7. In landscape > mode on iPad, I get a size of 20, 1024 in iOS 7, and 1204, 20 in iOS 8. > > Any suggestions on the best way to handle this? > That rather depends on what you’re using it for. Usually just working with topLayoutGuide etc etc makes all this stuff go away. However if you’re currently using that information for something … then … WWDC 2014 session 214, View Controller Advancements In iOS8, the venerable Bruce Nilo. ‘Changes to screen coordinates’ towards the end. I glossed over this bit when I saw it originally as it wasn’t instantly relevant to anything I’m up to but it definitely affects status bars and keyboard popup rectangles and there’s some APIs in there to convert from anything to anything else, one of which probably does what you need to convert what you’re getting back to what you were getting before, or at least alert you to having to handle it differently. ___ 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: crashing on "-[UIViewController presentViewController:animated:completion:] " on ios 8
On 22 Sep 2014, at 6:36 pm, Herman Chan wrote: > GlobalSettingsViewController *c = [[GlobalSettingsViewController alloc] > initWithGroupDataSource:self.dataSource]; > navigationController = [[UINavigationController alloc] > initWithRootViewController:c]; > UIViewController *vc = UIApplication sharedApplication] delegate] window] > rootViewController]; > [vc presentViewController:navigationController animated:YES completion:nil]; Is there a particular reason why you are fishing out the root view controller via the delegate singleton? Does it work properly if your LeftMenuViewController instance (the class which according to your trace is making the call) simply calls presentViewController on itself instead? b -- Ben Kennedy, chief magician Zygoat Creative Technical Services http://www.zygoat.ca ___ 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: crashing on "-[UIViewController presentViewController:animated:completion:] " on ios 8
Hi Ben, I have both in my app, both presenting from rootVC and just plain controller. I fish out the rootVC to get rid of warning like this "Presenting view controllers on detached view controllers is discouraged". I am seeing crash logs from both instance of presenting view controllers (both from rootVC and not), so that's probably not the issue here. Herman On 22 Sep 2014, at 22:14, Ben Kennedy wrote: On 22 Sep 2014, at 6:36 pm, Herman Chan wrote: GlobalSettingsViewController *c = [[GlobalSettingsViewController alloc] initWithGroupDataSource:self.dataSource]; navigationController = [[UINavigationController alloc] initWithRootViewController:c]; UIViewController *vc = UIApplication sharedApplication] delegate] window] rootViewController]; [vc presentViewController:navigationController animated:YES completion:nil]; Is there a particular reason why you are fishing out the root view controller via the delegate singleton? Does it work properly if your LeftMenuViewController instance (the class which according to your trace is making the call) simply calls presentViewController on itself instead? b -- Ben Kennedy, chief magician Zygoat Creative Technical Services http://www.zygoat.ca ___ 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: -[UIApplication statusBarFrame] changes in iOS 8
On Sep 22, 2014, at 18:38 , Roland King wrote: > >> On 23 Sep 2014, at 9:20 am, Rick Mann wrote: >> >> I tried to find some documentation of a change, but can't It seems that the >> statusBarFrame returned in iOS 8 is different than in iOS 7. In landscape >> mode on iPad, I get a size of 20, 1024 in iOS 7, and 1204, 20 in iOS 8. >> >> Any suggestions on the best way to handle this? >> > > That rather depends on what you’re using it for. Usually just working with > topLayoutGuide etc etc makes all this stuff go away. However if you’re > currently using that information for something … then … > > WWDC 2014 session 214, View Controller Advancements In iOS8, the venerable > Bruce Nilo. ‘Changes to screen coordinates’ towards the end. I glossed over > this bit when I saw it originally as it wasn’t instantly relevant to anything > I’m up to but it definitely affects status bars and keyboard popup rectangles > and there’s some APIs in there to convert from anything to anything else, one > of which probably does what you need to convert what you’re getting back to > what you were getting before, or at least alert you to having to handle it > differently. Sigh. Thanks. Again, Apple not documenting stuff where it should be documented. -- Rick Mann rm...@latencyzero.com ___ 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
