Re: High Sierra Firmware Update

[Ben Kennedy]

> On Sep 26, 2017, at 7:25 AM, Richard Charles  wrote:
> 
> Question: Has anyone successfully upgraded the firmware an older Mac Pro when 
> installing High Sierra?

I upgraded my MacPro5,1 without incident. However, the subsequent installation 
progress just hung the computer when the progress bar was about 9/10 of the way 
through. (I left it on overnight and nothing else happened.) Hard rebooting it 
worked successfully. Maybe this was related to its conversion of my SSD to 
APFS? Who knows.

Anyway, this isn't Cocoa-related, so we probably shouldn't be discussing it on 
this list.

b

___

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: High Sierra Firmware Update

[Richard Charles]

> On Sep 26, 2017, at 8:25 AM, Richard Charles  wrote:
> 
> I have a 2009 Mac Pro with the firmware upgraded from MacPro4,1 B08 to 
> MacPro5,1 B03. It has been running macOS Sierra flawlessly for 9 months. Now 
> when installing macOS High Sierra I get the following message. 
> 
> "To install macOS High Sierra, a firmware update is required.”
> 
> So apparently High Sierra upgrades the firmware on Mac Pro 5,1 models.
> 
> 
> https://www.macobserver.com/news/mac-pro-macos-high-sierra-firmware-update/
> 
> Question: Has anyone successfully upgraded the firmware an older Mac Pro when 
> installing High Sierra?

Firmware upgraded to MP51.0084.B00 when installing macOS High Sierra. Starting 
computer from macOS Sierra Installer does not allow firmware to be upgraded. 
Must start computer from macOS Sierra then launch installer app and follow 
directions. Everything seems to be working fine.

--Richard Charles

___

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 state] must by used from the main thread

[Quincey Morris]

On Sep 26, 2017, at 08:19 , Jens Alfke  wrote:
> 
> You’re assuming it’s a synthesized getter, but there’s no reason it couldn’t 
> be a custom method that does arbitrary computation before returning the 
> value, and there’s no way to know whether that work is thread-safe or not.

It is, in a sense, “even worse” than that. Even with a synthesized getter, you 
might get a bad value, if it’s a non-synthesized, non-trivial setter. For 
example, it’s possible to pass an arbitrary number to the NSButton.state 
setter, but the getter is supposed to return one of three values (on, off, 
mixed). If the setter stores the input value transiently, before replacing it 
with the legal equivalent, that could lead to a failure in using the getter.

___

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 state] must by used from the main thread

[Jens Alfke]

> On Sep 26, 2017, at 1:16 AM, Tamas Nagy  wrote:
> 
> “state” of the NSButton is a NSInteger property, so that should be safe to 
> read from a background thread, right?

No. You can’t tell anything about a property’s implementation from its return 
type. You’re assuming it’s a synthesized getter, but there’s no reason it 
couldn’t be a custom method that does arbitrary computation before returning 
the value, and there’s no way to know whether that work is thread-safe or not.

—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

High Sierra Firmware Update

[Richard Charles]

I have a 2009 Mac Pro with the firmware upgraded from MacPro4,1 B08 to 
MacPro5,1 B03. It has been running macOS Sierra flawlessly for 9 months. Now 
when installing macOS High Sierra I get the following message. 

 "To install macOS High Sierra, a firmware update is required.”

So apparently High Sierra upgrades the firmware on Mac Pro 5,1 models.

 https://www.macobserver.com/news/mac-pro-macos-high-sierra-firmware-update/

Question: Has anyone successfully upgraded the firmware an older Mac Pro when 
installing High Sierra?

--Richard Charles

___

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 state] must by used from the main thread

[Gary L. Wade]

If you have an issue with one API reporting such an issue, write a radar, as I 
did for getting the application’s delegate when I encountered it. For a 
button’s state, however, there may be a better way to pass that value to a 
background thread, especially if the button should be setting a value somewhere 
else that can be atomic and which decouples your background thread from the UI.
--
Gary L. Wade
http://www.garywade.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: High Sierra

[sqwarqDev]

Fair enough.

I’d seen (and had) the issue with an existing installer during the beta updates 
and figured it was the same.

Glad you got it sorted!


Best


Phil
@sqwarq
> On 26 Sep 2017, at 20:25, Richard Charles  wrote:
> 
> 
>> On Sep 26, 2017, at 7:00 AM, sqwarqDev  wrote:
>> 
>> Likely you have a copy of the beta installer either on your boot drive or an 
>> attached periphery.
>> 
>> Delete that copy (or move it to another disk and unmount it), then do 
>> ‘Command-R’ to refresh the App Store page.
> 
> Actually I do not have a copy of the beta installer that I can find. 
> Apparently the link in the developer download area for the final release of 
> High Sierra area never got updated.
> 
> --Richard Charles
> 

