HDevelop User's Manual

More documents

Recommendations

Info

88 CHAPTER 4. CODE GENERATION 4.2.3.1 Duplicate Parameters Due to the parameter handling of Visual Basic / COM it is not possible to use the same variable more than once in one call. Thus, for input and output parameters different variables have to be used. Also it is not possible to use the same variable twice for input or output. Examples for code which is not allowed are: ÑÒÑ´ÁÑ¸ÁÑ¸¿¸¿µ Ñ´ÁÑ¸ÁÑ¸¸½¸¼µ You have to introduce additional variables. 4.2.3.2 Reserved Words In contrast to C, C++, or HDevelop, Visual Basic has many reserved words. Thus, the export adds the prefix ÀÈ to all variables to avoid collisions with these reserved words. 4.2.3.3 Exception Handling In HDevelop, every exception normally causes the program to stop and report an error message in a dialog window. This might not be useful in Visual Basic. The standard way to handle this in Visual Basic is by using the ÇÒ ÖÖÓÖ ÓØÓ command. This allows to access the reason for the exception and to continue accordingly. Thus, for HDevelop programs containing error handling (Ú ×Ø ÖÖÓÖ ÚÖ) the corresponding code is automatically included. Please note, that a call of ´Ú µ×Ø ´Ú ÖÖÓÖµ has no influence on the operator call. The exception will always be raised. This is also true for messages like À ÅËË ÁÄ which are not handled as exceptions in C++ e.g.. When handling exceptions you also have to be aware that the COM interface always resets the output parameters at the beginning of the operator execution. Thus, when the exception occures, output variables are set to ÆÓØÒ. Therefore, you cannot use the values of variables used as output parameters of the operator causing the exception. 4.2.3.4 Special Comments HDevelop comments containing the symbol as the first character are exported as Visual Basic statement. Thus the line ÐÐ Å×ÓÜ´ÈÖ×× ÙØØÓÒ ØÓ ÓÒØÒÙ¸Ú×¸ÈÖÓÖÑ ×ØÓÔ¸¸½¼¼¼µ in HDevelop will result in ÐÐ Å×ÓÜ´ÈÖ×× ÙØØÓÒ ØÓ ÓÒØÒÙ¸Ú×¸ÈÖÓÖÑ ×ØÓÔ¸¸½¼¼¼µ in Visual Basic. This feature can be used to integrate Visual Basic code into an HDevelop program. HDevelop / 2000-11-16
4.3. CODE GENERATION FOR C 89 4.3 Code Generation for C This section describes how to create a HALCON application in C, starting from a program developed in HDevelop. 4.3.1 Basic Steps 4.3.1.1 Program Export The first step is to export the program using the menu Ð º ËÚ ×. Here, select the language (C) and save it to file. In UNIX you specify the language by giving the file the extension “º”. A file will be created that contains the HDevelop program as C source code in a procedure ØÓÒ´µ. This procedure is called in function ÑÒ´µ. Besides the program code, the file contains all necessary ÒÐÙ instructions. All variables (iconic as well as control) are declared locally in the procedure ØÓÒ´µ. Iconic variables belong to the class ÀÓØ and all other variables belong to ÀØÙÔÐ. Please note, that in the current version the generated C code is not optimized for readability, yet. 4.3.1.2 Compiling and Linking in Windows NT Environments The next step is to compile and link this new program. In the Windows NT environment, Visual C++ is used for the compiling and linking. Example projects can be found in the directory ±ÀÄÇÆÊÇÇÌ±ÒÜÑÔÐ×ÒÒ¹ÒØ. If you want to use Parallel HALCON, you have to include the libraries ÔÖÐÓÒºÐ»ºÐÐ and ÔÖÐÓÒºÐ»ºÐÐ instead of ÐÓÒºÐ»ºÐÐ and ÐÓÒºÐ»ºÐÐ in your project (see the HALCON/C++ User’s Manual for more details). 4.3.1.3 Compiling and Linking in UNIX Environments To compile and link the new program (called e.g. Ø×Øº) in the case of UNIX, you can use the example ÑÐ which can be found in the directory °ÀÄÇÆÊÇÇÌ»ÜÑÔÐ×» by calling Ñ ÌËÌÈÊÇØ×Ø Alternatively, you can set the variable ÌËÌ ÈÊÇ in ÑÐ to Ø×Ø and then just type Ñ. You can link the program to the Parallel HALCON libraries by calling Ñ ÔÖÐÐÐ ÌËÌÈÊÇØ×Ø or just type Ñ ÔÖÐÐÐ if you set the variable ÌËÌ ÈÊÇ as described above. For more details see the HALCON/C User’s Manual. HALCON 6.0
Page 1 and 2:
HALCON Version 6.0 MVTec Software G
Page 3 and 4:
About This Manual This manual is a
Page 5 and 6:
Contents 1 Introducing HDevelop 1 1
Page 7 and 8:
Contents iii comment . . . . . . .
Page 9 and 10:
Chapter 1 Introducing HDevelop In f
Page 11 and 12:
1.2. EXAMPLE SESSION 3 Figure 1.1:
Page 13 and 14:
1.2. EXAMPLE SESSION 5 Figure 1.2:
Page 15 and 16:
1.3. ADDITIONAL SOURCES OF INFORMAT
Page 17 and 18:
Chapter 2 Graphical User Interface
Page 19 and 20:
2.3. MAIN WINDOW 11 Figure 2.1: The
Page 21 and 22:
2.3. MAIN WINDOW 13 A security chec
Page 23 and 24:
2.3. MAIN WINDOW 15 a directory whe
Page 25 and 26:
2.3. MAIN WINDOW 17 Figure 2.7: The
Page 27 and 28:
2.3. MAIN WINDOW 19 and not HDevelo
Page 29 and 30:
2.3. MAIN WINDOW 21 Figure 2.10: Ma
Page 31 and 32:
2.3. MAIN WINDOW 23 2.3.2.4 The Men
Page 33 and 34:
2.3. MAIN WINDOW 25 Figure 2.13: On
Page 35 and 36:
2.3. MAIN WINDOW 27 in a graphics w
Page 37 and 38:
2.3. MAIN WINDOW 29 Figure 2.16: On
Page 39 and 40:
2.3. MAIN WINDOW 31 Figure 2.17: Co
Page 41 and 42:
2.3. MAIN WINDOW 33 Figure 2.18: Se
Page 43 and 44:
2.3. MAIN WINDOW 35 Figure 2.20: Se
Page 45 and 46: 2.3. MAIN WINDOW 37 Figure 2.23: Ex
Page 47 and 48: 2.3. MAIN WINDOW 39 output paramete
Page 49 and 50: 2.3. MAIN WINDOW 41 is registered i
Page 51 and 52: 2.3. MAIN WINDOW 43 ËÙ×ØÓÒ×
Page 53 and 54: 2.3. MAIN WINDOW 45 ÏÒÓÛ º ×
Page 55 and 56: 2.3. MAIN WINDOW 47 Figure 2.31: Th
Page 57 and 58: 2.5. OPERATOR WINDOW 49 The program
Page 59 and 60: 2.5. OPERATOR WINDOW 51 Please refe
Page 61 and 62: 2.6. VARIABLE WINDOW 53 operator ha
Page 63 and 64: 2.6. VARIABLE WINDOW 55 aspect rati
Page 65 and 66: 2.7. GRAPHICS WINDOW 57 Figure 2.38
Page 67 and 68: Chapter 3 Language The following ch
Page 69 and 70: 3.2. CONTROL TYPES AND CONSTANTS 61
Page 71 and 72: 3.4. OPERATIONS ON ICONIC OBJECTS 6
Page 73 and 74: 3.5. EXPRESSIONS FOR INPUT CONTROL
Page 85 and 86: 3.6. RESERVED WORDS 77 ÓÖ, ÜÓÖ
Page 87 and 88: 3.8. LIMITATIONS 79 In the followin
Page 89 and 90: Chapter 4 Code Generation The idea
Page 91 and 92: 4.1. CODE GENERATION FOR C++ 83 Ì
Page 93 and 94: 4.1. CODE GENERATION FOR C++ 85 tha
Page 95: 4.2. CODE GENERATION FOR VISUAL BAS
Page 99 and 100: 4.4. GENERAL ASPECTS OF CODE GENERA
Page 101 and 102: Chapter 5 Program Examples This cha
Page 103 and 104: 5.2. CAPILLARY VESSEL 95 ÚÐÓ×Û
Page 105 and 106: 5.2. CAPILLARY VESSEL 97 Figure 5.3
Page 107 and 108: 5.3. PARTICLES 99 each. Now it is e
Page 109 and 110: 5.4. ANNUAL RINGS 101 ÚÐÖÛÒÓ
Page 111 and 112: 5.5. BONDING 103 Figure 5.9: Exampl
Page 113 and 114: 5.7. DEVICES 105 Figure 5.11: Calib
Page 115 and 116: 5.7. DEVICES 107 Figure 5.13: Resis
Page 117 and 118: 5.8. CELL WALLS 109 Figure 5.15: Mi
Page 119 and 120: 5.10. EXCEPTION HANDLING 111 Figure
Page 121 and 122: 5.11. ROAD SCENE 113 any case. All
Page 123 and 124: 5.11. ROAD SCENE 115 tures. Hence a
Page 125 and 126: Chapter 6 Miscellaneous This chapte
Page 127 and 128: 6.5. RESTRICTIONS 119 Figure 6.1: E
Page 129 and 130: 2 APPENDIX A. CONTROL ÌÙÔÐ½
Page 131 and 132: 4 APPENDIX A. CONTROL Attention For
Page 133 and 134: 6 APPENDIX A. CONTROL Result retur
Page 135 and 136: 8 APPENDIX A. CONTROL ÚÙÔØÛÒ
Page 137 and 138: 10 APPENDIX A. CONTROL HDevelop / 2
Page 139 and 140: 12 APPENDIX B. DEVELOP Attention If
Page 141 and 142: 14 APPENDIX B. DEVELOP Ú ÓÔÒ Û
Page 143 and 144: 16 APPENDIX B. DEVELOP Ú Ò×ÔØ
Page 145 and 146: 18 APPENDIX B. DEVELOP Parallelizat
Page 147 and 148:
20 APPENDIX B. DEVELOP º ÀØ (inp
Page 149 and 150:
22 APPENDIX B. DEVELOP ’black’
Page 151 and 152:
24 APPENDIX B. DEVELOP Parameter º
Page 153 and 154:
26 APPENDIX B. DEVELOP Parameter º
Page 155 and 156:
28 APPENDIX B. DEVELOP If ÊÓÛ½
Page 157 and 158:
30 APPENDIX B. DEVELOP Ú ×Ø ÛÒ
Page 159 and 160:
32 APPENDIX B. DEVELOP Possible Suc
Page 161 and 162:
34 APPENDIX B. DEVELOP See Also Ú
Page 163 and 164:
36 APPENDIX B. DEVELOP HDevelop / 2
Page 165 and 166:
38 APPENDIX C. GLOSSARY Operator wi
Page 167 and 168:
40 Index Ú ×Ø ÔÖØ, 27, 39 Ú
Page 169 and 170:
42 Index Operator Data base, 37 Nam
Page 171:
44 Index HDevelop / 2000-11-16
show all

HDevelop User's Manual

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?