JavaFX 2.0 (questions lebel)

Similar Questions

• Assessment JavaFX: a few simple questions

  Hi all.
  
  I am to evaluate the possibility of migration of Swing to JavaFX development. I have a few simple questions, and simple answers will suffice.
  
  1 is mature enough to support all Project Professional JavaFX?
  
  2. JavaFX is a functional superset of Swing? I mean. Is capable enough to do any other thing that Swing can make JavaFX?
  
  3. is also well documented that the Swing JavaFX is? I mean especially the Swing tutorial and the Javadocs.
  
  4A JavaFX equivalent to "treeWillExpand" event? Also important in my case.
  
  5 a JavaFX frames internal for the development of MDI?
  
  6a JavaFX equivalent of JFormattedTextField? I use this component intensively for the validation of the data and formatting.
  
  7A the JavaFX AutoComplete text field component? Or is it difficult to develop a custom for this component?
  
  8. is it is possible to mix different styles of text (i.e. text color) in a text field component?
  
  9 is it difficult to create custom components and extend/decorate existing ones?
  
  10. is the beta for Linux mature enough to start trying? Can I use Netbeans with the current beta on Linux?
  
  Thank you!
  Antonio.

  I'll take a shot at answering them, some of them are probably better answered by one of the developers if:

  1. it seems stable and has a feature set large enough should allow you to create the lack of parts yourself

  2 JavaFX and Swing are unrelated to each other. JavaFX has its focus more on the provision of outstanding visual effects without trying to look the same as other applications on your platform. For example, control of JavaFX table doesn't have a built-in filter support and sort - it's something you can do yourself with appropriate templates.

  3. There are some examples out there already but no where near as many Swing. However, the Javadocs seem good enough, I could usually find what I wanted there.

  4 are not specifically, I think, but I'm sure that you should be able to veto over enlargement, by changing the State where you receive when a node is open or by consuming the appropriate event. Better write a small test for this program to see if you can do what you want - and if not, a feature to apply.

  5 I don't know well.

  6 No.

  7 there not. It is not too difficult to develop custom components.

  8. not directly I think, but a combination of FlowLayout + text objects must be able to do what you want.

  9. I developed some custom components, mainly by combining other components and that seems pretty easy. I don't know how you can change the functionality of a component exist (such as change the text field component in a text formatted field or who can use several colors; you will probably have to create your own skin for more delicate changes. Skin isn't very well documented.

  10. I do not know this.

• Questions about JavaFX, Swing, Touch and Netbeans

  Hi all. I'm trying to implement a touch support with JavaFX within a Netbeans application and met with a wall of problems.

  When running through JavaFX, everything works fine. Touch events are recorded and processed as expected. However, it seems that the JFXPanel who lives my scene in, or the Netbeans window system itself, interferes with key events.

  The Panel is multitouch. I mainly work with JavaFX obtaining buttons to work properly.

  • Committee will draw mouse down and mouse released event, but the event of mouse button is raised only AFTER the finger is removed from the Panel. In my mind, the mouse down event should pull your finger touches the Panel, as this event is triggered when you click with the mouse button otherwise. This of course could very well have nothing to do with Java, Swing or Netbeans, since it's the BONE that fires the original event.
  • The Panel goes off the pressed key, touch stationary and released touch events correctly, but these events are not detected with JavaFX in Netbeans/Swing.
  • The onAction event behaves the way the mouse pressed event. Tire only after removing your finger, not to touch.
  • If you move your finger (within the limits of the button) after a touching, onAction and the mouse goes off. But only if.

  Does anyone have experience with the creation of tactile support JavaFX in Netbeans framework?

  It is on 7u25, Win7 Enterprise Java.

  OK, so there's actually a windows control panel to change settings touch. Buried in a settings dialog box is the option to disable press it and hold for right-click fully function. This causes a mouse down event to be fired as planned on the button down.

  So, the solution is to disable the right click of press and hold Windows itself. Just enter 'touch' in the search box and you should see an option "Change touch input parameters" in the control panel.

