Flowcode Support Board

Hello everyone,

I have a problem where a previously working project is malfunctioning after updating and recompiling the library.
To avoid such problems, I have a suggestion for improving Flowcode.

• The project file can save the name and version of the Component Libraries used during the last compilation, as well as the compiler type and version.
  You can check this in the "Updates" window, in a new "Used Version" column.

• If I open an old project and the "Used Version" and "Current Version" values ​​differ for any of the libraries used, a warning window appears.

• It would also be nice if updating the component library did not overwrite the previous library files. (If this could be resolved, when opening an old project, it would open with the library versions originally used.) This way, the Flowcode user could also select library items from previous versions as "Current Version".

I believe that this improvement can also make the work of Flowcode support staff easier and shorten debugging time by describing the programming environment more accurately.
If someone has already asked for this or has a solution, please link it here.

Regards,
Sasi

Hi,
I faced about version problem many times too, and not later than last week I got this problem , opening a 6 month project to make a firmware modification l and project not working. I have already warning about this
1- it would be very good to be able to open the project in the exact same session as it was created.
2- And get a choice to open it the new version and like said Sasi to have the list of components version who are not same as before .
Include files, FC, components , etc.. all who can affect the firmware .
For professional it's very important to know .
Thx

Thx

Thanks for the excellent suggestions.

Component version info for previous builds can be found in the generated C code file, but that could be overwritten easily and does not cover versions of other library files like the CAL and the FCD chip definitions.

I will see what we can do to improve this.

I concur, being able to open and compile a flowchart with ‘locked’ component versions would be an excellent improvement. Of course allowing the user to update versions. Currently development can very much be hit and miss because of changes to components.

Ideally a user would be to be able to version the flowchart and all components (and CALs) it depends on.

I think it would be a step forward if the Flowcode developers declared which compiler version they recommend (practically this should be packaged in the installation kit), and tested the improved component libraries with this version before release.

The compilers are packaged and made available by Matrix for most targets so the versions are known.

You're right.
I wanted to be brief and didn't clearly state what I wanted to suggest.
Currently, everyone uses the compiler version they consider the most reliable.
In my experience, different versions are not necessarily compatible with each other in terms of the functionality of the generated hex file.
Therefore, I tried to imply that until the topic starter development is completed, we would use the version recommended by the developers,
since component development and bug fixing tasks are also tested with this version. (I'm just assuming that.)
If we send a problematic project to Flowcode support, the MatrixTSL specialists would conduct the investigation with this version.
That's roughly what I was thinking.