Menubar doesn't automatically resize, using scene builder

Hi,
I started playing around with the new scene builder. I love it!
In the past I added the menubar into the top area of a border pane. If I resized the window to full screen, the menubar also automatically resized to full screen.
It seems to me that scene builder doesn't support a border pane (scene builder use anchor pane).
This is how it looks like if I resize the window:
|__Menu__!
|
|_______________
And it should look like this:
|__Menu_________!
|
|_______________

@Josef
BorderPane support will be added in an upcoming Developer Preview build.
In the mean-time, you can anchor the MenuBar:
Select the MenuBar, go the Layout part of the Inspector and click on the Left and Right Anchors in the AnchorPane Constraints to activate them.

Similar Messages

Modularizing large FX gui apps, esp. using fxml developed by Scene Builder

StarterApp - One large java source file.
Trying Out the JavaFX UI Controls (Using the JavaFX UI Controls)
StageCoach is a simpler app, but with fxml, controller, and main code in separate files.
Allows manipulation using Scene Builder.
https://code.google.com/p/jfxtras/source/browse/ProJavaFX/Chapter03/StageCoach?repo=samples&r=322042d9ac293fcd9dd8f63e1664df45a0c4746f
I was lead to these by the book, Pro JavaFX 8:
http://www.apress.com/9781430265740
Rich as it is, the StartApp is one big piece of code, with no modules such as an fxml file.
By spreading out the code for StarterApp and StageCoach and studying it carefully
I should be able to build a system as large as StarterApp, but as a three-file combo.
StarterApp has nothing that deals with concurrency or persistence - those will be my jobs.
I'm doing this because I'm building a large NLP app.
It needs a GUI for future users.
- Bob F

Take a look at some app examples from the open-jfx repository
https://wiki.openjdk.java.net/display/OpenJFX/Quick+Start
For a smallish app, see the ConferenceScheduleApp:
   openjfx/8u-dev/rt: 3d138300d935 /apps/experiments/ConferenceScheduleApp/
For a (much) larger app, see SceneBuilder:
   http://hg.openjdk.java.net/openjfx/8u-dev/rt/file/3d138300d935/apps/scenebuilder
   Ladstatt: Home made JavaFX SceneBuilder
For a minimal framework which features FXML and dependency injection, see afterburner.fx:
   http://afterburner.adam-bien.com