• [JavaFX] Editable TreeTableCells

  Hello

  I want to implement a TreeTableView where the cells in a column can be changed according to the other properties of the displayed object.

  Bat I would control it via isCellEditable() method of TableModel.

  What is the recommended way to make thin in JavaFX?

  Here's a NBS that failed the behavior desired.

  Could you please someone add the lines of bfing in there?

  /*
   * //from www.java2s.com Copyright (c) 2008, 2014, Oracle and/or its affiliates. All rights reserved. Use is
   * subject to license terms. This file is available and licensed under the following license: Redistribution
   * and use in source and binary forms, with or without modification, are permitted provided that the following
   * conditions are met: - Redistributions of source code must retain the above copyright notice, this list of
   * conditions and the following disclaimer. - Redistributions in binary form must reproduce the above
   * copyright notice, this list of conditions and the following disclaimer in the documentation and/or other
   * materials provided with the distribution. - Neither the name of Oracle nor the names of its contributors
   * may be used to endorse or promote products derived from this software without specific prior written
   * permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR
   * IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
   * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE
   * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
   * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
   * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
   * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
   * THE POSSIBILITY OF SUCH DAMAGE.
   */
  import java.util.Arrays;
  import java.util.List;
  
  import javafx.application.Application;
  import javafx.beans.property.BooleanProperty;
  import javafx.beans.property.SimpleBooleanProperty;
  import javafx.beans.property.SimpleStringProperty;
  import javafx.scene.Group;
  import javafx.scene.Scene;
  import javafx.scene.control.TreeItem;
  import javafx.scene.control.TreeTableColumn;
  import javafx.scene.control.TreeTableView;
  import javafx.scene.control.cell.CheckBoxTreeTableCell;
  import javafx.stage.Stage;
  
  public class FxMain extends Application {
  
      List<Employee> employees =
              Arrays.<Employee> asList(new Employee("Ethan Williams", "[email protected]", false),
                      new Employee("Emma Jones", "[email protected]", false),
                      new Employee("Michael Brown", "[email protected]", true),
                      new Employee("Anna Black", "[email protected]", true),
                      new Employee("Rodger York", "[email protected]", false),
                      new Employee("Susan Collins", "[email protected]", true));
  
      final TreeItem<Employee> root = new TreeItem<>(new Employee("Sales Department", "", false));
  
      public static void main(String[] args) {
          Application.launch(FxMain.class, args);
      }
  
      @Override
      public void start(Stage stage) {
          root.setExpanded(true);
          employees.stream().forEach((employee) -> {
              root.getChildren().add(new TreeItem<>(employee));
          });
          Scene scene = new Scene(new Group(), 400, 400);
          Group sceneRoot = (Group) scene.getRoot();
  
          TreeTableColumn<Employee, String> empColumn = new TreeTableColumn<>("Employee");
          empColumn.setPrefWidth(150);
          empColumn.setCellValueFactory((TreeTableColumn.CellDataFeatures<Employee, String> param) -> param.getValue()
                  .getValue()
                  .nameProperty());
  
          TreeTableColumn<Employee, String> emailColumn = new TreeTableColumn<>("Email");
          emailColumn.setPrefWidth(190);
          emailColumn.setCellValueFactory((TreeTableColumn.CellDataFeatures<Employee, String> param) -> param.getValue()
                  .getValue()
                  .emailProperty());
  
          TreeTableColumn<Employee, Boolean> superiorColumn = new TreeTableColumn<>("is Superior");
          superiorColumn.setPrefWidth(190);
          superiorColumn.setCellValueFactory((TreeTableColumn.CellDataFeatures<Employee, Boolean> param) -> {
              Employee employee = param.getValue().getValue();
              return employee.isSuperiorProperty();
          });
          superiorColumn.setCellFactory(col -> {
              // what to change here to get no checkbox for department entry??
              CheckBoxTreeTableCell<Employee, Boolean> checkBoxTreeTableCell = new CheckBoxTreeTableCell<>();
              // what to change here to deactivate checkbox for all superiors??
              checkBoxTreeTableCell.setEditable(false);
              return checkBoxTreeTableCell;
          });
  
          TreeTableView<Employee> treeTableView = new TreeTableView<>(root);
          treeTableView.setEditable(true);
          treeTableView.getColumns().setAll(empColumn, emailColumn, superiorColumn);
          sceneRoot.getChildren().add(treeTableView);
          stage.setScene(scene);
          stage.show();
      }
  
      public class Employee {
  
          private final SimpleStringProperty name;
          private final SimpleStringProperty email;
          private final BooleanProperty isSuperior;
  
          public Boolean getIsSuperior() {
              return isSuperior.get();
          }
  
          public void setIsSuperior(Boolean isSuperior) {
              this.isSuperior.set(isSuperior);
          }
  
          public SimpleStringProperty nameProperty() {
              return name;
          }
  
          public BooleanProperty isSuperiorProperty() {
              return isSuperior;
          }
  
          public SimpleStringProperty emailProperty() {
              return email;
          }
  
          private Employee(String name, String email, Boolean isSuperior) {
              this.name = new SimpleStringProperty(name);
              this.email = new SimpleStringProperty(email);
              this.isSuperior = new SimpleBooleanProperty(isSuperior);
          }
  
          public String getName() {
              return name.get();
          }
  
          public void setName(String fName) {
              name.set(fName);
          }
  
          public String getEmail() {
              return email.get();
          }
  
          public void setEmail(String fName) {
              email.set(fName);
          }
  
      }
  }
  

  Thank you

  DPT

  I want to implement a TreeTableView where the cells in a column can be changed according to the other properties of the displayed object.

  Bat I would control it via isCellEditable() method of TableModel.

  What is the recommended way to make thin in JavaFX?

  Did not work with this but a simple web search for EXACTLY what you ask about "javafx editable tree table cell" produced the Oracle for TreeTableVIew API doc.

  https://docs.Oracle.com/javase/8/JavaFX/API/JavaFX/scene/control/TreeTableView.html

  Have you reviewed this API? He seems to have the info you need.

  Edition

  This control supports the online edition of values, and this section attempts to provide an overview of the available API and how you should use them.

  First of all, the cells most often requires a different user interface than when a cell is not being edited. It is the responsibility of the Cell implementation used. For TreeTableView, it is strongly recommended that edition is per-TreeTableColumn , rather than per row , as more often than otherwise you want users to change the value of each column differently, and this approach allows for specific to each column publishers. It's your choice, if the cell is constantly in a State of change (for example, this is common for CheckBox of the cells), or to switch to a different user interface when editing begins (for example when a double click is received on a cell).

  To find out what changes were requested on a cell, simply substitute the Cell.startEdit() method and update the cell text and graphic properties as appropriate (for example to set the null text and set the graphics to be a TextField ).

  In addition, you must also override Cell.cancelEdit() to reset the user interface to its visual state of origin when the installation ends. In both cases, it is important that also ensure you that you call the method super for that cell to perform all the duties he has to do for his edit mode or its output.

  Once your phone is in a State of change, the next thing you are probably interested is how to validate or cancel the current editing. It is your responsibility as a cell factory supplier. Your implementation of cell will know when the editing is complete, based on user input (for example when the user presses ESC or enter keys on their keyboard). When this happens, it is your responsibility to call Cell.commitEdit(Object) or Cell.cancelEdit() , as the case may be.

  When you call Cell.commitEdit(Object) an event is fired to the TreeTableView, you can observe by adding a EventHandler via TreeTableColumn.setOnEditCommit(javafx.event.EventHandler) . Similarly, one can also observe edit events for edit start and edit cancel .

  By default, the validation Manager TreeTableColumn edit is not null with a default manager who is trying to replace the property value for the item in the currently-being-edited line. It is able to do this as the Cell.commitEdit(Object) method is passed to the new value, and this should be transferred to the validation Manager change via the CellEditEvent , which is triggered. It is simply a matter of calling TreeTableColumn.CellEditEvent.getNewValue() to retrieve this value.

  It is very important to note that if you call TreeTableColumn.setOnEditCommit(javafx.event.EventHandler) with your own EventHandler , then you will remove the default handler. Unless you then manage writeback in the property (or the relevant data source), nothing will happen. You can work around this by using the TableColumnBase.addEventHandler(javafx.event.EventType, javafx.event.EventHandler) method to add a TreeTableColumn.EDIT_COMMIT_EVENT EventType with desired EventHandler as the second argument. Using this method, you will not replace the default implementation, but you will be notified when a validation of the change has occurred.

  I hope this summary answers some of the most frequently asked questions. Fortunately, JavaFX comes with a number of pre-built cell plants that handle all the requirements of editing on your behalf. You can find these cell factories pre-built in the javafx.scene.control.cell package.

