Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Window border size not preserved when nodes are changed #1

Open
andytill opened this issue Mar 3, 2013 · 3 comments
Open

Window border size not preserved when nodes are changed #1

andytill opened this issue Mar 3, 2013 · 3 comments

Comments

@andytill
Copy link

andytill commented Mar 3, 2013

Excellent project, many thanks! I am trying to use it in my own project, EstiMate but have run into an issue.

I have my own container FXML called rootView.fxml, I put a login control in rootView and set that as the Undecorated control. When the user logs in I put a main screen in the root view, this replaces the login screen. The undecorator no longer has the correct border size.

Do you know of any issues when switching around nodes inside the Undecorator control? Below is a screen shot.

Thanks!

EstiMateWin8

@andytill
Copy link
Author

andytill commented Mar 3, 2013

You can recreate this issue using the following program.

import insidefx.undecorator.UndecoratorScene;
import javafx.application.Application;
import javafx.scene.control.Button;
import javafx.stage.Stage;

public class UndecoratorApp extends Application {

    @Override
    public void start(final Stage stage) throws Exception {

        // The Undecorator as a Scene
        UndecoratorScene undecoratorScene = new UndecoratorScene(stage, new Button("Hello"));

        // Set minimum size
        stage.setMinWidth(500);
        stage.setMinHeight(600);

         stage.setScene(undecoratorScene);

         stage.show();
     }

     public static void main(String[] args) {
         launch(args);
    }
}

@in-sideFX
Copy link
Owner

Hi,
Indeed, this could lead to a problem... The client area is part of bounds calculation so if it is changed it may produce unexpected results.
Do you have to the same issue if you use an intermediate Pane where you load both the login and the second screen into this one?
Thanks.

@andytill
Copy link
Author

andytill commented Apr 8, 2014

Hi!
It did use an intermediate pane. I think this is basically the same issue as #3 where the min size of the content area is not used, you can use the sample program to recreate.
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants