It's even messier than that. It essentially specifies exactly how the
value is determined and there is not only no need to override it - doing
so just opens the door to violating its spec.
Both XToolkit and WToolkit have the exact same implementation which
complies with the documentation for
Ok then, I'll upload you a webrew patch for JDK8 later for review :)
I need a bug id I guess.
Cheers,
Mario
---
pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF
Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF
http://www.ladybug-studio.com
IcedRobot: www.icedrobot.org
Proud
Hi Artem,
> > While working a bit on cacio, we just found some new nice addition to the
> > Toolkit code, like this one:
> >
> > public boolean areExtraMouseButtonsEnabled() throws HeadlessException {
> > GraphicsEnvironment.checkHeadless();
> >
> > return Toolkit.getDefaul
On 10/15/2011 12:30 AM, Mario Torre wrote:
While working a bit on cacio, we just found some new nice addition to the
Toolkit code, like this one:
public boolean areExtraMouseButtonsEnabled() throws HeadlessException {
GraphicsEnvironment.checkHeadless();
return Toolkit.
While working a bit on cacio, we just found some new nice addition to the
Toolkit code, like this one:
public boolean areExtraMouseButtonsEnabled() throws HeadlessException {
GraphicsEnvironment.checkHeadless();
return Toolkit.getDefaultToolkit().areExtraMouseButtonsEnabled()