Machine controller - export_hundegger_with_file_path

[djdbarroso]

Hello all!
I've just recently upgraded Cadwork to V2025 and have noticed a change in the function export_hundegger_with_file_path, which is leading to problems in an API we have been using.
In the previous version (V30 SP2024) we could define freely the name of the file, but now the function only creates a folder with the name we set and saves the machine file inside, with the name of the Cadwork file... Is this supposed to be like this?
If so, any idea on how the code can get the name of the file, to be able to parse it?

Thanks in advance for any help!

[djdbarroso]

Have solved the problem by getting the name of the file using the get_3d_file_name() function and manipulating the string, but can someone confirm that export_hundegger_with_file_path has changed with V2025?

Thanks!

[Brunner246]

Hi @djdbarroso

There was an issue which has been fixed. This fix will be available within the next update from cadwork 2025.

Expected output after that update will be

from pathlib import Path, WindowsPath

import attribute_controller as ac
import cadwork
import element_controller
import machine_controller as mc

robot_drive = cadwork.hundegger_machine_type.robot_drive.value

mc.calculate_hundegger_machine_data(element_controller.get_visible_identifiable_element_ids(),
                                    robot_drive)

mc.export_hundegger_with_file_path(robot_drive, str(WindowsPath(Path().home() / "Downloads" / "machine" / "data")))
mc.export_hundegger_with_file_path_silent(robot_drive, str(WindowsPath(Path().home() / "Downloads" / "silent_export")))

# results are
## C:\Users\JohnDoe\Downloads\machine\data.bvx
## C:\Users\JohnDoe\Downloads\silent_export.bvx