One of the most annoying features of the Matlab compiler is the fact that compiled (deployed) applications take a loooooooooong time to load the first time that they are run on the target platform, or after a computer restart. This can take anywhere from 15-60 seconds, depending on platform characteristics. During this time, there is absolutely no visual indication that the application is loading. The application displays no window or other visual cue to let the user know something is loading.
I have seen many users double-click the application icon again and again in frustration, thinking that perhaps the application did not start when they first tried. In fact, this launches multiple applications and MCR loads at the same time, which only prolongs the overall time that it takes the application to actually load and display.
The “normal” solution for this would be to display a splash figure or start-up message at the very beginning of the application. Unfortunately, this doesn’t help because the vast majority of the launch time is due to MCR load time, which happens before any user code is executed. The result is that our application’s splash figure or msgbox will only be displayed after the very long time in which the application appears unresponsive.
I developed a splash-screen wrapper application for deployed applications that solves this problem on Windows platforms.
The idea is to create a stand-alone non-Matlab application that displays a user-specified image (splash) in a dedicated window at the center of the screen, and then immediately launches the requested deployed Matlab application in the background. The wrapper then waits for the Matlab application to load, and automatically closes the splash window when it detects that the target Matlab GUI has finally displayed.
The effect is that upon launching the application, the user sees immediate feedback in the form of a dedicated splash window (for example, displaying an image of the application or company logo with the message “Loading – please wait…”). This does not make the target application load any faster, but at least users are given immediate feedback that prevents them from re-launching the application. Users also report that this makes the application appear to load faster. This is due to a psychological effect called “perceived performance” – we also see this effect with phone ringtones and elevator floor-level indicators.
My splash wrapper application receives the following input parameters:
- splash image filepath (BMP/JPG/GIF – note that other formats are NOT supported)
- splash image width in pixels (will resize the image if necessary)
- splash image height in pixels (will resize the image if necessary)
- target window title string
- title matching mode:
- 1 = match at the beginning of the title (case sensitive)
- 2 = match at any place within the title (case sensitive)
- 3 = match the entire title (case sensitive)
- -1, -2, -3 = case-insensitive version of the above values
- target application filepath (this is the actual deployed application executable)
- optional input parameters for the target application
splash MySplashImage.bmp 600 450 "My GUI Title" 1 "C:\Program Files\MyApps\MyTargetApplication.exe" param1 param2
This will display the MySplashImage.bmp image in a 600×450 window (resizing the image if needed) until a window with a title of “My GUI Title” appears. In the example above, the parameters to the splash application were as follows:
- image filepath – MySplashImage.bmp
- image width – 600 pixels
- image height – 450 pixels
- target window title string – “My GUI Title”
- title matching mode – 1 (=match at the beginning of the title)
- target application – “C:\Program Files\MyApps\MyTargetApplication.exe”
- optional input parameters to your target application – param1, param2
You can create a shortcut that runs the above command-line and then when the user clicks the shortcut it will automatically launch splash.exe, which will automatically display the splash screen and then load your main application.
I’ve contributed dozens of useful open-source utilities to the Matlab user community over the years (look at my File Exchange profile). This utility is different because it directly targets compiled applications, which are typically used commercially. For this reason, my splash wrapper application is not free (but also not very expensive). You can purchase a copy here, and I will email it to you.
Please note: this is a Windows application. It will not work on Macs or Linux.
Interested in learning more about actual and perceived performance improvement tricks in Matlab? Consider joining my Matlab Performance Tuning course in Geneva on August 21, 2012 – email me (altmany at gmail dot com) for details.
- Docking figures in compiled applications Figures in compiled applications cannot officially be docked since R2008a, but this can be done using a simple undocumented trick....
- Removing user preferences from deployed apps An unsupported MathWorks Technical Solution explains how to remove private information from deployed (compiled) matlab applications. ...
- Disabling menu entries in deployed docked figures Matlab's standard menu items can and should be removed from deployed docked figures. This article explains how. ...
- Enable/disable entire figure window Disabling/enabling an entire figure window is impossible with pure Matlab, but is very simple using the underlying Java. This article explains how....
- Minimize/maximize figure window Matlab figure windows can easily be maximized, minimized and restored using a bit of undocumented magic powder...
- Transparent Matlab figure window Matlab figure windows can be made fully or partially transparent/translucent or blurred - this article explains how...