There is a brief description in the system reference guide, also in component author guide,
Creator, help menu to access both.
I looked at it. IMHO it won't help much until cypress starts adding the hooks to the component library. But will their idea of where to add match my/our desires.
It will make it a little easier to take a library component, copy it, mod it for MY wanted hooks, then use it. It will make it easier to port to new releases.
It is more of a standard coding practice than a 'feature' like the parsing engine of regions.
All my opinion,
@danaaknight thanks for the help, i didn't see that documents before , just the Creator Help.
@psoc-ed i think i see the purpose now, thanks for the opinion.
Thanks for the info.
I can see how the location of the callback would be fixed in component API code that *I* create, however, if I add a callback to a Cypress component, for instance, will subsequent builds leave it alone, or do I need to hide it in a "Merge Region?"
Did a easy program and the code on the callback function is kept after newer builds, "merge region" is there just for backward compatibility.
same thing which carlos mentioned, i used the same thing in my code can i implemnt those macros for my other functions also in creator 3.3.
what my question is i want to add different files for different task like for reading and computing tempereature and then displaying . i am not getting how to include those different files in main.c and how to call those functions in main.c its completely like archieving and tio bring my code to standard one plz anybody help me
different files for different task This is usually solved using a .h file (only Declarations, no variables except externals) and the corresponding .c file. The .h file is #included into main.c (and of course in the corresponding .c)