Skip to main content
Aug 3, 2025 4:53 AM UTC
Acknowledged

Enhancing Creo Toolkit APIs to Support Drag and Drop Event Handling.

Related products:Creo Parametric

1. Describe the Problem

Creo Toolkit/Pro Toolkit does not provide APIs to capture the drag and drop event of Creo design files into the Creo Parametric session.

  • Creo Toolkit currently does not expose APIs or event hooks that allow developers to monitor or intercept drag-and-drop activities in the UI.
  • The lack of drag/drop event handling creates a gap for advanced customization, particularly in workflows requiring file tracking, validation, or dynamic behavior based on the dropped content.
  • Article CS230497 confirms that Toolkit support for these events does not exist at this time.


2. Are you using a workaround?
No.

3. What is the use case for your organization?
The Creo Parametric CAD application currently offers built-in support for drag-and-drop functionality—allowing users to open design files directly by dragging them into the session’s view area. While this behavior is useful for end users, it presents a limitation for developers working with the Creo Toolkit who wish to implement custom logic tied to drag-and-drop events.

4. What impact does this problem currently have on your organization?
As part of a customization using the Creo Toolkit, I am looking for a Creo Toolkit API to intercept and handle the following aspects of drag-and-drop behavior within Creo Parametric: - capture the drag initiation: Detect when a file drag event begins and which file is being moved. - identify the target location: the target location can be model tree or view area where the file will be dropped. - Perform conditional logic: Based on file type or context, allow or restrict drops, trigger automated actions. - to perform specific validations: run validations before the file is opened in Creo.

1 reply

olivierlp
Community Manager
Aug 4, 2025 8:28 PM UTC
Status changed to: Acknowledged

Thank you @Sampath for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.

Olivier