You can skip all of the stuff below if you don't like reading and just want to go code...
In general for app code, use aggregation over inheritance in most places, though inheritance is useful sometimes. Don't try to create your own controls by extending the Control class unless you are writing control libraries - that is complex and not well documented as well as largely unnecessary for app code. Similarly PopupWindow isn't all that great or at least I have never found a need for it in app code - a basic Stage works fine for pretty much every case except perhaps very specialized things like context menus. Java 8 has built-in dialogs and alerts in 8u40, so for standard dialogs or some reasonably customized dialogs, using those is better than creating your own. If the standard controls aren't enough, try ControlsFX, it is (mainly) great and high quality.
Let resizable layout managers do the layout work for you and use constraints in the layout managers and nodes rather than mucking around with fixed sized layouts or layout through binding.
Don't try to implement a spreadsheet in a JavaFX TableView - just use the built-in controls for what they are good at and either develop a new control for specific functionality not provided by the built-in controls or just skip that feature if it would be too expensive to build it from scratch yourself (and it probably will be expensive - you just have to justify that against your project budget whether that is money or your own time).
Make use of WebView to bring in web components (e.g. Google Docs or Google Maps). Don't try and pass a lot of data back and forth between a WebView and your app.
Don't do any style in code nor in FXML, put it all in a CSS style sheet.
For medium sized apps - use FXML to design and mark-up your GUI, and use SceneBuilder to create and edit the FXML, don't hand code basic form style UIs - in the long run the FXML based app will be easier to maintain.
For really small apps and learning tasks, write everything in code against the API so you understand that - use no FXML at all.
With JavaFX you are writing user interfaces, follow basic user interface design heuristics for which there are some principles to keep in mind.
Once you have a few FXML pages, passing parameters or sharing data between them is a question that most people run into as well as how to deal with navigation. That navigation framework I linked is super basic and just meant for pretty simple applications. A nicer framework which worked in general like a Browser navigation model would be useful - but I haven't seen a generic implementation of such a thing yet - I guess you could create one, but I definitely wouldn't start out trying to do that - instead focus on the basics of your application and get that implemented first. If you end up needing a reasonably sophisticated navigation framework, eventually you will know it and can evaluate what to do then.
You can do an awful lot with CSS and styling the built-in controls. It really is very flexible. Learn CSS and the JavaFX variant by reading general CSS tutorials (then forget everything HTML specific) and study in depth the JavaFX CSS reference guide and understand its extensions like looked up colors and derivation functions. When you want to know how some inbuilt thing is styled, go to the modena.css source (which can be hideously obtuse and complicated). Use ScenicView and SceneBuilder CSS analyzer to understand how CSS is applied to elements. Don't style borders with boxes - use layered backgrounds, that is how every control modena.css works and how your app should also work.
Deployment is a difficult topic - so sad and depressing. For development, just build and run in your IDE. For production, package the app as a self-contained application. Maybe one day there will be a better deployment model for JavaFX - but that is the best you can get for now. Completely ignore webstart and web deployment models - any time spent investigating such technologies is completely wasted.
Do not try to integrate JavaFX and Swing or SWT. Just write pure JavaFX apps.
For larger apps you intend to deploy to production, use Maven or Gradle as your build system (you can google the JavaFX plugins for each). Do not spend any time with the stand-alone JavaFX packager or the JavaFX ant tasks and do not rely on your IDE to do your production builds.
Get help to targeted questions on StackOverflow.
Only code to Java 8+ and make use of functional programming techniques.
Don't write multi-threaded apps unless you know what you are doing. When you do write multi-threaded apps, use the JavaFX concurrency utilities. Never modify the active scene graph from another thread, nor touch a property which might trigger an event which might modify the scene graph. Do use the concurrency utilities if you have network I/O otherwise you will freeze your app while the network I/O occurs and that is a "bad thing".
The Oracle JavaFX 8 documentation is good - read it and run a lot of the examples (except the ant based deployment ones and the Swing/SWT integration ones).
Ensemble is great, play with it and study the code to see for the samples (which you can view within Ensemble).
Binding is programming by side-effect, so be aware that when you change a property, it may trigger some potentially unrelated action through bindings or attached listeners.
Programming JavaFX in any language other than Java is an experimental thing, so only do that if you like experimenting and are prepared to do so without a lot of support.
Targeting embedded devices, iOS or Android for a JavaFX app is an experimental thing, so only do that if, yada, yada, yada.
JavaFX is a mid-level UI system, not a full application stack - it abstracts away the basics like rendering, controls and animation but does not provide comprehensive OS hooks, navigation frameworks, model/view/presenter frameworks, full dependency injection, client/server messaging, data <-> controls serialization and deserialization, etc. FXML is just a markup system with a binding capability to Java code. JavaFX and FXML do not constitute a full application framework. There is no widely-used full application framework for JavaFX. Sure some people have tried to create one, but none of those solutions have achieved critical mass of usage and features - plus a one-size fits all application framework will never exist anyway - client applications (e.g. a game versus a line-of-business app) differ greatly and deserve completely different architectures.
There are many things in the Java EE world which can be used in JavaFX (e.g., its dependency injection, its web socket or rest APIs and implementations, its server based systems to allow your app to access cloud based logic and storage, etc) - so feel free to use the bits you need, usually it's as simple as adding additional library dependencies to your maven or gradle project. A typical medium sized JavaFX application will include multiple third party libraries (mostly non-UI libraries) to get its job done as this will be more convenient than coding everything against the JRE API - though there is an awful lot of out the box functionality you get from the JRE.
JavaFX is more complicated to use than Delphi and in some respects doesn't supply as much functionality in terms of built-in stuff like data base backed tables (though it supplies a ton more functionality in style). It is not easier to create a complete business app using JavaFX than it would be to create a similar thing in Microsoft Access in the 90's. Such is progress.
JavaFX is portable across desktop environments (OS X, Windows, Mac). JavaFX apps have their own look and feel which is not like the native OS, but that is probably fine for a lot of apps. AquaFX does an amazing job of making a JavaFX app looks like OS X apps (kudos to the creators of both AquaFX and the JavaFX built-in styling capabilities).
Unlike some other portable frameworks like QT, you don't have to write C code, you can write Java code (which to me at least is a win). Similarly unlike HTML/CSS/JavaScript you don't have to write untyped JavaScript or make use of some obscure code snippet you pulled off the web for your button control. You don't have to use the web framework of the day which withered yesterday. Instead you have the (benefit?) of hardly any framework at all for JavaFX. You don't have to have your app live within a browser sandbox that another developer once described as the ghetto of application sandboxes.
So, as compared to HTML - I think JavaFX is kinder to the developer, though end users don't really seem to care that much and are fairly accepting of HTML applications even when their functionality is often inferior to many more traditional GUI apps. HTML is standardized, its full of standards, even the non-standard parts. Everybody used to implement all the standards differently or make their own standards, however now the standards are so painstakingly, nitpickingly prescriptive that everybody implements pretty much the same thing - except when they don't. JavaFX has no standard but its public API docs, it has just one implementation. If you code against the API, your app is probably going to work forever - at least if you bundle the runtime with your app, cause if you don't you might end up like the poor guy in the previous question who can't figure out how to update his app specific CSS rules to get his app to look the same with a newer Java version. JavaFX is a relatively niche technology and you don't have the legion of developers, tinkerers, industry investments and people just plain getting stuff done in any which way that you have with the whole HTML juggernaut. The major thing that HTML provides that JavaFX does not is: Sharable, browsable deep links to stuff with search indexed content. With HTML, Google will index it and you can link to and refer to other docs and other docs can link to yours. It is the HT in HTML which makes the web so amazing and the F in FXML doesn't match it. What is the F anyway?
That's a huge wall'o'text. Just some random thoughts and opinions. All opinions are my own. Your opinions may vary. That's OK. I don't think a discussion is needed. If you would like any clarification or further advice you can ask in new questions.

