Skip to content

Troubleshooting๐Ÿ”—

General information๐Ÿ”—

hinfo utility๐Ÿ”—

If you have trouble starting HDevelop or a HALCON application, you can run the hinfo utility from a command shell. This program will display various information about HALCON, including the values of environment variables relevant to HALCON, the version of HALCON, the license being used, etc. If no valid HALCON license can be found, hinfo will display the license and the error message explaining why the license cannot be used for any license it can find.

Log files๐Ÿ”—

Each time you run HDevelopEVO, a logfile is stored but only the last 10 session will be stored. To access your log files of HDevelopEVO, go to File > Open Log File and your stored log file(s) will be displayed. The exact folder location of your files depends on your operating system.


Terminating HALCON library๐Ÿ”—

Problem
In applications where DLLs are unloaded in a thread-exclusive context, for example, with FreeLibrary() under Windows, the HALCON library will not terminate properly if there are still active HALCON threads.
Example
A possible scenario in which the problem may occur is using HALCON/C++ to implement an ATL control.
Solution
Call the function FinalizeHALCONLibrary() before unloading the DLL. The application has to be linked against halcon.lib. Make sure that the call to FinalizeHALCONLibrary() does not occur from within any other DLLโ€™s DllMain function.
Note that once FinalizeHALCONLibrary() has been called, no further HALCON functions may be called.
Further, the HALCON library is not capable to free all resources properly during termination. This can result in memory leaks when loading and unloading the HALCON library repeatedly.

Executed program or procedure raises exception for display operators when not using implementation of display operators๐Ÿ”—

Problem
If you are not using an implementation of HDevelopโ€™s internal display operators (dev_*), calls to these operators in the executed HDevelop program or procedure are simply ignored. However, if the program or procedure contains other, โ€œexternalโ€ display operators like set_tposition or write_string, which need a window handle as input parameter, the program or procedure will raise an exception at this operator if the window handle has not been instantiated.
Solution
Typically, this problem will not arise when executing programs, because you will in most cases use an implementation of the display operators. When executing procedures, we recommend that you leave out the external display operators that use window handles. If this is not possible, you could place them in a separate procedure and use the implementation of display operators for just this procedure. Alternatively, initialize the window handle with a value like -1 and test it before executing the external display operators.

External procedures cannot call local procedures๐Ÿ”—

Problem
Local procedures can call external procedures but not the other way round.
Solution
This is the intended behaviour. If you want to call a procedure from another procedure, ensure that the called procedure is not local.