On Wed, Apr 1, 2015 at 10:50 PM, Scott Palmer swpal...@gmail.com wrote:
I seems like a decent compromise to defer to the native platform code that
will ultimately be used to process the file anyway. It seems a little
heavy, but the alternative is perhaps bloating the JavaFX API.
Yes
On Wed, Apr 1, 2015 at 9:48 PM, David DeHaven david.deha...@oracle.com
wrote:
I was a bit surprised that the metadata retrieval functionality
of javafx.scene.media.Media is only usable in conjunction with a player,
so
if I want to retrieve the dimensions of a video file I have to
On my retina MBP (10.8) I get 60fps for es2 and 44fps for sw. Are you
running a newer version of MacOS?
...jim
On 3/31/15 3:40 PM, Chris Newland wrote:
Hi Hervé,
That's a valid question :)
Probably because
a) All my non-UI graphics experience is with immediate-mode
Hi Damien,
The main problem is that the definition of a stroked path and the
definition of a filled path are at odds. If the default stroke width is
1.0 and the default stroke type is CENTERED, then the stroke is
centered on the outline of a path and half of it falls on either side of
the
Hi Kevin, Chien,
Please review fix for https://javafx-jira.kenai.com/browse/RT-40184
Link to webrev: http://cr.openjdk.java.net/~ekleyman/RT-40184/
Thanks,
Elina
If not is there a specific reason not
to offer this functionality independently of a player?
There were plans, there were also issues as we don't have a Java based mp4
parser so we're relying on the underlying platforms (e.g. QTKit,
AVFoundation, etc..) to provide that data, which
If not is there a specific reason not
to offer this functionality independently of a player?
There were plans, there were also issues as we don't have a Java based mp4
parser so we're relying on the underlying platforms (e.g. QTKit,
AVFoundation, etc..) to provide that data, which
On Thu, Apr 2, 2015 at 6:16 PM, David DeHaven david.deha...@oracle.com
wrote:
If not is there a specific reason not
to offer this functionality independently of a player?
There were plans, there were also issues as we don't have a Java based
mp4 parser so we're relying on the
