Migrating to HDevelopEVO From HDevelop

HDevelopEVO behaves differently than HDevelop in several aspects. In particular, HDevelopEVO differs regarding the following:

• Changed file format (.hscript instead of .hdev)
• Changed handling of procedures
• Changed behavior of dev_* operators

More Info

For a quick overview, see also Introducing HDevelopEVO.

Behavior of “dev” Operators

“dev_*” operators are now executed via the engine directly, and visualization in the graphics windows of the IDE via dev_* operators, such as dev_display or dev_disp_text, is not possible. Instead, you can display the visualization in a native HALCON graphics window, which can be opened using dev_open_window.

Example

To use the dev_display operator, for example, you first need to open a native HALCON graphics window with dev_open_window.

Re-Using HDevelop Programs in HDevelopEVO

Unlike the “old” XML-based .hdev files, the new .hscript format is simple plain text. Apart from that, existing programs can be used as they are shown in the HDevelop editor in HDevelopEVO as well.

To migrate an existing HDevelop program, you can use the following workaround:

1. In HDevelop, open the File > Export Program dialog.
2. Export the program as a Text File with default settings.
3. In HDevelopEVO, open the exported file as HSCRIPT.

You probably have to clean up the file to make it executable. In particular:

• The only allowed comment sign is “*” (asterisk). Change lines starting with “#” accordingly.
• If the program contains procedures, adapt them to the new syntax.
  For more information, see Working With Procedures.
• If the program contains dev_* operators like dev_open_window, adapt the code as described in the previous section.