• Public access to the JavaFX Jira?

  Hello world

  Surely I'm missing something obvious but... Does anyone know how to get the JavaFX Jira? : https://javafx-jira.kenai.com

  I need to create an account? Where?

  Thank you

  Marc

  Hey mark,.

  Missing probably not something obvious.  My guess is that they stopped allowing automatic registration for the current tracker. The independent instance of JIRA you accessed is deleted and JavaFX bugs are migrated to JBS.  The target date for the migration to complete is June 5.  After that bugs can anonymously view-through JBS:

  https://bugs.OpenJDK.Java.NET/secure/dashboard.jspa

  There are 2 ways to submit bugs in the JBS system.

  (1) If you have an author JBS status, you will have an account JBS and can submit bugs directly.

  (2) any person may submit bugs via the Bug database.

  I just checked and it seems that there already is an option to choose JavaFX when using bugs.java.com.  If you submit a bug, you might try it.  I have not used yet, so if you submit a bug, I'd be interested to hear how it works.  Ex: What kind of confirmation you get, how there are mapped in JBS, do you get notifications by e-mail updates, etc. ?

  If you are looking for a specific bug, I don't see a way to view them at the present time.  All existing bugs will be added to the JBS, and after migration, should be accessible via the bug current IDs.  There's more info here:

  JavaFX JIRA to JBS questions June 5

• Make JavaFX alerts look like ControlsFX dialogue

  Hello

  is there a way to make the official dialogue boxes (alerts) 8u40 looks like ControlsFX dialog boxes?

  I am talking mainly about the black title bar and slightly "generic" gray (who appear to be white in alert javafx?) as seen here:

  http://controlsfx.BitBucket.org/org/controlsfx/dialog/dialogs.html

  Thank you

  ControlsFX dialog boxes are deprecated,

  See the following blog announcement:

  Announces ControlsFX 8.20.7 / / JavaFX News, demos and Insight / / FX experience

  Use rather openjfx-dialog boxes:

  https://BitBucket.org/controlsfx/openjfx-dialogs

  This project is the controlsfx dialog box (probably the style you want), the features implemented on top of the new API of the Java 8u40 dialog box.

  Dialogs in the basic platform do not natively have the ability to return at your leisure without improvements that (I assume) are in openjfx-dialogues.

  ----

  I looked inside and I assumed wrong, openjfx-dialogue just seems to be a copy of the Java8u40 API dialog box so it has all the features of the obsolete ControlsFX dialog boxes.

  I guess your best bet to get the dialog boxes works the way you want is to use the deprecated ControlsFX API dialog box.

  Directly contact the developers of ControlsFX if you have any other questions.

  https://groups.Google.com/Forum/?hl=en#! controlsfx/forum-dev

  I see the currently last post is titled 'The plan for the dialogues'... it reads:

  (4) the existing dialogs API in ControlsFX will be deprecated but not

  deleted. This API will be removed when we planned on JavaFX 8u40. If

  you use the ControlsFX dialog boxes, please take the time to transition away from

  the old API as soon as possible. If there are things that you could do once

  Now you can't, please file bugs, but please note that we will not

  bring all the features (for example I'm sorry to say that I won't be

  bring back the light dialog boxes unless someone puts a big bag of

  money).

