Use a polygon or rectangle. Better than messing with a bitmap.Because the whole gauge is active, dispense (get rid of) the Area code, that is,andcheers,nick

>Hi J, glad the tutorials are proving useful. I'd like to>write some more, but finding time is difficult.>You click on the gauge and that 'frees-up' (not freeze-up :()>FS so you can edit an active gauge and save it. Without the>initial click, you cannot save a gauge. After saving the>gauge, click again and the changed gauge is reloaded. You do>not have to reload the plane.>Not sure the polygon is documented anywhere. Have a search>here for a lot of useful stuff. The following might prove>useful. You put these vector graphics into the code where you>would normally put in any bitmap information. The square>brackets means this info is optional or rather additional. If>you use any of the info in the square brackets, then remove>said brackets.>cheers,>nick>>Rectangles:>>LineWidth="2" Color="#000000">[Fillcolor=#000000] Bright="Yes"/>>>Color="Cyan" FillColor="#000000" Bright="Yes"/>>>Circles:>>Color="#000000">[backgroundcolor=#000000] or>[FillColor=#000000] Bright="Yes"/>>>Lines:>>LineWidth="xx" Bright="Yes">> > > > > []>>>Polygons:>>[LineWidth=xx] Bright="Yes">> > > > > []>Thanks Nick,I'm gonna play with it. I understand about the tutorials - I'd be happy to "donate" towards seeing them finished. I am guessing that the Flight1 PC-12 is not yours. I'd buy yours but I have the F1 model. Perhaps I can show my appreciation by purchasing your King GPS.On the vector graphics - very encouraging. How does the performance and fluidity compare to GDI/GDI+? I find bitmap-based C gauge programming approachable, but then if it's going to be bitmap-based, then why not just use the XML scripting? Now, if these vector graphics are possible in XML scripting, why bother with GDI?Thanks again,J-

Well,I do notice that you are all using the K: events rather than the alternate syntax - maybe this is the key.J-

>On the vector graphics - very encouraging. How does the>performance and fluidity compare to GDI/GDI+? I find>bitmap-based C gauge programming approachable, but then if>it's going to be bitmap-based, then why not just use the XML>scripting? Now, if these vector graphics are possible in XML>scripting, why bother with GDI?All XML 'vector graphics' are parsed and translated to GDI drawing code. The G500 default GPS is a prime example.OTOH, if you want any of the benefits of GDI+ (advanced font formatting, linear/radial gradients, etc.) then you'll have to stick with C++/GDI+ gauge coding. ;)

Ughh...Thanks Bill. I've been doing quite a bit of GDI+ in .NET/C# in the last year and I PRAY that a managed-code approach to panel making comes along soon - the C used for panel-making has always felt archaic (to be fair, so was Win32 programming when I was tortured with that).I've got quite a curve to climb with this XML stuff. Any advice on getting better at RPN? J-