How do i add/use FileChooser on or with scene builder

Hello... i am still new to javafx nd my english is not very, please bare with me... i was trying to implement a simple application that manages personal contacts. i started using scene builder to help with user interface.. i was planning on adding File Chooser for profile picture uploads but i just cant find it anywhere on scene builder
How can be able to use the fileChooser?

Scene Builder is just a layout creation tool, it doesn't write any code for you.
To use a FileChooser you need to write code.
This is because a file chooser is associated with the dynamic behaviour of a program, not the program's layout.
There is sample code in the Oracle file chooser tutorial:
http://docs.oracle.com/javafx/2/ui_controls/file-chooser.htm
1. In Scene Builder create a button with text "Open File".
2. Select your button.
3. In the code pane provide a name for the onAction event handler.
4. Have Scene Builder generate a code skeleton and save it to a file.
5. Open the code skeleton and place the following code in the generated on action method stub;
FileChooser fileChooser = new FileChooser();
fileChooser.setTitle("Open File");
File file = fileChooser.showOpenDialog(null); // you could pass a stage reference here if you wanted.
if (file != null) // do something interesting with the file.
6. Compile and run your application.
7. Click on your Open File button.
8. A FileChooser will open.
9. Choose a File.
10. Your program will do something interesting with the file.

How to use JavaFX Scene Builder 1.1 build b29 in Eclipse

I would like to use Scene Builder to generate FXML with corresponding handlers and then use other technologies to implement the handlers. I have looked at jfxeclipse and it was not suitable. The Scene Builder team has done a great job with the easy layout and the terse xml. Any information would be appreciated. The support in Netbeans is very good but I can't use that IDE at this time.

By jfxeclipse, do you mean e(fx)clipse? You can create a new FXML file directly in there (File -> New -> Other... -> JavaFX -> New FXML document). You can right click on that file and choose "Open with Scene Builder". It will open it in Scene Builder (whatever version you have installed), let you edit it there, and then update it in Eclipse when you save. Not quite using Scene Builder as a plugin, but just as convenient.

Resizing the scene

Hi guys!
I''ve been working in this screen: http://i.imgur.com/57Teo4y.png
There's the menu in the left side, the highlighted button that opens another area that we'll call "central area" and the empty space that will be the container for the selected menu item. In this case, it's the "Historico da aula", that can be translated to english like "Class History" (just FYI )
Well, when I press the highlighted button to open the "central area", this happens: http://i.imgur.com/Ia2z2mL.png
The container extrapolates the scene and instead of resizing, it moves to left.
I use Scene Builder (FXML) and NetBeans.
I don't know what kind of specific informations I can give to you, but feel free to ask and I'll respond.
If anyone has an idea why this happens, it will make my day.
Thanks!