• JavaFX 8 node dynamic scaling

  I'm trying to implement a scene with a ScrollPane in which the user can drag around a knot and resize it dynamically. I'm moving and scaling with the mouse wheel work as well as a zoom reset.

  Here's my question:

  I have a problem with the calculations to suit the width of the parent node.

  If I Zoom in or out, the width adjustment does not work.

  If I change the size of the window after execution of fitWidth() once, the width adjustment does not the second time.

  Here is my code as a NBS and how it works...

  1 (works) mouse wheel will zoom in and out around the mouse pointer

  2 (works) or press left mouse to drag the rectangle autour

  3 (work) left, double-click to reset the zoom

  4. (does not) double-clicked right to fit the width

  My calculations to reposition the rectangle at the top left of the pane and mount it (i.e., resize it upwards or downwards) to the width of the parent are incorrect.

  import javafx.animation.KeyFrame;
  import javafx.animation.KeyValue;
  import javafx.animation.Timeline;
  import javafx.application.Application;
  import javafx.beans.property.DoubleProperty;
  import javafx.beans.property.SimpleDoubleProperty;
  import javafx.event.EventHandler;
  import javafx.scene.Group;
  import javafx.scene.Scene;
  import javafx.scene.control.ScrollPane;
  import javafx.scene.control.ScrollPane.ScrollBarPolicy;
  import javafx.scene.input.MouseButton;
  import javafx.scene.input.MouseEvent;
  import javafx.scene.input.ScrollEvent;
  import javafx.scene.layout.AnchorPane;
  import javafx.scene.layout.Pane;
  import javafx.scene.paint.Color;
  import javafx.scene.shape.Rectangle;
  import javafx.scene.shape.StrokeType;
  import javafx.stage.Stage;
  import javafx.util.Duration;
  
  public class ZoomAndPanExample extends Application {
  
     private ScrollPane scrollPane = new ScrollPane();
  
     private final DoubleProperty zoomProperty = new SimpleDoubleProperty(1.0d);
     private final DoubleProperty deltaY = new SimpleDoubleProperty(0.0d);
  
     private final Group group = new Group();
  
     public static void main(String[] args) {
     Application.launch(args);
     }
  
     @Override
     public void start(Stage primaryStage) {
  
    scrollPane.setPannable(true);
    scrollPane.setHbarPolicy(ScrollBarPolicy.NEVER);
    scrollPane.setVbarPolicy(ScrollBarPolicy.NEVER);
     AnchorPane.setTopAnchor(scrollPane, 10.0d);
     AnchorPane.setRightAnchor(scrollPane, 10.0d);
     AnchorPane.setBottomAnchor(scrollPane, 10.0d);
     AnchorPane.setLeftAnchor(scrollPane, 10.0d);
  
     AnchorPane root = new AnchorPane();
  
     Rectangle rect = new Rectangle(80, 60);
  
    rect.setStroke(Color.NAVY);
    rect.setFill(Color.NAVY);
    rect.setStrokeType(StrokeType.INSIDE);
  
    group.getChildren().add(rect);
     // create canvas
     PanAndZoomPane panAndZoomPane = new PanAndZoomPane();
    zoomProperty.bind(panAndZoomPane.myScale);
    deltaY.bind(panAndZoomPane.deltaY);
    panAndZoomPane.getChildren().add(group);
  
     SceneGestures sceneGestures = new SceneGestures(panAndZoomPane);
  
    scrollPane.setContent(panAndZoomPane);
    panAndZoomPane.toBack();
    scrollPane.addEventFilter( MouseEvent.MOUSE_CLICKED, sceneGestures.getOnMouseClickedEventHandler());
    scrollPane.addEventFilter( MouseEvent.MOUSE_PRESSED, sceneGestures.getOnMousePressedEventHandler());
    scrollPane.addEventFilter( MouseEvent.MOUSE_DRAGGED, sceneGestures.getOnMouseDraggedEventHandler());
    scrollPane.addEventFilter( ScrollEvent.ANY, sceneGestures.getOnScrollEventHandler());
  
    root.getChildren().add(scrollPane);
     Scene scene = new Scene(root, 600, 400);
    primaryStage.setScene(scene);
    primaryStage.show();
     }
  
     class PanAndZoomPane extends Pane {
  
     public static final double DEFAULT_DELTA = 1.3d;
     DoubleProperty myScale = new SimpleDoubleProperty(1.0);
     public DoubleProperty deltaY = new SimpleDoubleProperty(0.0);
     private Timeline timeline;
  
  
     public PanAndZoomPane() {
  
     this.timeline = new Timeline(60);
  
     // add scale transform
    scaleXProperty().bind(myScale);
    scaleYProperty().bind(myScale);
     }
  
  
     public double getScale() {
     return myScale.get();
     }
  
     public void setScale( double scale) {
    myScale.set(scale);
     }
  
     public void setPivot( double x, double y, double scale) {
     // note: pivot value must be untransformed, i. e. without scaling
     // timeline that scales and moves the node
    timeline.getKeyFrames().clear();
    timeline.getKeyFrames().addAll(
     new KeyFrame(Duration.millis(200), new KeyValue(translateXProperty(), getTranslateX() - x)),
     new KeyFrame(Duration.millis(200), new KeyValue(translateYProperty(), getTranslateY() - y)),
     new KeyFrame(Duration.millis(200), new KeyValue(myScale, scale))
     );
    timeline.play();
  
     }
  
     /** 
    * !!!! The problem is in this method !!!!
    * 
    * The calculations are incorrect, and result in unpredictable behavior
    *  
    */
     public void fitWidth () {
     double scale = getParent().getLayoutBounds().getMaxX()/getLayoutBounds().getMaxX();
     double oldScale = getScale();
  
     double f = (scale / oldScale)-1;
  
     double dx = getTranslateX() - getBoundsInParent().getMinX() - getBoundsInParent().getWidth()/2;
     double dy = getTranslateY() - getBoundsInParent().getMinY() - getBoundsInParent().getHeight()/2;
  
     double newX = f*dx + getBoundsInParent().getMinX();
     double newY = f*dy + getBoundsInParent().getMinY();
  
    setPivot(newX, newY, scale);
  
     }
  
     public void resetZoom () {
     double scale = 1.0d;
  
     double x = getTranslateX();
     double y = getTranslateY();
  
    setPivot(x, y, scale);
     }
  
     public double getDeltaY() {
     return deltaY.get();
     }
     public void setDeltaY( double dY) {
    deltaY.set(dY);
     }
     }
  
  
     /**
    * Mouse drag context used for scene and nodes.
    */
     class DragContext {
  
     double mouseAnchorX;
     double mouseAnchorY;
  
     double translateAnchorX;
     double translateAnchorY;
  
     }
  
     /**
    * Listeners for making the scene's canvas draggable and zoomable
    */
     public class SceneGestures {
  
     private DragContext sceneDragContext = new DragContext();
  
     PanAndZoomPane panAndZoomPane;
  
     public SceneGestures( PanAndZoomPane canvas) {
     this.panAndZoomPane = canvas;
     }
  
     public EventHandler<MouseEvent> getOnMouseClickedEventHandler() {
     return onMouseClickedEventHandler;
     }
  
     public EventHandler<MouseEvent> getOnMousePressedEventHandler() {
     return onMousePressedEventHandler;
     }
  
     public EventHandler<MouseEvent> getOnMouseDraggedEventHandler() {
     return onMouseDraggedEventHandler;
     }
  
     public EventHandler<ScrollEvent> getOnScrollEventHandler() {
     return onScrollEventHandler;
     }
  
     private EventHandler<MouseEvent> onMousePressedEventHandler = new EventHandler<MouseEvent>() {
  
     public void handle(MouseEvent event) {
  
    sceneDragContext.mouseAnchorX = event.getX();
    sceneDragContext.mouseAnchorY = event.getY();
  
    sceneDragContext.translateAnchorX = panAndZoomPane.getTranslateX();
    sceneDragContext.translateAnchorY = panAndZoomPane.getTranslateY();
  
     }
  
     };
  
     private EventHandler<MouseEvent> onMouseDraggedEventHandler = new EventHandler<MouseEvent>() {
     public void handle(MouseEvent event) {
  
    panAndZoomPane.setTranslateX(sceneDragContext.translateAnchorX + event.getX() - sceneDragContext.mouseAnchorX);
    panAndZoomPane.setTranslateY(sceneDragContext.translateAnchorY + event.getY() - sceneDragContext.mouseAnchorY);
  
    event.consume();
     }
     };
  
     /**
    * Mouse wheel handler: zoom to pivot point
    */
     private EventHandler<ScrollEvent> onScrollEventHandler = new EventHandler<ScrollEvent>() {
  
     @Override
     public void handle(ScrollEvent event) {
  
     double delta = PanAndZoomPane.DEFAULT_DELTA;
  
     double scale = panAndZoomPane.getScale(); // currently we only use Y, same value is used for X
     double oldScale = scale;
  
    panAndZoomPane.setDeltaY(event.getDeltaY()); 
     if (panAndZoomPane.deltaY.get() < 0) {
    scale /= delta;
     } else {
    scale *= delta;
     }
  
     double f = (scale / oldScale)-1;
  
     double dx = (event.getX() - (panAndZoomPane.getBoundsInParent().getWidth()/2 + panAndZoomPane.getBoundsInParent().getMinX()));
     double dy = (event.getY() - (panAndZoomPane.getBoundsInParent().getHeight()/2 + panAndZoomPane.getBoundsInParent().getMinY()));
  
    panAndZoomPane.setPivot(f*dx, f*dy, scale);
  
    event.consume();
  
     }
     };
  
     /**
    * Mouse click handler
    */
     private EventHandler<MouseEvent> onMouseClickedEventHandler = new EventHandler<MouseEvent>() {
  
     @Override
     public void handle(MouseEvent event) {
     if (event.getButton().equals(MouseButton.PRIMARY)) {
     if (event.getClickCount() == 2) {
    panAndZoomPane.resetZoom();
     }
     }
     if (event.getButton().equals(MouseButton.SECONDARY)) {
     if (event.getClickCount() == 2) {
    panAndZoomPane.fitWidth();
     }
     }
     }
     };
     }
  }
  

  I found the answer. I was looking at the wrong calculations, assuming that it be linked to translation. The real culprit was the calculation of the difference in scale. I just changed this:

  double f = (scale / oldScale)-1;
  

  to do this:

  double f = scale - oldScale;
  

  in the fitWidth() method, thus producing this...

      public void fitWidth () {
          double scale = getParent().getLayoutBounds().getMaxX()/getLayoutBounds().getMaxX();
          double oldScale = getScale();
  
          double f = scale - oldScale;
  
          double dx = getTranslateX() - getBoundsInParent().getMinX() - getBoundsInParent().getWidth()/2;
          double dy = getTranslateY() - getBoundsInParent().getMinY() - getBoundsInParent().getHeight()/2;
  
          double newX = f*dx + getBoundsInParent().getMinX();
          double newY = f*dy + getBoundsInParent().getMinY();
  
          setPivot(newX, newY, scale);
  
      }
  

