![]() ![]() To explicitly release the resources before the instance gets out of scope, you can call the method Clear() of the instance. Thus, there is no need to call the operator ClearObj in HALCON/C++ what is more, if you do use it HALCON will complain about already released memory. Furthermore, when constructing instances anew, e.g., by calling CreateBarCodeModel via an already initialized instance as mentioned in section 5.2.3 on page 48, the already allocated memory is automatically released before reusing the instance. Right now try to comment ClearObj statement in the end of the code.Īll of HALCON’s classes, i.e., not only HImage, HRegion, HTuple, HFramegrabber etc., but also the class HObject used when calling operators in the procedural approach, release their allocated resources automatically in their destructor (see also section 5.2.4 on page 49). In this review, we examine the next generation. ![]() ![]() You can read more about the features below. Unfortunately I don't have PC with LabVIEW, Halcon and Visual Studio at the moment, but I could check your code later (somewhere in a week or so). Welcome to MVTec on Campus for Lecturers Here you can download and activate your MVTec HALCON Progress Student Edition, as well as manage your tickets and.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |