I would agree to the past few posts on this thread.
When a serious bug is found in my code, I have a responsibility to my customers
to fix that bug and do some initial testing before releasing it back to the
customer. That is what being a dedicated developer is all about.
Apple should have the same responsibility to its customers, many of whom are
developers partnering with Apple to get them where they are today.
The color picker bug is in the OS and Apple should simply fix it.
Jeremy Sagan
Sagan Technology
www.sagantech.biz
From: Martin Crane
Sent: Tuesday, November 29, 2016 5:24 PM
To: Jeff Evans
Cc: Mark Lucas ; carbon-dev@lists.apple.com
Subject: Re: FPShowHideFontPanel crash on Sierra
Just chiming in here… my app has a built-in text editor and Font Panel just
doesn’t work at all any more - nothing happens - but the spelling panel and
Check Spelling options crash my app. I’m guessing these are related? I will log
radars and post here if it helps?
-Martin
On 29 Nov 2016, at 22:18, Jeff Evans <jev...@ars-nova.com> wrote:
I hope it is not misuse of this list to add another voice to that of Mark -
we received two user complaints about the font panel problem in our legacy
apps, but it must have bothered many many more who didn't complain or who
didn't realize the problem was with the font panel - as far as they were
concerned, the computer or our software was just acting up. It took me a while
to realize the problem was in system code, and I didn't file a report either;
by that time Apple had heard about it. So certainly one should not take a low
number of bug reports as evidence that a problem is not causing much trouble.
Especially something so integral to so many older apps; any program offering a
font choice is likely to have people using that mechanism.
Jeff
On Nov 29, 2016, at 2:02 PM, Mark Lucas wrote:
On Nov 29, 2016, at 3:00 PM, carbon-dev-requ...@lists.apple.com wrote:
the fact that it existed through at least one major OS release prior to
being reported indicates that it’s not causing big problems for lots of people
- if it were, we’d have a lot more reports.
Hi Eric,
Please don’t take this personally, but while that's apparently a common
perception at Apple I feel compelled to respectfully point out that it’s not
even remotely true…
For example no matter how many users of our authoring tool experience a given
problem, you’re vanishingly unlikely to receive more than one bug report
documenting it. That’s because few of these folks have developer accounts, and
fewer of those who do will ever file a bug themselves about it (because they’re
busy, and without the source code they literally have no clue what’s going
wrong, where, or why, and use these tools specifically to avoid needing to). So
anything I file a report against (unless explicitly noted otherwise) typically
affects hundreds or thousands of loyal longtime Mac developers all over the
world. But if I can’t fix or work around a problem in Apple’s code they
complain only to ME, not to you (and I file the aforementioned lonely report,
which typically sinks without so much as a ripple).
Due to their work environments most of these folks are not ‘bleeding edge’
adopters either, so such a bug not being officially reported for an entire OS
release indicates little to nothing about how catastrophically show-stopping it
may ultimately prove to them and their users/employers.
That can (and does) delay or prevent entire organizations from updating their
OS or buying new machines that fatally break legacy in-house apps they depend
on (which often are a principal anchor to the Mac platform) that upgrading
would force them to rewrite from scratch. Not to mention SERIOUSLY pissing them
off, and forcing them to question their decision to live in a walled garden…
And I can’t possibly be the only one in this position, which means there’s
undoubtedly a whole flotilla of such ‘big problems for lots of people' that are
effectively invisible to ‘radar’ yet still have a significant and ongoing
negative impact on Apple’s customer/developer (ahem) loyalty and bottom line.
Just sayin’...
<<climbs down off soap box>>
-Mark
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (Carbon-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/carbon-dev/jevans%40ars-nova.com
This email sent to jev...@ars-nova.com
--
If this email is spam, please report it to
https://support.onlymyemail.com/view/report_spam/MTAxOTYyOjE5NDYwOTU1MzE6amV2YW5zQGFycy1ub3ZhLmNvbTpkZWxpdmVyZWQ
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (Carbon-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/carbon-dev/martincrane%40mac.com
This email sent to martincr...@mac.com
--------------------------------------------------------------------------------
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (Carbon-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/carbon-dev/info%40sagantech.biz
This email sent to i...@sagantech.biz _______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (Carbon-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/carbon-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