• Two quick questions (hopefully) - right way to dynamically change the CSS class and put of Splash screen implemented

  Couple of quick questions have left me speechless!

  So, it seems obvious that many JavaFX applications want to dynamically change the CSS styles.  Is the best way to do it through la.getStyleClass () .add ("classname") < node >?  The underlying data structure is a list of observable.  So let's say we have 5 styles that simply to change the fill color of a circle of 5 different colors, respectively.  So if I have a condition in which I want to dynamically apply 1 of these 5 styles, as I do now it's by setting all 5 styles as a string in a list by using a static initializer, then I call < node > .getStyleClass () .removeAll (list), then getStyleClass () .add ("classname").  I do this to avoid adding again and still the same style and inflate the underlying list.  What is the right way to manage dynamic CSS styles?

  Finally a very simple I think.  So I know there's a little differently to implement a splash screen.  My app has certainly got bigger in the last few months of development and I noticed there are about a 5 second delay between when I run the application when I see the main stage.  I was thinking what a splash screen would be nice to fill that time.  I had no time to prototype using a Preloader and I fear that using another, early stage start-up again would be too long of a delay.  "I actually thought that using the Nice and simple JVM argument" - splash: image name > "would be simple, easy and effective.  Unfortunately when I try to do, the splash screen appears but never goes away.  Anyone know what is happening with this?

  Your mechanism to manage the css style classes is a good approach; I've used several times. I wonder why the style classes have been implemented as a list, instead of a game, but there may be cases of good use for the use of a list.

  In some cases you can also consider using CSS PsuedoClasses, which were presented in JavaFX 8. Here is a little easier to use, especially if you have two options. But a use case might look like:

  public class Message {
      public enum Status { NORMAL, WARNING, CRITICAL }
  
      private final ObjectProperty status = new SimpleObjectProperty<>(Status.NORMAL);
      private final StringProperty message = new SimpleStringProperty();
  
      // constructor, getters, setters, and property accessors....
  }
  

  public Label createLabel(Message message) {
      PseudoClass warning = PseudoClass.getPseudoClass("warning");
      PseudoClass critical = PseudoClass.getPseudoClass("critical");
  
      Label label = new Label();
      label.textProperty().bind(message.messageProperty());
      message.statusProperty().addListener((obs, oldStatus, newStatus) -> {
          label.pseudoClassStateChanged(warning, newStatus == Message.Status.WARNING);
          label.pseudoClassStateChanged(critical, newStatus == Message.Status.CRITICAL);
      }
      return label ;
  }
  

  And then your css looks like

  .label:warning {
      -fx-text-fill: orange ;
  }
  .label:critical {
      -fx-text-fill: red ;
  }
  

• Creating a JavaFX 8 front-end application using command line tools.

  I'm sure this has been asked and answered, but the deluge of search results I get from Google and Bing do things much more confused than they already are.

  I'm finally taking the plunge and spend C/C++ and Python for the Java SE and JavaFX 8 platform.  I am the creation of user interface running on top of the back-end tools that can run from seconds to days and output GB of data generated (imagine the tar running on Google's servers).

  I understand how to run my tools saved using a running process and how to interact with them and operate a simple text like a command-line Java app as planned work.  This problem occurs when I wrap the code in a late snow JavaFX UI try to update the UI in a reasonable manner.  If I just use System.out.println () as in the command line version, I see the output of my task.  However, simply trying to put this same output in a text box using the. appendText() is not updated once the component TextArea until the background process completes.

  I see all kinds of press clippings related to the task, CreateProcess, invokeLater updateProgress, but none of them does not seem to resolve the issue of their original posters (or mine at this stage).

  Has anyone created a simple tutorial that is bound to this type of operation?  Pointers?  Better search terms?

  Thank you

  Tim

  For posterity:

  I found the answer to this - the class ProcessBuilder does everything need AND Lambdas make even easier!

  This discussion on StackOverflow have me in the right direction:

  http://StackOverflow.com/questions/12361600/JavaFX-fxml-communication-between-application-and-controller-classes

