Skip to content

Add a temporary workaround for the CHIP#4554

Merged
benfry merged 1 commit into
processing:masterfrom
gohai:chip-XQueryBestCursor-workaround
Jul 28, 2016
Merged

Add a temporary workaround for the CHIP#4554
benfry merged 1 commit into
processing:masterfrom
gohai:chip-XQueryBestCursor-workaround

Conversation

@gohai

@gohai gohai commented Jul 1, 2016

Copy link
Copy Markdown
Contributor

Reported this to the CHIP team: Seeing some odd exception from deep within Java's awt classes ("Width (0) and height (0) must be non-zero"). This is triggered because the libX11 function XQueryBestCursor is returning a width and height of zero, which seems to be a bug. I am guessing that this will also pop up with other Java applications.

This makes things work on the CHIP w/ OS image 4.4 and latest packages. I also tested on OS X, but I am not familiar enough with the Tweak Mode to say for sure.

Reported this to the CHIP team: Seeing some odd exception from deep within Java's awt classes ("Width (0) and height (0) must be non-zero"). This is triggered because the libX11 function XQueryBestCursor is returning a width and height of zero, which seems to be a bug. I am guessing that this will also pop up with other Java applications.

This makes things work on the CHIP w/ OS image 4.4 and latest packages. I also tested on OS X, but I am not familiar enough with the Tweak Mode to say for sure.
@gohai gohai added the arm label Jul 1, 2016
@benfry benfry merged commit 80cb1e9 into processing:master Jul 28, 2016
@gohai gohai deleted the chip-XQueryBestCursor-workaround branch July 29, 2016 08:59
@github-actions

Copy link
Copy Markdown

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Jun 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants