|
Previous Top Next |
This utility template writes information about each procedure to a <appname>.appi file. The resulting file is a comma separated file with information about each procedure, such as Line number, application type (EXE, DLL, LIB), dependency (true if global data is external, false if global data is not external), procedure name, procedure prototype, procedure template, module name and if the procedure is external or exported. This is invaluable when working with multi-dll systems when creating external procedures as it shows the prototype etc. It is also very handy when doing code searches as it shows the module name so it's easy to open the module even if the Clarion IDE is not open. There are no prompts on this template.
For our PowerToolbar multi-dll test app that we compile before each release, this template creates the following data into the PowerToolbarDemo.appi file:
"Line","Type","Dependent","Procedure","Prototype","Template","Module","Export","External"
"1","EXE","1","BrowseDemo","","Browse","Power004.clw","0","0"
"2","EXE","1","BrowseDemoForm","","Form","Power006.clw","0","0"
"3","EXE","1","ColorDemo","","Window","Power011.clw","0","0"
"4","EXE","1","ControlTypesDemo","","Window","Power003.clw","0","0"
"5","EXE","1","GetProgramID","(String pID),String","Source","Power015.clw","0","0"
"6","EXE","1","IExplorerDemo","","Window","Power009.clw","0","0"
"7","EXE","1","IconsDemo","","Window","Power007.clw","0","0"
"8","EXE","1","Main","","Frame","Power001.clw","0","0"
"9","EXE","1","MenuTest","","Window","Power014.clw","0","0"
"10","EXE","1","NotepadDemo","","Window","Power010.clw","0","0"
"11","EXE","1","OutlookDemo","","Window","Power008.clw","0","0"
"12","EXE","1","StylesDemo","","Window","Power002.clw","0","0"
"13","EXE","1","TabbedViewDemo","","Window","Power013.clw","0","0"
"14","EXE","1","Welcome","","Window","Power012.clw","0","0"