• How to correctly customize the text label of a JavaFX ComboBox

  Hello

  from Swing to 8 JFX, I'll try to find out how to do something I would normally do in a single super ListCellRenderer, i.e. to customize the string that is displayed for an item. I tried this:

  ComboBox<Integer> combo = new ComboBox<>();
      combo.getItems().addAll(1, 2, 3);
      combo.setCellFactory(new Callback<ListView<Integer>, ListCell<Integer>>() {
          @Override
          public ListCell<Integer> call(ListView<Integer> param) {
              return new ListCell<Integer>(){
                  @Override
                  protected void updateItem(Integer item, boolean empty) {
                      if(item != null)
                          setText("#" + item);
                  }
              };
          }
      });
  

  However, when I do this, the custom string is not used for the selected item (rather the toString() standard value of the element). Apart from that, it is more selectable with the mouse (I submitted a bug report for this to https://javafx-jira.kenai.com/browse/RT-37445), but this isn't really the point of my question.

  What Miss me? Is not the way to do it? The thing I have to do to make sure that the selected item is also rendered using the custom cell or is there a different mechanism for that?

  Thank you

  Robert

  There is no bug here (in the API, there are some bugs in your code). The question of the selection is because you call implementation of the superclass of the updateItem (...). The display of the selected item is controlled by the button cell, not the cell factory. If you have the permissions to do so, it might be useful to retract or close the jira.

• OffTopic question: The Forum stage Builder?

  Hi all friends, JavaFX forum is the right forum to ask questions on stage Builder?

  Thank you

  
  

  Yes, it is, without a doubt!

• Why almost all javafx methods must be called from the thread of the application?

  I have a pretty big 3D scene that is refreshed every few seconds.

  It takes a while to update the scene, and I wanted to do it in a background thread.

  Problem is that almost every approach I take requires the application-fx thread.

  Now, I understand that change the UI itself must be called in the application thread, so I tried a different approach:

  Create a new group, add all the nodes (which takes the greatest amount of time) and update the component root of the view with the new group.

  I assumed that only the last party required the application thread, but alas this was not the case.

  group.getChildren () .add also requires that the thread of the application. Why?

  node.setLayoutX () also requires that the thread of the application. Why?

  It is a new set of nodes that are not visible and groups yet, so why can't do this in a background thread?

  The reasons of principle (I think) that JavaFX is mainly a single toolbox threaded are described in:

  https://weblogs.Java.net/blog/2004/10/19/multithreaded-toolkits-failed-dream

  That said, if you manipulate objects that are not part of an active scene, then it should work.  The dream that failed has what to do with the components who participate actively in the molten, interactive GUI.  If you're interacting with only the components out of the screen, then it (should be) without issue.

  Please, create and post an example minimum, executable that replicates the question.

  (Please ensure that the example is minimal and executable).

  In addition, what is the cause as your application "takes some time to update the scene?  Computers are today quite incredibly fast.  Of course, there are valid reasons for some things take time, I wonder what these are in your case.  What is the time?  If your executable example can include something reasonably representative of what you're done which shows something that will take "some time", would be great.

  What you have described so far, I feel that, even if there is no problems with threads, your proposed approach would not fix your performance problem.

• JavaFX should be installed for ports gpio raspi in java programming?

  I have a question. I watched the tutorials to youtube of vinicius senger

  and, he said, that JavaFX should be installed on my raspberry pi.

  But I don't understand why...  JavaFX is used for graphics is not it?

  So why am I need to install (and overclock my IP I want to do in fact...)

  When I want to just program my gpio in java ports?

  I understand why should I install pi4g and wiringpi, but what I really need to install JavaFX?

  Tanks to support fast and pleasant.

  Hello

  In fact we provide instructions on how to configure javafx, if you want to use. It comes with JDK1.8.0 anyway and you do not need to use GPIO.

  So, if you want to play with GPIO, go ahead and jump all the instructions of JavaFX.

  Vinicius-

• JDK 8 and JavaFX TabPane throwing NullPointerException

  Hi all. I hope this is the right forum for this. I want to preface this question by declaring that the following code works perfectly fine in JDK 1.7. The goal here is to create a component with a tab at the end tab (with the value text '+') so that whenever this tab is selected, the program creates a new tab in the tab pane. This feature works fine. The problem is that when you close the new tab via the X, it goes to the tab 'add,' creates a new tab, then survey the following NullPointerException in some code JDK (and the app shows now TWO new tabs that correspond to the exact same object):

  Execution using the C:\Program Files\Java\jdk1.8.0\jre/bin/java java.lang.NullPointerException at com.sun.javafx.scene.control.skin.TabPaneSkin platform $TabHeaderSkin.access$ 302 (TabPaneSkin.java:1040) of C:\Users\XXXXXX\Documents\NetBeansProjects\TestJavaFx\dist\run2082574567\TestJavaFx.jar...

  I cut down the trouble code bare minimum to view the issue, and it's as follows:

  (Incase it do not paste correctly, see here: [Java] package testjavafx; import javafx.application.Application; import javafx.bea - Pastebin.com)

  package testjavafx;
  
  
  import javafx.application.Application;
  import javafx.beans.value.ChangeListener;
  import javafx.beans.value.ObservableValue;
  import javafx.scene.Scene;
  import javafx.scene.control.Tab;
  import javafx.scene.control.TabPane;
  import javafx.scene.control.TabPane.TabClosingPolicy;
  import javafx.scene.layout.StackPane;
  import javafx.stage.Stage;
  
  
  public class TestJavaFx extends Application {
  
  
      private TabPane tabPane;
      private Tab addTab;
      private Tab currentTab;
  
  
      @Override
      public void start(Stage primaryStage) {
  
  
          //Create the tab pane and the 'addTab' for adding new tabs.
          tabPane = new TabPane();
          tabPane.setTabClosingPolicy(TabClosingPolicy.SELECTED_TAB);
  
  
          addTab = new Tab("+");
          addTab.setClosable(false);
          tabPane.getTabs().add(addTab);
  
  
          //Add a listener to listen for changes to tab selection.
          tabPane.getSelectionModel().selectedItemProperty().addListener(new ChangeListener<Tab>() {
              @Override
              public void changed(ObservableValue<? extends Tab> observable, Tab oldSelectedTab, Tab newSelectedTab) {
  
  
                  //If we change to the addTab create a 
                  //new tab and change selection.
                  if (newSelectedTab == addTab) {
                      //Create the new tab.
                      createNewTab();
                  } else {
                      currentTab = newSelectedTab;
                  }
              }
          });
          //Create a new tab for initial load of the app
          createNewTab();
  
  
          StackPane root = new StackPane();
          root.getChildren().add(tabPane);
  
  
          Scene scene = new Scene(root, 500, 500);
  
  
          primaryStage.setTitle("Tab Test");
          primaryStage.setScene(scene);
          primaryStage.show();
      }
  
  
      /**
       * @param args the command line arguments
       */
      public static void main(String[] args) {
          launch(args);
      }
  
  
      private Tab createNewTab() {
          Tab newTab = new Tab("New Tab");
          newTab.setClosable(true);
          tabPane.getTabs().add(tabPane.getTabs().size() - 1, newTab);
          tabPane.getSelectionModel().select(newTab);
          return newTab;
      }
  
  
  }
  

  Does anyone have ideas on this? Why it would break in 1.8? Is there a bug in the JDK?

  It's clearly a bug in the code of TabPaneSkin. What seems to be the case, it's that the tab is removed before the end of the deletion tab animation. The problem may be exacerbated by the code by automatically adding a tab if the last tab is deleted, but the code base should not fall like that.

  To work around the issue, disable the close animation of the tab with the following CSS bit.

  tabPane.setStyle ("- fx - close-tab-animation: none ;"); ")

  I created https://javafx-jira.kenai.com/browse/RT-36443 to follow up the matter.

• The JavaFX class hierarchy

  I have a question about the architecture of the JavaFX class. In fact, she should follow the pattern of composite named design looking for this http://en.wikipedia.org/wiki/Composite_pattern way somehow.

  However if I want to draw the composite model of the JavaFX package I find myself sort of this way:

  

  It seems that I can add children to buttons or labels. It was also possible with SWING. Why it has not been repaired? Is this a feature? On the other side window and the steps are now outside the model. In fact, they should be Parents I think. Why is it designed this way?

  Hope someone can enlighten me upward. Thank you very much for your answers in advance.

  > Actually it must follow the model of composite named design somehow.

  I think you are trying to simplify things.

  The JavaFX scene graph is a composite structure, but its design is subtler than a model composite vanilla.

  The basic concept of the presentation of JavaFX is a scene graph.  A scene contains a node tree, which forms the scene graph.  Any node that is not a leaf is a parent.  The parent base has a public method getChildrenUnmodifable and a protected getChildren method.  This means that you cannot add outwardly new nodes to a Parent unless you provide additional APIs.  The only thing that can add children to the mother is the Parent or the subclass of the Parent.  So, there's some cache information to go on.

  Some subclasses that act like editable containers expose their list of children to be publicly editable.  Usually, this is done by providing a public getChildren method.  A component, which is the root layout manager class, so in general, you can change the children of any pane layout is an example of such a class.  Conversely, if you have something that does not expose its getChildren method publicly, then external components cannot directly change the children of this thing.

  Region and the control are examples of nodes that extend from Parent and do not provide a public API getChildren.  As a button is a control, if you can not directly change her children through the public API.  The only way to change the control's children is to provide your own skin or to use additional modifier of APIs that control could provide.  For example, a button can have a chart, you can set the button and thus provide an arbitrary node or node tree to the button.  However, that is not quite the same Exhibitor getChildren button, because the graph is just a node, and layout in the button can be handled by the button through the display of the content of the button setting.

  OK, so JavaFX should not have had this complexity.  He could really go for a simpler approach where everything is a node, there are only a few types of nodes and HTML node types are not extensible example.  But he did not do this.  Instead, he went for a more detailed breakdown of the nodes of types, with each type supported by an object model providing State and functionality.  It's just a different approach.

  > It seems that I can add children to buttons or labels.

  Have you tried to do this by calling getChildren on one of them to get the list of children so you can change?  I bet that you could not do.

  > Window and steps are now outside the model.

  Yes, they are not part of the scene.

  All this is just a metaphor for the theatre.  Imagine that you go to the theater to watch Romeo and Juliet.  You sit in your Chair and watch the scene, the curtain has just unveiled the first scene.  The scene contains a background (a square of city to Verona in Italy), some accessories (swords and a fountain) and actors (nobles) who move and speak and go away.  These things in the scene are the nodes of the scene.  The curtain goes down and another scene appears, then again and another scene.  Finally, you arrive at the scene of the balcony where Romeo climbs the wall to join Juliette.  Whenever the curtain goes down, a new scene is assembled, and when the curtain rises the new scene appears.  All the time, the scene never changes.  This isn't a part of the scene.  The scene is the scaffolding in which many different scenes will appear.