FSX [c++] for-loop to generate strings?

[Vitus]

Hi,

I am currently working on a gauge that contains a lot of dynamic text. I found that programming it using STRING macros is extremely tedious and I was wondering if there's a way to automate it. So, instead of manually typing three dozens of STRING macros, is it possible to have a for-loop generate the gauge elements?

 

[kalong]

create array, use it using for-loop

 

[JB3DG]

Don't use gauge macros period. Use the GDI+ example instead.

 

[WarpD]

Even the GDI+ example uses a gauge macro... just sayin'... though I agree that a GDI+ approach would support his needs the best.

 

[ddawson]

The straight answer to your question is no, you can't do that.

 

[Vitus]

Hi guys,
Thank you all for chiming in! It took me the whole day, but I switched to a GDI+ scheme. It seems to work so far - I can create multiple lines of text using for-loops. Fun!

Generally speaking, what's the advantage of using GDI+ over a pure macro-based gauge?

 

[WarpD]

Better text formatting with regards to displaying strings.

 

[Vitus]

I see.
I always had trouble with transparency using the default macros. Is there a way to get a proper alpha-channel rendering done using GDI+? Similar issues with the rendering of strings - they all get a black outline where it should be semi-transparent. I currently avoid that problem by first drawing a filled-in rectangle, but I'd much rather see some proper transparency.

 

[Vitus]

Another thing I noticed is that my fonts are not used any more. With XML strings as well as with the normal string macros, I was able to use custom fonts that are copied to the <sim>/Fonts folder. Using GDI+, those fonts don't seem to work. I initialize the font with this:

    mMachineFont = new Font(L"Veteran Typewriter", 24.0f, FontStyleRegular, UnitPixel);

 

[WarpD]

In GDI+ the fonts available are the ones installed in the OS, unless you have a font resource you load directly. It's far easier to install the font to the OS.
As for transparency... if you're taking about a transparent gauge... that requires a few changes (24-bit images, etc), but is possible.

 

[Vitus]

I don't want to install the font automatically, I feel that's a bit invasive. . In the meantime, I found this:
https://docs.microsoft.com/en-us/wi...diplus-creating-a-private-font-collection-use
will have a look and see if it works. But now I've got another issue: in order to load the font, I need to locate the "font" folder of the sim. gnnnaaaa....

Transparency: for now the problem lies with the strings. They all have rugged edges, unless I draw a rectangle under them, which I'd like to avoid if at all possible. Maybe I should mention that I am drawing the C++ gauge on top of another XML gauge, I don't know if that affects the outcome.

 

[WarpD]

I have never, in my insanely long career writing software ever heard anyone call installing a font invasive. That is indeed a first. LOL
Check out SetTextRenderingHint and SetSmoothingMode.
Overlapping gauges can have visual side effects.

 

[Vitus]

Well... I really dislike the fact that my system fonts are filled with symbol libraries from some programs. That makes it so much harder to find what you're looking for.

Here's what I found:

std::wstring tmp_wstr = path_sim.wstring()+L"\\fonts\\veteran typewriter.ttf";
PrivateFontCollection privateFontCollection.AddFontFile(tmp_wstr.c_str());
int count = privateFontCollection.GetFamilyCount();
if (count == 0)
    debug_log("Could not load custom fonts.");

Font * mMachineFont = new Font(L"Veteran Typewriter", 18.0f, FontStyleRegular, UnitPixel, &privateFontCollection);

where path_sim is a string that holds the directory of the sim, obtained through GetModuleFileNameA().




I tried doing this:

                    mGraphics->SetTextRenderingHint(TextRenderingHintAntiAlias);
                    mGraphics->SetSmoothingMode(SmoothingModeAntiAlias);

I call those functions in the PANEL_SERVICE_PRE_DRAW before all the strings are set. Doesn't work, though. Any idea what could be wrong?

 

[WarpD]

I would need to see an image of the GDI+ render.

 

[Vitus]

The background is an image loaded with an XML gauge. The text is the C++ gauge in question.

 

[WarpD]

That looks correct. Have you reviewed the actual appearance of the font itself?

 

[Vitus]

Not sure if this is related, but I also have an issue with the redrawing of the gauge. When I open the next page in the book, a new set of data is loaded from an SQLite database to populate the page. Currently the new data is drawn on top of the old one, without deleting it first. The MAKE_STATIC macro of the gauge has those flags set:
IMAGE_CREATE_DIBSECTION | IMAGE_USE_TRANSPARENCY | IMAGE_USE_ALPHA | IMAGE_USE_ERASE

I didn't set the IMAGE_ERASE_ALWAYS, because otherwise the underlying XML gauge gets deleted as well.

 

[Vitus]

In comparison, here's how the font looks like when placed on a FillRectangle background:

 

[WarpD]

Ok... before you do any rendering... always do a FillRectangle with the default background color to 'erase'. There is a GDI+ Clear() method... but it's horribly inefficient by comparison and should only be used when doing a transparent gauge.

 

[Vitus]

Is there a way around this? I don't want to fill anything, I want the gauge to be transparent so that the underlying XML gauge can render the background image. I tried to do a FillRectangle with an alpha value of '0', hoping that the call itself would cause the panel to redraw. But noooo...

edit: I currently have a Clear() call in there as well. Doesn't help.