My question, which I asked in the JIRA, is whether this is Apple's bug
that we can expect them to fix, or whether they really did mean to nuke
a deprecated interface in an update release. Even with Apple's at-times
cavalier attitude regarding backward compatibility, it seems unlikely
that they would intentionally do this in a dot-dot release.
-- Kevin
Mike Hearn wrote:
Ugh. Seems this also nukes Chrome and Blender.
http://9to5mac.com/2014/11/30/google-chrome-crashes-hard-with-mac-os-10-10-2-beta-heres-the-fix/
I really wonder how an update that hard crashes Chrome can actually even
ship to beta. That seems like a total absence of app compat testing.
Seems like the issue is Apple changed an internal API but didn't update all
their own callers? So a bug in AppKit?
On Mon, Dec 1, 2014 at 10:09 PM, Tobias Bley <t...@ultramixer.com> wrote:
They work but the performance goes down to many native exceptions….
Tobi
Am 01.12.2014 um 22:04 schrieb Mike Hearn <m...@plan99.net>:
What happens to existing jfx apps once 10.10.2 starts rolling out? Do
they
all break?! I didn't see much discussion of the scope of this issue in
the
bug report.
On Mon, Dec 1, 2014 at 9:44 PM, Morris Meyer <morris.me...@oracle.com>
wrote:
Kevin and David,
Please review this patch for the issue added with the 10.10.2 software
patch that deals with part of the NSTouch interface changing.
--morris
JIRA - https://javafx-jira.kenai.com/browse/RT-39489
WEBREV - http://cr.openjdk.java.net/~morris/RT-39489.01/