Guys, I've found the solution.
You can't use AnchorPanes in this case. Just use HBox and / or VBox to mount you scene and they will (or is supposed to) work.

Scene builder and nodes position

Hi,
I've created form using scene builder, additionaly from java code I want to draw some shapes on this form and I need positions of nodes.
How can I check that? Also I need to be informed when user resizes the window to compute new positions of nodes.
Thanks for your help.
Lukasz

On the Scene or Stage you can add listeners to the height and width properties.
scene.heightProperty().addListener(windowResized);
scene.widthProperty().addListener(windowResized);
    private static ChangeListener windowResized = new ChangeListener() {
        @Override
        public void changed(ObservableValue arg0, Object arg1, Object arg2) {
            //code to handle window resizing
    };thanks
jose

Scene Builder Inspector

I am using Scene Builder and I would like to replicate the inspector look.
My questions:
1) Are Padding, size, position areas ...etc panels within a Scroll Pane or are just two separators with a label in between ? It looks like a Swing TitledBorder Jpanel.
2) In case of panels, what has been used and how to set a title ?
3) Is there a naming convention for fx:id field? I have only find some examples all written in lowercase such as "maintabbedpane".
Thanks

acepsut wrote:
I am using Scene Builder and I would like to replicate the inspector look.
My questions:
1) Are Padding, size, position areas ...etc panels within a Scroll Pane or are just two separators with a label in between ? It looks like a Swing TitledBorder Jpanel.It's a Label over an HBox which is squeezed by setting its maxHeight to a little value.
Something close to this:
<StackPane prefHeight="-1.0" xmlns:fx="http://javafx.com/fxml">
<children>
<HBox maxHeight="2.0" prefHeight="-1.0" prefWidth="-1.0" style="-fx-background-color: gray;-fx-background-insets: -1 -17 1 -17, 0 -17 1 -17;" />
<Label style="-fx-font-weight: bold;-fx-background-color: white;-fx-padding: 0 6 5 6;" text="Title" />
</children>
</StackPane>
>
2) In case of panels, what has been used and how to set a title ?Will try to find out.
>
3) Is there a naming convention for fx:id field? I have only find some examples all written in lowercase such as "maintabbedpane".I am not aware of any.
fx:id can be considered as java variable name.
So using camel case seems natural to me.
Eric

Diffrent coordinates between Scene builder and javafx

Hello,
I'm building an image using javafx, i don't want to use fxml, but i tried to use scene builder to help me identify my object corrdinates.
I have to add a background picture and to add some other graphic object, when using exactly same coordinates for my background picture and graphic object (got from generated fxml) i did not find the same corrdinates?
Is there any clear reason.
Help :)

Thank you jrguenther! yes, I the input images with File>Import>Media menu
But, how I program a piece (image png) to move with the mouse click on the board?
My project is a game.
Please!

Scene Builder 1.0 will not start

Hi. For a number of months I've been using Scene Builder 1.0 (BuildInformation = Version: 1.0-b50, Changeset: 22db15834430 Date = 2012-08-07 16:33) on a Windows 7 system. However, it has been about a month since I last used Scene Builder. Today, I tried to use Scene Builder and it would not start. No error message was displayed. I uninstalled Scene Builder and reinstalled it... that did not help.
I noticed the logging.properties file in the "bin" directory. This file contained: java.util.logging.FileHandler.pattern = %t/scenebuilder.log. So, I looked in the system temp directory... no log file.
The JRE (used by my browsers, etc.) has been updated within the last month, but I am guessing Scene Builder is isolated from any JRE changes, right?
I downloaded and installed Scene Builder 1.1 (pre-release). Fortunately, Scene Builder 1.1 starts.
However, I would still like to know why Scene Builder 1.0 does not start. Any ideas on how to troubleshoot the problem?
Thanks!
Chris

Glad it's not just me...
I had the same problem. Either it downloaded a patch and fixed itself, or this worked:
Go to Control Panel / Add / remove programs (in Control Panel / all control panel items / Programs and Features / Add remove programs)
Right click on Adobe Reader and select Change.
Choose Repair
This appears to have reinstalled the Core DLL file, and it seems to be working normally now.
Good luck

Will pages automatically reformat to correct size when using Folio Builder or do I have to make pages iPad format, for example, in InDesign document set up from the start?

