Good idea… However I just did this: 1. created a new document project 2. added to AppDelegate.m - (BOOL)applicationShouldOpenUntitledFile:(NSApplication *)sender { // Use this method to decide

I can’t swear to it, but I’m pretty certain this is a result of state restoration. Assuming you had at some previous point created an untitled window, then state restoration will recreate it at

macOS Yosemite 10.10.5; Xcode 6.4 In testing a vanilla Document app I tracked down what may be a bug in Cocoa. I expected that the app would not open an untitled file

The docs for that section do reflect the behavior, which you can see where the imageView size was set to the image size pre-layout by calling sizeToFit(). The problem is that in the auto layout world,

Steve, I haven’t explored your argument in a test environment, but the reason I said the call to setNeedsLayout() was in ‘addition’ to the call to sizeToFit() is the following excerpt from the

I'm glad it worked for you. One thing I noticed in your bug report is your mention of the *addition* of setNeedsLayout() to the existing sizeToFit(). I believe in the auto layout world that

Follow-up. Filed rdar:\\42735829 42735829 1Attachments Image Scaling When Returning From UIImagePickerController Created on July 30 2018, 12:01 PM for iOS + SDK Close

Steve, I know I’ve tried various things to force a re-layout, but obviously not that. Your solution worked in my app beautifully. Thank you so much for the suggestion. I will follow up by filing a

Hi Rick, Sorry I didn't reply sooner but the day job got in the way. I just tried out your test app on my iPhone. I ended up adding overrides of viewWillLayoutSubviews() and viewDidLayoutSubviews()

Slightly off topic, but... Veld or veldt(both Afrikaans and pronounced as “felt") refers to open, uncultivated grassland in southern Africa. “Bush" generally refers to thick vegetation consisting

Yup. It disturbs me too. But unless UIImagePickerController is doing something funky behind the scenes, then no, I am not doing anything on a background thread, nor am I explicitly making any changes

Guys, you are epic beyond all expectation. You do realize that this fucks security transactions for a large part of GMT + 1, right? Like major fucks, right? And through your help now we know.. There

AHA! I tried them all. Fun times! It is called the veld, is it not? Must I send you a photo from the Cape Town Fish Market which sadly is in Windhoek. Biltong saves lives

In a capital and it was jacked in Doha and Windhoek. Good data though.

You can try zdump -v /usr/share/zoneinfo.default/Africa/Windhoek To understand what your system thinks is the timezone in Windhoek, on my system the latest lines

It seems that Namibia recently changed the timezone permanently (cfr. https://support.microsoft.com/en-us/help/4074837/time-zone-and-dst-changes-in-windows-for-northern-cyprus-sudan-and-ton , sorry

Hi Alex, Sorry to hear of your problem. I’m in Johannesburg, I’ve included my setting below which may help. Note that I set the region to Apple Europe and the system detects Johannesburg (if it

AFAIK cell phones can determine time accurately via the cell transmission, so they are always accurate. Macs, and iOS devices without cell chips, on the other hand, don’t have that benefit nor a GPS

No worries about disagreements: you're looking at the code and I'm getting the condensed version in your description. Your comment about timing being an issue disturbs me since, ideally, the behavior

This sounds like something for Radar. So far, travelling the well-known world (the oddest being the canary islands), I have had any issues with that. I have been tracking the back-and-forth of the