Facility Control

Hi,

two questions, possibly vaguely related...

Is there a way to prevent multiple instance of Dashboard from running. I find I get Java errors related to sockets in use if a second instance of my Dashboard is opened - I'd like to catch these error gracefully, or prevent two instances of the same Dashboard being opened.

Are there any command line options I can add to a desktop shortcut to specify which .grid file to open, and to make it open in full screen mode.

Many thanks,
Martin

Hi Martin.
There is not currently a solution to prevent multiple instances of DashBoard from running. In some cases, it is necessary to have them running as individual DashBoard instances have a limit on how much memory they are allowed to use and it is possible that a customer's requirements may exceed them if multiple [very] large panels are used.

One quick solution to make DashBoard launch with a specific *.grid file and remember its fullscreen state is to save a layout (SHIFT + F10) with the grid file open and DashBoard in fullscreen mode. You can then create a shortcut and add -layout LAYOUT NAME as a command line option to the shortcut (just make sure your layout name has no spaces in it). There may be other options that will work for you but I think this one gets the closest to what you're after.

James
#DashBoard

Hi James,

the Layout trick works brilliantly, thank you. I'll try to build something into my code that can trap the multiple instance problem.

thanks again,
Martin
#DashBoard

One thing we've seen people do is check for the presence of a file on startup and, if it is there, show a "DB ALREADY RUNNING" screen. You can create an onclose handler to delete the file when DashBoard shuts down. Naturally, you'd also need to have a "LOAD ANYHOW" option in case DashBoard/the PC was not properly shut-down).
#DashBoard

James, I missed your post. Thanks, this sounds like a great way to detect multiple instances running, it will be in my finished panel!
#DashBoard