I used the following printers together with JavaFX (versions 14.0.2.1
and 16-ea+1):
- cups-pdf under Ubuntu 18.04 (supports A4, all orientations, down to 0
margins)
- PDF24 under Windows 7 (supports A4, all orientations, down to 0 margins)
- Kyocera FS 2020DN under Windows 7 (supports A4, all
what printer, driver, and os?
did you call any methods to verify the values being passed are supported ?
-Phil.
> On Aug 17, 2020, at 9:01 PM, Tobias Oelgarte
> wrote:
>
> I just experimented with the JavaFX printing API and I'm confused about the
> results.
>
> If I request to print in lan
I just experimented with the JavaFX printing API and I'm confused about
the results.
If I request to print in landscape format the resulting page is still in
portrait mode, but rotated by 90 degrees and with mirrored
borders/margins. Is this intentional or should I file a bug report?
Simplif
On Mon, 17 Aug 2020 11:16:55 GMT, Bhawesh Choudhary
wrote:
> Added missing explicit no-arg constructors to classes in package
> javafx.scene, javafx.css and javafx.stage.
Marked as reviewed by kcr (Lead).
-
PR: https://git.openjdk.java.net/jfx/pull/283
On Mon, 17 Aug 2020 09:23:34 GMT, Bhawesh Choudhary
wrote:
> Added missing explicit no-arg constructors to classes in package
> javafx.beans.property, javafx.collections, javafx.util
> and javafx.util.converter in module javafx.base.
Marked as reviewed by kcr (Lead).
-
PR: https:
Remove
> On Aug 17, 2020, at 4:35 AM, openjfx-dev-requ...@openjdk.java.net wrote:
>
> Send openjfx-dev mailing list submissions to
>openjfx-dev@openjdk.java.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>https://mail.openjdk.java.net/mailman/listinfo/openjfx-dev
> or
Hi,
I can see in the implementation that
Platform.isSupported(ConditionalFeature.UNIFIED_WINDOW) is always false on
Linux [1].
So it seems that the issue does not occur in Linux because
StageStyle.UNIFIED is not supported there and so as per the specification
[2] the StageStyle is downgraded to St
On Mon, 17 Aug 2020 09:23:34 GMT, Bhawesh Choudhary
wrote:
> Added missing explicit no-arg constructors to classes in package
> javafx.beans.property, javafx.collections, javafx.util
> and javafx.util.converter in module javafx.base.
Marked as reviewed by nlisker (Reviewer).
-
PR
They are not required if you use the command line interface, but I find
that they do make things easier since I can run the gradle command from
Eclipse directly.
The instructions mention that if you import through gradle, you will need
to replace the Eclipse files with the ones in the repo because
Added missing explicit no-arg constructors to classes in package javafx.scene,
javafx.css and javafx.stage.
-
Commit messages:
- 8251353: Many javafx scenegraph classes have implicit no-arg constructors
Changes: https://git.openjdk.java.net/jfx/pull/283/files
Webrev: https://webre
Added missing explicit no-arg constructors to classes in package
javafx.beans.property, javafx.collections, javafx.util
and javafx.util.converter in module javafx.base.
-
Commit messages:
- 8251352: Many javafx.base classes have implicit no-arg constructors
Changes: https://git.ope
Hi,
Do we really use the Eclipse-Gradle-Tooling now? I think the reasons we
checked in all .product/.classpath files is that this did not work in
the past.
At least my Eclipse install I use for OpenJFX-Development does not have
the gradle-tooling installed and things work there just fine.
12 matches
Mail list logo