Slicken up 'C' component macro editing
Posted: Fri Dec 26, 2014 9:59 pm
Hope you all had a good Xmas
My 2-bits...
When editing the 'C' component macro, I believe it would make perfect sense for Flowcode to facilitate selection of declared variables/C-styled functions/etc (just as with any other component macro or calculation), plus automating uppercase conversion and the required FCx_ prefix (or local variable prefixing) in front of the entry.
Furthermore, when hitting "OK" to confirm edits, perhaps the semicolon could be automatically appended to the end of each line if it doesn't exist - unless I've overlooked possible exceptions to regular line termination?
From personal experience this would save a lot of typing, typo's, and similar errors with large/multiple C code blocks, and reduced potential for resident faults only to be discovered at build/run time, though please don't ask what inspired these suggestions
All the best,
Brendan
My 2-bits...
When editing the 'C' component macro, I believe it would make perfect sense for Flowcode to facilitate selection of declared variables/C-styled functions/etc (just as with any other component macro or calculation), plus automating uppercase conversion and the required FCx_ prefix (or local variable prefixing) in front of the entry.
Furthermore, when hitting "OK" to confirm edits, perhaps the semicolon could be automatically appended to the end of each line if it doesn't exist - unless I've overlooked possible exceptions to regular line termination?
From personal experience this would save a lot of typing, typo's, and similar errors with large/multiple C code blocks, and reduced potential for resident faults only to be discovered at build/run time, though please don't ask what inspired these suggestions
All the best,
Brendan