No problem. There will be a file in the same folder as the Flowcode *.fcfx project with the same name as the project file but with the extension ".msg.txt". This is the file generated when Flowcode compiles your project and contains all errors. Just attach that as well as the project file.

While we fix this, there is a workaround you can use. Either use individual LEDs instead of the array, or set each LED array to have all 8 LEDs (even though some are unused). If the latter, you could add a shape over the unused ones to block them from view on the panel (or arrange them so the unused ...

That image is very small.

Please attach the *.msg.txt file for the project so we can see the error you are seeing. That's always preferable to an image (even when the image is readable).

Thanks, Martin. The wiki is used by all versions of Flowcode so the v10 info can stay.

In fact, the text refers to converting the v10 examples to v11, so they should definitely remain there.

Thanks, Martin. Looks fine to me, but I'll check with Ben first.

Thanks, Martin. That looks like a nice addition to that component.

It might be worth posting the source to the component too so that users can see what you have added or changed, and can also see what version of the component you have modified. This is especially important if the official component ...

Thanks, Martin. I've sorted that for the next release.

Thanks Martin, and Martin. Interesting examples.

You probably know this already, but or the @medelec35 project, you can use direct string comparisons in v11 - e.g. a decision with the following expression:

.MacroTable[.Index] == "macro5"


This makes it a bit easier to read that the current ...

Thanks, Martin.

I can see the issue and it seems to be because an error is returned when trying to open the file within the component. BTW I debugged this by essentially recreating the CSV_ReadWrite1 calls as their base FileSCADA1 calls and monitoring the return values. In the Ev_Property, the ...

Sorry - I see that there's a succinct project in the linked post. I'll have a look. Although you seem to have solved the issue anyway and so hopefully you're good to continue?


Could you confirm this is indeed how events are implemented under the hood? If so, it'd be worth stating plainly in the ...