HALCON Extension Package Programmer's Manual

2.3. DESCRIBING THE PARAMETERS 272.3.1 NameÔÖÑØÖNameÒÔÙØÓظÓÙØÔÙØÓظÒÔÙØÓÒØÖÓиÓÙØÔÙØÓÒØÖÓÐThis defines the name and the class of a parameter. The parameters must be described in thesame order as in their definition within the header of the operator description.2.3.2 default typeÙÐØØÝÔÒØÖ¸Öи×ØÖÒOnly for control parameters! This slot specifies, what C-type to use in general. It must haveexactly one of the three above values.2.3.3 sem type×ÑØÝÔclass[.spec]This slot determines the semantics and specifies the class of data passed as parameters, whenusing an object-oriented language. Names of classes within the -file are only symbolic. Themapping to the actual class names is is provided by the HALCON compiler ÓÑÔ. HDevelopalso uses the semantic types, e.g., in order to provide specific inspection routines (like for framegrabber handles). For complex classes it must be defined by .spec, which aspect of the classis represented by the parameter. By this, one can pass complex objects that are described byseveral parameters of the C-procedure as one logical parameter.The following semantic types (classes) are availabe at the moment:¯ Iconic data (object parameters):– ÓØ (any iconic object: images, regions, XLDs)– Ñ (images)– ÖÓÒ (regions)– ÜÐ (any XLDs: lines in eXtended Line Description)– ÜÐ ÓÒØ, ÜÐ ÔÓÐÝ, ÜÐ ÔÖ, ÜÐ ÑÓ ÔÖ, ÜÐ ÜØ ÔÖ.¯ Elementary data (control parameters):– ÒÙÑÖ (unspecific)– ÒØÖ, ÖÐ, ×ØÖÒ– ÖÝÚÐ (gray value)– ÒÒÐ (channel number).¯ Handles (control parameters):– ÖÑ ÖÖHALCON 6.0