In the previous post where we introduced the new RXI files we mentioned some new command line switches added to OpenInsight 10. In this post we’ll take a look at them and describe what they do.
/TB (taskBarID)
Under Windows 7 and 8 multiple instances of an executable launched from the same directory are grouped under one icon on the taskbar, making navigating between them quite tedious. To allow an executable to override this behavior Microsoft introduced a new application property called the “Application User Model ID” – a simple string that can be applied to an executable instance to differentiate it from other sibling instances, thereby allowing them to be un-grouped.
Windows assigns a default value to this property at runtime based on the executable name and the starting directory. The OpenInsight /TB switch (or taskBarID element in an RXI file) allows you to set your own unique value for this property so that your application can be differentiated on the Windows taskbar (A read-only property called TASKBARID is exposed by the SYSTEM object at runtime to provide access to this value).
The Application User Model ID must be set before any forms are created by an executable which is why it can only be set via the RXI file or the command line switch.
If you wish to find out more details about the Application User Model ID please see the MSDN documentation about the SetCurrentProcessExplicitAppUserModelID function.
/SI (singleInstance)
This is a boolean (1/0) flag that ensures there is only one instance of the specified OI application executing on a workstation. Any other OI applications from the same executable are unaffected.
/EL (elevate)
This is a boolean flag (1/0) that specifies if the application requires Administrator privileges when it is launched. If this switch is set to “1” and the Windows user is not an administrator they will be asked to provide Administrator level credentials before they can continue (via the standard Windows UAC prompt).
/MD (minDisplaySecs)
When displaying a banner image file at startup this switch specifies the minimum number of seconds to display the banner for.
/EP (enginePath)
This switch specifies an alternative OpenEngine path (normally the Presentation Server expects to load OpenEngine from the same directory where it is located).
/2D (useD2D)
This is a boolean flag (1/0) that specifies if the system should use Direct2D technology for rendering when available. By default OpenInsight will attempt to use Direct2D where it can (Windows Vista SP2, Windows 7 and later), but it can be forced to use GDI rendering instead if this flag is set to “0”.
/DP (useDPIScaling)
This is a boolean flag (1/0) that specifies if the application should automatically scale coordinates when used on a high-DPI system.
[Edit: 01 Feb 13 – AM switch renamed to TB and taskBarID]
[Edit: 08 Jan 13 – Added DPI Scaling modifications]
(Disclaimer: This article is based on preliminary information and may be subject to change in the final release version of OpenInsight 10).
Building OpenInsight 10 
For those of us not up to date with graphical standards what does D2D provide that GDI doesn’t?
There’s an article in the pipeline that explains Direct2D in a little more detail, but if you really want the full lowdown you can find a comparison on Microsoft’s site here:
http://msdn.microsoft.com/en-us/library/windows/desktop/ff729480(v=vs.85).aspx
Pingback: OpenInsight and Direct2D | Building OpenInsight 10
Pingback: The APPUSERMODELID property | Building OpenInsight 10
Pingback: Subject to change… | Building OpenInsight 10
Does the /MD switch allow the banner to run asynchronously while the entry point is loading up or will the entry point still wait until the banner is taken down?
Any entry point form will be shown after the banner – the /MD switch is basically to allow the user time to read the banner as some systems that load fast make this difficult.
Any other initialization task (like the ones in F32 of the engine ENV record for example) will run “in the background” while the banner is displayed.
Carl,
Thank you for the response. Given that some entry points take some time on their own to run processes within the CREATE event – and perhaps do this before the form becomes visible – you may want to find a way to allow the banner to remain visible while this is happening. Most applications I launch these days allow the splash screen to stay on top as the application is visible in the background.
Hi Don,
I can see the value in that – I’ll take a look at it … we should be able to leave it up unless we need a login dialog …
(See, even more good news! :))
Pingback: The Future Is Now – Launching OpenInsight Applications | SRP Update (Blog)
In the RXI file I have set a bannerFile, however, no matter what I use, a PNG or a JPG, the image shows as transparent. With PNG, it is transparent to point of not really being able to see it and with a JPG is uses the white background semi-transparent with the images transparent. I need it to be a full white background pic and would like to avoid fade in/fade out with no transparency at all. Any switches in the RXI for this?
Hi Greg – email me a copy of the file you’re trying to use and I’ll take a look…