Hi Jean-Luc,

in the GNS manual (page 5) it is said : "In addition, the gauges can be manually configured to
reserve and display a surrounding coloured fixed-size border for convenience."

So far I succeeded in setting both GNS 530 and 430 into their respective small monitors but, when fullscreened using ALT-ENTER, both GNS screens are a little bit outsizing my frames.

So my question regarding the manual configuration you mentionned in the manual (pun intended 😉 )

How can you resize the fullscreen no-bezel window (or add fixed-size border) so as to fit your physical frame ?

TIA

Francois

Edited May 8, 20206 yr by altack

Hi,

You'd need to create a "Gauge Rendering Setting" in the .ini file for this first. This will make things easier.

Then, you can edit the panel.cfg file to associate the rendering setting section (using its name) to any instance of the RXP gauge, using the 5th parameter.

This is better explained p14.

You might want to also review the following discussion (start with the recommended posts) because it explains and uses this concept extensively:

 

Edited May 11, 20206 yr by RXP

Ok Jean-Luc, I grasped the rendering setting section concept thanks to the thread and your manual so, before fiddling with the .ini file I just want to confirm a few  points:

if I want to move the whole screen down by, let say, 3 pixels I have to resize it with the line « gauge## = File ! Name , x, 3, w, h [,param] ».

if I want to move up the bottom of the screen I need to play with the height parameter, something like gauge## = File ! Name , x, y, w, h-3 [,param] , right ?

if so, what about the proper screen ratio to respect as per the manual ?

Sorry by putting the initial message in the wrong section and thank you for straightening things up !

Hi,

There are different concepts at play here:

1) size of the window containing the gauge.

2) size of the gauge within the window.

3) position of the gauge within the window.

4) all the above can be stretched to any size, which is implying any 'offset' whether y = y+3 or h  = h-3 will stretch too.

The easiest is the border.size setting in order to render a border/edge around the gauge screen pixels within the popup window. Unlike the position/dimension in the gauge##= panel.cfg file, which is proportionally resizing with the containing window, the border.size setting is in pixels. Whatever the popup window size, the gauge will draw the surrounding edge with exactly border.size pixels around.

You'd use border.size to 'fill' a void when placing the gauge within the boundaries of a 3D bezel which is not exactly accurate in dimensions, or to get an area you can right-click for the popup window menu, or to drag the window around for a NO_BEZEL GTN gauge.

That's exactly what I needed !

My GNS combo is fitting snugly now 🙂

One last question though : what is the proper RGB or RGBA code # for...no color at all (i.e. full transparency) ?

When googling that I only get what the A of RGBA stand for...

Thanks for your great support !

 

#11223344 =

11 red
22 green
33 blue
44 alpha

You'd use #00000000 then for transparent black.

However, I've just reviewed the code and alpha is not supported right now. This is not a bug, rather an omission, but I'm wondering whether we didn't remove alpha support 2 years ago because of XP11 rendering not capable or not supporting it back then.?!!?

This will be added in the next update IIF there is no side-effect with X-Plane.

 

Looking forward for the next update and thanks again for your great support !