HDevelop User's Manual

More documents

Recommendations

Info

54 CHAPTER 2. GRAPHICAL USER INTERFACE Creation of a new variable happens in the operator dialog area during specification of operator parameters. Here every sequence of characters without single quotation marks is interpreted as a variable name. If this name did not exist before, the variable is created in the operator dialog area by pressing ÇÃ or ÒØÖ. The variable type is specified through the type of the parameter where it was used for the first time: Variables that correspond to an iconic object parameter create an iconic variable; variables for a control parameter create a control variable. Every time an operator is excecuted the results are stored in variables connected to its output parameters. This is done by first deleting the contents of the variable and then assigning the new value to it. The variable window is a kind of watch window used in window-oriented debuggers. Inside this window you are able to keep track of variable values. Corresponding to the two variable types, there are two areas in the variable window. One for iconic data (above) and the other for control data (below) (see figure 2.36). Figure 2.36: Variable window for both iconic and control data. All computed variables are displayed showing their iconic or control values (see page 16). In case of a tuple result which is too long, the tuple presentation is shortened, indicated by three dots. 2.6.1 Area for Iconic Data Here you can see iconic variables. They are represented by icons, which contain a gray image, a region or an XLD, depending on the current value. The icons are created depending on the type of data according the following rules: ¯ In the case of images the icon contains a zoomed version of it filling the icon completely. Due to the zooming onto the square shape of the icon the aspect ratio of the small image might be wrong. If there is more than one image in the variable, only the first image is used for the icon. Similarily for multi channel images only the first channel is used. ¯ Regions are displayed by first calculating the smallest surrounding rectangle and then zooming it so that it fills the icon using a border of one pixel. In contrast to images, the <strong>HDevelop</strong> / 2000-11-16
2.6. VARIABLE WINDOW 55 aspect ratio is always correct. This can lead to black bars at the borders. The color used to draw the region is always white without further modifications (except zooming). ¯ XLD data is displayed using the coordinate system of the largest image used so far. The color used for XLD objects is white on black background. Due to the different ways of displaying objects you have to be aware that the coordinates cannot be compared. The variable name is positioned below each icon. They are displayed in the variable window in the order of creation from left to right. If there is not enough space, a horizontal scrollbar is created, which you can use to scroll the icons. Clicking on an icon with the mouse will select this icon. This is indicated by the black background for the icon name. For an activated icon all operators that use the corresponding variable are marked in the program area with a black rectangle on the left. Double-clicking with the left mouse button on an icon displays the data in the active graphics window. If you use images of different sizes in a program, the system uses the following output strategy for an automatic adaption of the zooming: Every window keeps track of the size of the most recently displayed image. If you display an image with a different size, the system modifies the graphics window coordinate system in a way that the image is visible completely in the graphics window. If a partial zooming has been activated before (see chapter 2.7), it is going to be suppressed. Normally, regions, images, and XLDs are represented in variable icons. Besides this there are three exceptions which are shown by special icons: ¯ Empty variables are displayed as a question mark () icon. You may to write but not read them, because they do not have any values. ¯ Brackets (℄) are used if a variable is instantiated but does not contain an iconic object (empty tuple). This may be the case using operators like ×ÐØ ×Ô with “wrong” specified thresholds or using operator ÑÔØÝ Ó. Such a value might be reasonable if you want to collect iconic objects in a variable gradually in a loop (ÓÒØ Ó). Here, an empty tuple is used as starting value for the loop. ¯ A last exception is an empty region. Thisisone region that does not contain any pixels (points), i.e., the area (number of points) is 0. You must not confuse this case with the empty tuple, because there the area is not defined. The empty region is symbolized by an empty set icon (). 2.6.2 Area for Control Data To the right of the variable name you find their values in the default representation 6 . If you specify more than one value for one variable (tuple), they are separated by commas and enclosed by brackets. If the number of values exceeds an upper limit, the output is clipped. This is indicated by three dots at the end of the tuple. For empty variables, their name and a are shown in the variable field. An empty tuple is represented by ℄. Both exceptions use the same symbols as the corresponding cases for the iconic variables. 6 You have to keep in mind that a floating point number without significant fractional part is represented as an integer (e.g., 1.0 is represented as ½). 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: 2.6. VARIABLE WINDOW 53 operator ha
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

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

Delete template?

Save as template?