Will pages automatically reformat to correct size when using Folio Builder or do I have to make pages iPad format, for example, in InDesign document set up from the start?

Moved to DPS forum.
You need to set up the pages appropriately for the target device. For iPad that's 1024x768.

To import all songs on the CD, click Yes in the window that appears. iTunes starts importing the CD.---I am using a Dell and can't import the CD I need because the window doesn't automatically pop up. How do I fix this? Any thoughts?

"To import all songs on the CD, click Yes in the window that appears. iTunes starts importing the CD."
I am using a Dell and can't import the CD I need because the window doesn't automatically pop up. How do I fix this? Any thoughts?

You could try my script ConvertFormat and see if you like the results. Would be easier than inserting the CDs and correcting the tag info again. Just be aware this is a one-way trip. Once you've thrown away some quality to shrink the files you can't get it back without going back to the source. You may better off investing in a bigger drive.
If you just want to squeeze more on the iPod you can use the built-in iTunes option to convert files to a lower bitrate as they are added to the device.
tt2

How come when I use a Internet that I have already used it doesn't automatically connect

How come when I use an Internet that I have already used it doesn't automatically connect?

Does the iPod connect to other networks?
Does the iPod see the network?
Any error messages?
Do other devices now connect?
Did the iPod connect before?
Try the following to rule out a software problem:
- Reset the iOS device. Nothing will be lost
Reset iOS device: Hold down the On/Off button and the Home button at the same time for at
least ten seconds, until the Apple logo appears.
- Power off and then back on the router
- Reset network settings: Settings>General>Reset>Reset Network Settings
- iOS: Troubleshooting Wi-Fi networks and connections
- iOS: Recommended settings for Wi-Fi routers and access points
- Restore from backup. See:
iOS: How to back up
- Restore to factory settings/new iOS device.
If still problem make an appointment at the Genius Bar of an Apple store since it appears you have a hardware problem.
Apple Retail Store - Genius Bar

Scene Builder: cannot edit when I embed a custom control!

Hi guys, I'm having an issue with Scene Builder and embedded custom controls...
I have a LoginPanel .fxml/.java module, which contains two re-usable custom controls I've built:
* StatusZone .fxml/.java
* LanguageSelector .fxml/.java
The application runs.
However, I can't open LoginPanel.fxml to edit it with SceneBuilder v1.1 (developer preview).
To be specific, in LoginPanel.fxml, I have this data:
<StatusZone fx:id="statusZone" />
<LanguageSelector fx:id="languageSelector" />
SCENARIO 1
-- LoginPanel.fxml --
<?import kalungcasev2.view.StatusZone?>
<?import kalungcasev2.view.LanguageSelector?>
I get:
Warning: File 'LoginPanel.fxml' contains references to types that could not be loaded.
Missing types are [kalungcasev2.view.StatusZone]
I can click 'Set up classpath', but no matter which folder I choose, it doesn't seem to fix the problem.
SCENARIO 2:
-- LoginPanel.fxml --
<?import kalungcasev2.view.*?>
I get:
Warning: File 'LoginPanel.fxml' contains references to types that could not be loaded.
Missing types are: [StatusZone, LanguageSelector]
I can click 'Set up classpath', but no matter which folder I choose, it doesn't seem to fix the problem.
How do I fix this?

Hi,
If no ClassLoader is configured in the FXMLLoader, then the FXMLLoader will try to load the
classes using the System/Context class loader.
This works well in the context of an application where everything is in the system class loader.
In SceneBuilder however - your classes will not be in the System class loader, but in a special
URL class loader that SceneBuilder created for your FXML file.
SceneBuilder sets this ClassLoader on the FXMLLoader that loads your top FXML file,
but it can't do anything for the instances of FXMLLoader that your own code creates.
Therefore - it's best to configure your FXMLLoader with the appropriate class loader,
which is usually the class loader that loaded your custom type.
See https://javafx-jira.kenai.com/browse/DTL-5177 for more details.
-- daniel
Edited by: daniel on Apr 25, 2013 7:33 AM
Sorry - to be more precise:
loader.setClassLoader(this.getClass().getClassLoader());
is the correct line.

Neither Automatically Resize nor Zoom to Fit working

Hello out there in Appleland,
Neither Automatically Resize nor Zoom to Fit is working in Preview 5.0.3 under Snow Leopard. Zoom to Fit acts just like Actual Size or <Command> 0 and Automatically resize doesn't work at all. This must be and bug, so please explain how this can be permanently fixed, even at the command line level.
Thank you.
Best regards,
Bob
Denver, CO

