I think I see the issue.
In the code that calls maskTex.update(...) it passes
maskTex.physicalWidth() as the scan stride of the buffer, but the scan
stride of the buffer is based on the content size, not the physical
size. Thus, the checkUpdateParams() method overestimates how many bytes
are
Hi Johan,
Notes in line below...
On 3/8/16 6:14 AM, Johan Vos wrote:
We got a number of bug reports (on Android and iOS) reported by developers
using large images:
java.lang.IllegalArgumentException: Upload requires 2475266 elements, but
only 1549938 elements remain in the buffer
at com.sun.p
Hi everybody,
At wiki there is this statement:
Using X11 to obtain the EGL context, but acting as if we are the only
application. This path was implemented in the "Monocle" windowing
subsystem, which is available in the OpenJFX build, and will be part
of a future JDK for ARM release. This path was
You may track the progress of this work with this JIRA for now. We are
still investigating the scope and impact of this work. We may decide to
create a new JIRA and resolve this as a duplicate if we decide to go
with a better naming.
https://bugs.openjdk.java.net/browse/JDK-8090322
- Chien
Kevin,
(finally)
https://bugs.openjdk.java.net/browse/JDK-8147399
http://cr.openjdk.java.net/~ddhill/8147399/
--
David Hill
Java Embedded Development
"A man's feet should be planted in his country, but his eyes should survey the
world."
-- George Santayana (1863 - 1952)
As the Quantum author I will echo Johan that looking at the
QuantumToolkit.pulse() and QuantumRenderer.submitRenderJob() are good
places to start. Ignore the PaintCollector (Pain Collector :-) ) and pay
attention to the View Painters.
This article has good background.
http://fxexperience.com/
Given that development of JavaFX 9 will switch to JRE 9 completely
anytime soon I'm thinking of switching to JavaFX 9 and a JRE 9. However,
do the freely available JVMs for ARMv7 32bit have a JIT?
Maurice.
We got a number of bug reports (on Android and iOS) reported by developers
using large images:
java.lang.IllegalArgumentException: Upload requires 2475266 elements, but
only 1549938 elements remain in the buffer
at com.sun.prism.impl.BaseTexture.checkUpdateParams(BaseTexture.java:354)
at com.sun
Hi,
I think the best way to get started really depends on your personal
preferences (e.g. do you like to read code, docs, diagrams,...).
I can only comment on how I do it, but others may have other approaches:
First of all, you can run a simple JavaFX apps with lots of verbose info.
See com.sun.p
Great! In that case forget the patch I made, it doesn’t make sense until the
treeVisible property is implemented. Is there any jira ticket that I could
follow?
Thank you Jonathan.
From: Jonathan Giles [mailto:jonathan.gi...@oracle.com]
Sent: Dienstag, 8. März 2016 10:01
To: Cirujano Cuesta, Die
The plan is that a new public API will be developed that matches the
expectations, whilst retaining the existing treeVisible semantics in that API.
Chien will be looking into this in the coming weeks. At that point we can
properly fix these issues.
-- Jonathan
Sent from a touch device. Please e
Hi all,
As I understood in the comments(JDK-8094829, JDK-8094078), treeVisible is
buggy. Is it still buggy? If yes, is there intention to fix the treeVisible
behavior? In case of fixing this it could be used to fix this issue. If I am
not wrong, treeVisible is still used by Node, SwingNode and
12 matches
Mail list logo