Hello Freemaster-Team,
Thanks for the great tool and the time it saved me during MCU development.
I have some feedback and some questions for the new revision:
Thank you in advance
Best regards
Sebastian
Solved! Go to Solution.
Hello Sebastian,
thank you for your cooperation on crash fixing. The fix will appear in the next version.
Please note that the Context Menu in the Project Tree already has a command to expand or collapse all child nodes. Try to do "Collapse" when the project root item is selected - it will walk through all top-level child items and will collapse them individually.
Regards,
Michal
Dear Sebastian,
thank you for your feedback and for the bug report.
To your points:
Thanks,
Michal
Hi Micha,
thank you very much for your response. Here some comments from my side:
Best regards
Sebastian
Hello Sebastian,
thank you for your cooperation on crash fixing. The fix will appear in the next version.
Please note that the Context Menu in the Project Tree already has a command to expand or collapse all child nodes. Try to do "Collapse" when the project root item is selected - it will walk through all top-level child items and will collapse them individually.
Regards,
Michal
Hello Michal,
The collapse command works like charm - and the bugfix as well!
Here I have some other improvment suggestions:
Is it possible to have a comment coloumn for the "variable watch" - sometimes it would just be nice to write some additional information for one variable.
We are often working with error flags in a bit field. Is it possible to have "bit field enum"? For every activated bit the output is build like 0b1000 0101 = "err1 err3 err8 ".
Is it possible to have 4 bits grouped if show as BIN is activated e.g. "0b0011 0110 1111 0011"
We have an array (uint16_t var_array[12]) and an index (uint8_t i) in the MCU code. Is it possible to show var_array[i] in the variable watch?
Best regards
Sebastian
Hello Sebastian,
thanks for your feedback. Here are some answers to your questions.
Good idea about the "comment column" and 4-bits grouping. Will address this in one of the next versions.
About the bit-field enums: I would rather recommend a workaround to create individual variables representing each bitfield and create a text-enumerations for them. In FreeMASTER 3.1 you can now share the single enumeration definition by multiple variables. This is a better / more universal solution in terms of bitfield modification etc.
Regards,
Michal