Looking at the code, the delay functions accept a 16-bit unsigned integer, so you are correct. Although you may want to check when using large values for us delays as opposed to the equivalent ms delay. In practice, a 5000us delay may give a different result to a 5ms delay, especially on slower devi...

To activate Flowcode versions v6 to v8, you should refer to the instructions in this FAQ:

https://www.flowcode.co.uk/faqs/offline ... -to-v8.php

The short answer is FCL_MYVAR. The suffix for globals is "FCV_" and the suffix for locals is "FCL_". In the C-code icons (which includes any other icons that have been customised), you can drag variables from the lists on the right onto the C code. When dropped, they will be adde...

Thanks. I have moved this to the "bug reports" page and we will investigate and hopefully fix this soon.

When robbing, bodging and checking against with C code examples from Microchip application notes, I see they use an easier to read method. PIR1bits.CCP1IF = 0; // Clear CCP1 interrupt flag PIE1bits.CCP1IE = 1; // Enable the CCP1 int Can this method be used without issue in Flowcode C code component...

Sorry. It looks like we have overlooked this. We'll investigate and report back asap.

In the meantime, you can revert to an earlier working version of the component using the library updates panel.

Unfortunately there is no way to currently organise the macros in that dropdown menu. I will investigate to see what can be done.

Thanks, Alan. That other workaround should help others who face the same issue.

Try just using WriteData without the square brackets.

Hi Alan, Thanks for letting us know. If this happens, then I have a workaround that can be used to retain this. If you open a C code icon and discover there is no code there, click cancel and then view the macro as C code. Then edit the code of the C-code icon directly in the C-code view (by double-...