___

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: High Sierra

[Richard Charles]

> On Sep 26, 2017, at 7:00 AM, sqwarqDev  wrote:
> 
> Likely you have a copy of the beta installer either on your boot drive or an 
> attached periphery.
> 
> Delete that copy (or move it to another disk and unmount it), then do 
> ‘Command-R’ to refresh the App Store page.

Actually I do not have a copy of the beta installer that I can find. Apparently 
the link in the developer download area for the final release of High Sierra 
area never got updated.

--Richard Charles

___

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: High Sierra

[sqwarqDev]

Likely you have a copy of the beta installer either on your boot drive or an 
attached periphery.

Delete that copy (or move it to another disk and unmount it), then do 
‘Command-R’ to refresh the App Store page. 


Best


Phil
@sqwarq



> On 26 Sep 2017, at 19:50, Richard Charles  wrote:
> 
> The developer downloads area has a button to download macOS High Sierra 10.13 
> 17A365 Sep 25, 2017. Clicking the button takes me to an App Store macOS High 
> Sierra Beta download. So how do I get the released version and not the beta?
> 
> --Richard Charles
> 
> ___
> 
> 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/sqwarqdev%40icloud.com
> 
> This email sent to sqwarq...@icloud.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: High Sierra

[Richard Charles]

> On Sep 26, 2017, at 8:50 AM, Richard Charles  wrote:
> 
> The developer downloads area has a button to download macOS High Sierra 10.13 
> 17A365 Sep 25, 2017. Clicking the button takes me to an App Store macOS High 
> Sierra Beta download. So how do I get the released version and not the beta?

I just discovered a solution.

Use this link to download.

https://www.apple.com/macos/high-sierra/

Click the Upgrade now button then click View in Mac App Store.


> On Sep 26, 2017, at 6:55 AM, David Delmonte  wrote:
> 
> Open the App Store and either: go to Featured, where you will see HS, or 
> search there.

That also works. Thanks.

--Richard Charles

___

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

High Sierra

[Richard Charles]

The developer downloads area has a button to download macOS High Sierra 10.13 
17A365 Sep 25, 2017. Clicking the button takes me to an App Store macOS High 
Sierra Beta download. So how do I get the released version and not the beta?

--Richard Charles

___

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 state] must by used from the main thread

[Tamas Nagy]

Makes sense, thanks Quincey.

Best,
Tamas

> On 2017. Sep 26., at 10:35, Quincey Morris 
>  wrote:
> 
> On Sep 26, 2017, at 01:16 , Tamas Nagy  > wrote:
>> 
>> but “state” of the NSButton is a NSInteger property, so that should be safe 
>> to read from a background thread, right?
> 
> Not necessarily. If the setter is thread-unsafe, then it’s possible that the 
> getter may retrieve an incorrect value.
> 
> It’s not clear whether Apple has audited methods to determine thread safety 
> (so that such reported errors represent an actual pitfall), or whether there 
> is a general restriction on settable properties of UI objects. Either way, 
> prudence dictates that you heed the warning and change the code.
> 
> Now that I think about it, getting a button state on a background thread does 
> seem like an odd thing to do. Except in the simplest of cases, it does seem 
> to open up the possibility of race conditions, since the “when” of the value 
> might matter, relative to the timing of the surrounding code.
> 

___

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 state] must by used from the main thread

[Quincey Morris]

On Sep 26, 2017, at 01:16 , Tamas Nagy  wrote:
> 
> but “state” of the NSButton is a NSInteger property, so that should be safe 
> to read from a background thread, right?

Not necessarily. If the setter is thread-unsafe, then it’s possible that the 
getter may retrieve an incorrect value.

It’s not clear whether Apple has audited methods to determine thread safety (so 
that such reported errors represent an actual pitfall), or whether there is a 
general restriction on settable properties of UI objects. Either way, prudence 
dictates that you heed the warning and change the code.

Now that I think about it, getting a button state on a background thread does 
seem like an odd thing to do. Except in the simplest of cases, it does seem to 
open up the possibility of race conditions, since the “when” of the value might 
matter, relative to the timing of the surrounding code.

___

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

[NSButton state] must by used from the main thread

[Tamas Nagy]

Hi there,

XCode 9’s new main thread checker feature found the possible issue mentioned on 
the subject line. Indeed there is a background thread that check’s the state of 
an NSButton subclass, but I’m wondering if this is a real issue - I understand 
the problems with changing the UI from a background thread, but “state” of the 
NSButton is a NSInteger property, so that should be safe to read from a 
background thread, right?

Thanks in advance!

Best,
Tamas
___

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