The constant is a string and should be called "MYFILENAME". Yes, you will need to create the variables. The alternative is to export the macro from my project and import it into your project. This will retain the local variables, but you will need to manually link this to the AddConst even...

Here are the steps that I did to create it in that attached project: Create a global constant Double-click the Compile::Ev_AddConst event in Project Explorer Double-click <Add new> Click "OK" Click "OK and Edit Macro" Add code as per my example to the Ev_AddConst macro If the &qu...

Hopefully the attached project shows you how to do it. I used a combination of the "AddConst" event to manipulate the value (and size) of a constant and the "Expand.PathName" to retrieve the name of the file. If you compile the project, the "MYFILENAME" Flowcode constan...

Ben is the master of this kind of thing, but I think you can use it in conjunction with the Ev_AddHeader event. This allows you to change or add to the C code generated for the component. Here's a snippet from the GLCD_Base component: Screenshot 2025-12-04 103037.png In your case, you could potentia...

May also need "main"?

If you mean getting the Flowcode version, then the "GetFCVersion" function provides it. My debug build is showing 0x0B0001 which means v11.0.1 (treat the returned value as 0xAABBCC where the version is AA.BB.CC). Screenshot 2025-12-04 091038.png For a macro name, it depends on exactly what...

We have disabled the v10 purchasing mechanisms and generally prefer users to be on the latest version of Flowcode. But there is a way to update v10 in some circumstances. I will PM you with some details shortly.

Sorry, but there are currently no free STM32 targets for Flowcode.

Please attach a project file so I can try to replicate the issue you are seeing. That's really the best way to solve this problem. If you are reluctant to post your project here, then you could perhaps create a small project that shows the error you are seeing. And if that is no good, you can post y...

I've just checked the "generic 4x20" LCD in v10 and it seems to work ok for me. Do you have an example file that shows the problem? That would really help us solve this issue for you.