[Altia Forum] How do I position Altia Runtime window on secondary display

Let's say the main display is 1680x1050 and the 2nd display is 1024x768. In this case, Windows (at least XP) will let us put a window on the 2nd display that is as large as 1680x1050. So we can size the Altia Runtime main view to 1024x768, keep the borders on the Altia Runtime window, and just position it so that the left and top borders are not showing on the 2nd display.

This is done with settings in the .rtm file. There is always a file with a .rtm extension associated with the .dsn design file. The .rtm file is just a simple text file. Open it in Notepad.

For these example changes/additions to the .rtm file, the main display is 1680x1050 and the 2nd display is 1024x768.

First change the Altia window width and height to 1024x768 in the .rtm file if it is not already 1024x768:

Altia*AltiaScene*width: 1024
Altia*AltiaScene*height: 768


Now add a geometry setting to the .rtm to show the runtime window 1680 pixels to the right of the main 1680x1050 display's left edge. This puts it on the 2nd display. Actually use 1680-4=1676 on Windows XP to hide the left border region of the runtime window. Also nudge the runtime window 29 pixels higher on Windows XP to hide the top border region of the runtime window (the +-29 does this, it is not a typo, really use +-29).

Altia*Altia-GraphicsEditor*geometry: =+1676+-29

If no borders is essential, the transparent border settings can be added. Note the transparent region is chosen to be small and beyond the visible window area so it does not cause any side effects. Setting transColor is absolutely necessary for transBorder to be recognized so also set transLimit to keep Altia from chewing up CPU cycles trying to look for the transparent color everywhere on the screen:

Altia*AltiaScene*transColor: 255 0 255
Altia*AltiaScene*transBorder: True
Altia*AltiaScene*transLimit: 3000,3000,3001,3001


After making these changes to the .rtm file, we want to fix the .rtm file so that Altia Design does not overwrite it the next time the .dsn file is saved in Altia Design. We can do this while we are still editing the .rtm file by changing the top line to read something like:

! Altia Design Run-Time View Configuration File - NOTWritable

Note the NOTWritable instead of Writable. If the first line of the .rtm does not exactly match what Altia Design expects, the .rtm file is not overwritten when the .dsn design file is saved.

OK, now you can start Altia Runtime altiart.exe with the .dsn file. It will read the associated .rtm file and configure itself appropriately. For example, here is a command to run Altia Runtime from a PC .bat script or Command Prompt window:

altiart.exe my_design_file.dsn

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.