HDevelop User's Manual

More documents

Recommendations

Info

52 CHAPTER 2. GRAPHICAL USER INTERFACE method. Here you have to click into a text field with the left mouse button. This activates the field and prepares it for user input. Simultaneously, the writing position is marked by a vertical bar. Now you may input numbers, strings, expressions, or variables. There are some editing functions to help you doing input: ×Ô deletes the left and ÐØ deletes the right character. You may also select (invert) a sequence of characters in the text field using the mouse. If there is a succeeding input, the marked region is going to be deleted first and afterwards the characters are going to be written in the text field. You can find additional editing functions on page 117. Combo box selection: Using this input method, you can obtain rapid settings of variables and constants. To do so, you have to click the button on the text field’s right side. A combo box is opened, in which you may select an item. Thus you are able to choose a certain variable or value without risking erroneous typing. This item is transferred to the operator name field. Previous entries are deleted. Afterwards the combo box is closed. If there are no variables or appropriate values, the combo box remains closed. 2.5.3 Control Buttons Below the parameter edit fields you find four buttons that comprise the following functions (see figure 2.35): Figure 2.35: Operator window with operator ×ÐØ ×Ô. ÇÃ By clicking ÇÃ you execute the operator with the specified parameters. In doing so, the execution mode is dependent on the position of the È: IftheÈ is placed above the insertion position, the system computes the program from the È until the insertion position first. Then the operator that has been edited in the operator window is executed. The reason for this is that the parameter values that are used as input values for the new <strong>HDevelop</strong> / 2000-11-16
2.6. VARIABLE WINDOW 53 operator have to be calculated. In case the È is placed at or after the insertion position, this operator is executed only. Before execution the operator is entered into the program window. The È and the insertion cursor are positioned after the new operator. The computed output parameter values are displayed in the variable window. Iconic variables are shown in the current graphics window, if you haven’t suppressed this option (see page 24). Afterwards the operator window is cleared. If you did not specify all parameters or if you used wrong values, an error dialog is raised and execution is canceled. In this case, the operator window remains open to support appropriate changes. ÒØÖ By clicking the button ÒØÖ the program line is only transferred in the program window. There is no operator execution, i.e., the position of the È is not changed. The insertion cursor is positioned after the new operator. ÔÔÐÝ If you click ÔÔÐÝ the operator is executed with the specified parameters, but not entered into or changed in the program. This enables you to determine the optimum parameters of an operator rapidly since the operator dialog remains open, and hence you can change parameters quickly. Unlike the button ÇÃ, only the single line you edit or enter is executed, no matter where the È is located. Thus, you have to ensure that all the input variables contain maningful values. By pressing ÔÔÐÝ, the corresponding output variables are changed or created, if necessary, to allow you to inspect their values. If you decide to not enter the line into the program, some unused variables may thus be created. You can easily remove them by selecting Ð º ÐÒÙÔ. ÒÐ Clicking ÒÐ clears the contents of the operator window. Thus, there are neither changes in the program nor in any variables. ÀÐÔ Clicking ÀÐÔ invokes an appropriate help text for the selected operator. For this the system activates an HTML-browser (see chapter 6.3). 2.6 Variable Window There are two kinds of variables in HALCON. This corresponds to the two parameter types of HALCON: iconic objects (images, regions, and XLDs) and control data (numbers, strings). In HALCON the corresponding variables are called iconic and control variables. These variables may possess a value or be undefined. An undefined variable is created, for example, when loading a program or after inserting an operator with a new variable that is not executed immediately into a program. You may access these undefined variables by writing them only. If you try to read such a variable, a runtime error occurs. If a variable obtains a value, the variable type is specified more precisely. A control variable that contains, for example, an integer is of type ÒØÖ. This type might change after specification of new values for this variable to ÖÐ or a tuple of ÒØÖ. But it always remains a control variable. The more refined type is bound to the value and not to the variable. Similarly, this is the case for iconic variables, which may contain regions, images, or XLDs. You may assign new values as often as you want to. But you cannot change them to the state before the first assignment (see above). 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: 2.5. OPERATOR WINDOW 51 Please refe
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 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

Create successful ePaper yourself

Delete template?

Save as template?