4 ms·
A minor nitpick to be sure, but it's odd that you must close down all other copies of your application before your development copy will launch. There is proba
by tux1968 10y ago
A minor nitpick to be sure, but it's odd that you must close down all other copies of your application before your development copy will launch. There is probably a way to work around this, but the limitation is hard enough to get around that it is mentioned in the Builder instructions.
This seems like an unnecessary limitation of the Gnome environment. It would be nice to be able to compare your existing release to your changed copy and run them side by side.
- snuxoll 10y ago> This seems like an unnecessary limitation of the Gnome environment. It would be nice to be able to compare your existing release to your changed copy and run them side by side. This is because GNOME applications have a hybrid of Windows and OS X behaviors now, due to the addition of D-Bus activation. Applications still exit when you close the last window, but each application has a unique identifier (org.gnome.gedit, etc) and when the binary starts it will search for a running instance and tell it to activate if present.
- audidude 10y agoThe problem at hand is that applications are "single instance" by default. For Builder 3.26 we'll get something in place that starts a dbus-session to separate the built application from your host system. Another option is to finish the simulator, but I have a debugger to finish first.