HDevelop User's Manual

More documents

Recommendations

Info

14 CHAPTER 2. GRAPHICAL USER INTERFACE file type has no effect because only HDevelop programs with the extension ºÚ can be loaded. If you want to open your file with a write protection choose the checkbox at the bottom of this dialog window. To open your specified file, you press the ÇÔÒ button. This action deletes an already loaded HDevelop program and all created variables. The same actions as with Ð º ÆÛ are performed. Now you can see your new program in the program window. The file name is displayed in the title bar of the main window. All its (uninstantiated) variables are shown in the variable window. To indicate that they do not have any computed values, the system provides the iconic and control variables with a question mark. The program counter is placed on top of your program and you are ready to execute it. The visualization and options will be reset after loading (same as Ð º ÆÛ). If you want to cancel this task you have to press the corresponding button. By using one of these two buttons (ÇÔÒ or ÒÐ) the dialog window disappears. After you have loaded a program the corresponding file name will be appended at the end of the menu Ð (after the menu item ÉÙØ). This allows you to switch between recently loaded files quickly. The most recently loaded file is always listed first. Ð º ËÚ (keyboard shortcut ØÖÐ Ë) The menu item Ð º ËÚ saves the current program to a file. If no file name has been specified so far, the dialog corresponding to Ð º ËÚ ×ººº will be activated. Ð º ËÚ ×ººº The menu item Ð º ËÚ ×ººº saves the current program to a file. The type of file (HDevelop, text, Visual Basic, C, or C++) can be selected (see Figure 2.4). Figure 2.4: The dialog window to save a program to a file A dialog box (similar to the window described in menu item Ð º ÇÔÒººº) is opened in which you can specify the appropriate settings. You may specify a new file name and HDevelop / 2000-11-16
2.3. MAIN WINDOW 15 a directory where to locate this file. You may indicate whether the HDevelop program remains a HDevelop program or is transformed to a C, C++, Visual Basic, or an ASCII file. This is done by clicking the combo box of the text field called Ð× Ó ØÝÔ. In UNIX the selection of the file type has to be done by entering the corresponding file extension manually. For C++ code you have to add ºÔÔ to the file name, for C++ code º, and for ASCII ºØÜØ. The extension for Visual Basic is º×. Default type is the HDevelop type (extension ºÚ). The details of code generation are described in chapter 4. Similar to loading, the file name of the program you save is appended at the end of the menu Ð. Ð º Ê ÁÑ The menu Ð º Ê ÁÑ contains several directories from which images are usually loaded. The first entry of this menu always is the directory from which the most recent image was loaded. This is useful, when several images from a non-standard directory must be read. The remaining entries except the last one are the directories contained in the ±ÀÄÇÆÁÅË± environment variable. The final directory, denoted by º, isthecurrent working directory of the HDevelop program, which usually will be ±ÀÄÇÆÊÇÇÌ± on Windows NT systems, and the directory in which HDevelop was started on Unix systems. Figure 2.5: The menu item Ð º Ê ÁÑ. When any of the directories is selected, an image file selection box appears. Again, its 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: 2.3. MAIN WINDOW 13 A security chec
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 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
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 and 96:
4.2. CODE GENERATION FOR VISUAL BAS
Page 97 and 98:
4.3. CODE GENERATION FOR C 89 4.3 C
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?