I've found out a little more about Preview and its bug through a process of elimination.
After examining Automatically Resize for Preview 3.0.9 on my old PowerBook G4 with OS 10.4.11, Preview 4.1 on my iMac with OS 10.5.8, and now Preview 5.0.3 on my MacBook Pro with OS 10.6.8, I discovered they all work the same way. When Automatically Resize is checked the image is only resized when the window is reduced but never when the window is enlarged to a size greater than the image's Actual Size, which is a worthless feature for smaller images. I don't think this is the way it is supposed to work, but I may be wrong.
Where 5.0.3 differs from the other versions of Preview is in Zoom to Fit. Under the View Menu, Zoom to Fit is grayed out unless the image stretches beyond the borders of the window (i.e. Automatically Resize toggled off). In this case, the image will be reduced to the size of the window when Zoom to Fit is selected. On the other hand, if the image is smaller than the size of the window, Zoom to Fit is not grayed out but neither does it enlarge the image to the size of the window when selected. In other words, Zoom to Fit in 5.0.3 is only good for reducing an image to fill a smaller window but never for enlarging an image to fill a bigger window if that window is larger than the Actual Size of the image.
Perhaps the problem is with Preview 5.0.3 failing to access com.apple.Preview.ImageSizingPresets.plist since removing all the Preview plists and launching the application anew does not recreate this particular plist. Also, the modified date on the original com.apple.Preview.ImageSizingPresets.plist never seems to change.
This is a damned annoying bug and should have been fixed when Snow Leopard was the standard. In my opinion, the fact that this wasn't caught reveals Apple's slipping standards and a concentration on their growing market in mobile devices. I feel I have a right to say this since I've been a loyal Mac user since the early 1980s.
For those who suggest I move to Lion or beyond, you can keep the economy going with your new software purchases. For now, I'm going to continue using Rosetta and my old, third-party applications in Snow Leopard.

What happened to ?scenebuilder-stylesheet ... in Scene Builder 2?

Hi,
Did the way <?scenebuilder-stylesheet some-style.css?> works get changed in Scene Builder 2? When I use Preview -- Scene Style Sheets -- Add a Style Sheet, I can't figure out where Scene Builder 2 is storing the info for the previewed style sheet. When I commit the FXML file and check it out on another machine, all that information is lost.
What's the recommended way to deal with CSS for for files that are going to be included in other files using fx:include? For example, assume I have 2 FXML files:
1) Main.fxml - A StackPane that includes Sub.fxml via fx:include. Specifies main.css as a style sheet.
2) Sub.fxml - Uses styles from main.css, but no style sheet is attached directly.
It doesn't seem right to add main.css to both files. If I remember correctly, Scene Builder 1 would use <?scenebuilder-stylesheet some-style.css?> to make this work, but it seems to be ignored in Scene Builder 2. Can anyone suggest another way of doing what I want?

Yes it changed.
For some reason, in SceneBuilder 2.0, they decided to have the CSS preview and the I18N preview information stored in the SceneBuilder's preferences instead.
That is using Java's Preferences API.
So for example, in Windows, those info are stored in the Registry in, hold your breath: HK_CURRENT_USER\Software\JavaSoft\Prefs\com\oracle\javafx\scenebuilder\app\preferences\/S/B_2.0\/D/O/C/U/M/E/N/T/S/<name of your FXML file here>
Which means that :
CSS and I18N preview gets broken as soon as you move the FXML file around.
Hilarity ensues (or not) as soon as you have 2 FXML with the same mane in different projects and you move them around (one may get the CSS for the 2nd one if it ends up in the same location).
Your registry will get bloated with references to long deleted FXML after a while...
This also probably means that the same should be stored in some XML file in ~/.java/ in Linux and Mac OS X.
On the other hand, you do not have anymore the issue in SceneBuilder 1.x which was looking for the hard-coded location of the CSS and properties files when moving FXML files between computers when working on a multi-person/multi-computer project.
Also, it's not as bad as SceneBuilder 1.1 which was keeping a whole copy of the directory structure I had in my projects in the Registry for seemingly no good reason.

Menubar doesn't automatically resize, using scene builder

Similar Messages

Maybe you are looking for