Open Oliver-Loeffler opened 3 years ago
I had a look at code and apparently is intentional. Maybe a confirmation dialog may appear when try to open a new instance, what you think?
With a change on this method is possible to run two instances of scene builder if are different versions. Appending the current version of scene builder, it will create a folder like that. /home/my_user/.scenebuilder/16.0.0-SNAPSHOT/MB/
`public class AppPlatform {
private static String applicationDataFolder;
private static String userLibraryFolder;
private static String messageBoxFolder;
private static MessageBox<MessageBoxMessage> messageBox;
public static synchronized String getApplicationDataFolder() {
if (applicationDataFolder == null) {
final String version = getSceneBuilderVersion();
final String appName = "Scene Builder"; //NOI18N
if (IS_WINDOWS) {
applicationDataFolder
= System.getenv("APPDATA") + "\\" + appName+"\\"+version; //NOI18N
} else if (IS_MAC) {
applicationDataFolder
= System.getProperty("user.home") //NOI18N
+ "/Library/Application Support/" //NOI18N
+ appName+"/"+version;
} else if (IS_LINUX) {
applicationDataFolder
= System.getProperty("user.home") + "/.scenebuilder/"+version; //NOI18N
}
}
assert applicationDataFolder != null;
return applicationDataFolder;
}
...`
This is an easy approach, at least for linux, what you think?
Souns like a very good idea. Asking the user is alwas good. @abhinayagarwal , what do you think? Would this fit with the way Scene Builder is supposed to be used?
In my experience, Scene Builder stores its data in various locations, including and not limited to the ApplicationDataFolder
. There are a few instances where Scene Builder depends on Java preferences (https://github.com/gluonhq/scenebuilder/issues/369)
If we want to pursue this further, we need to make sure that all the data for the 2 instances is stored separately to avoid any unnecessary complications.
In my experience, Scene Builder stores its data in various locations, including and not limited to the
ApplicationDataFolder
. There are a few instances where Scene Builder depends on Java preferences (#369)If we want to pursue this further, we need to make sure that all the data for the 2 instances is stored separately to avoid any unnecessary complications.
Yes you are right, i believe that is more easy deal with different folders for different versions than change the code that avoid open new instances.
Maybe this cannot be deal like a bug but a new feature to be discussed. thanks
A similar topic raised with issue #369. Therefore I would opt-in with having separate settings and storages for individual installations of SceneBuilder. This also implies, that it should be first of all possible to have multiple versions installed. This is not possible yet but a requirement for #346 und #369.
Related to #579.
Starting multiple instances of SceneBuilder does not work.
Expected Behavior
SceneBuilder.exe
(from link or from CLI) shall open a new Scene Builder windowSceneBuilder.exe
should open a new window backed by an independen new instanceCurrent Behavior
SceneBuilder.exe
works.SceneBuilder
(regardless if same version or different version) does not workSteps to Reproduce
Running tests entirely from IDE helped me as follows:
Environment
Screenshots