Solved Limit the destination of UserArea.HandleMouseDrag()

Hi,

I am drawing an object as a node in UserArea and I want to drag that object only to the InExclude list (Attribute Manager).
The problem is that when I use HandleMouseDrag(), I can also drag to the Object Manager and that object will be duplicated unintentionally.
So I need to know how to restrict dragging to the object manager and only allow dragging to the Attribute Manager.

Any help would be appreciated.

Hello @kng_ito ,

Thank you for reaching out to us. As announced here, Maxon is currently conducting a company meeting. Please understand that our capability to answer questions is therefore limited at the moment.

You should share here code, as we are otherwise only guessing what you are doing. I am not quite sure what is meant with 'I am drawing an object as a node in UserArea', but I assume you are implementing some kind of UserArea and want to start a DRAGTYPE_ATOMARRAY event for one or many BaseList2D associated with your UserArea.

It is not possible to 'forbid' entities to consume a drag event when they implement that event. E.g., you cannot prevent the Object Manager from accepting a BaseObject being dragged into it.

Cheers,
Ferdinand

Hello @kng_ito ,

Thank you for reaching out to us. As announced here, Maxon is currently conducting a company meeting. Please understand that our capability to answer questions is therefore limited at the moment.

You should share here code, as we are otherwise only guessing what you are doing. I am not quite sure what is meant with 'I am drawing an object as a node in UserArea', but I assume you are implementing some kind of UserArea and want to start a DRAGTYPE_ATOMARRAY event for one or many BaseList2D associated with your UserArea.

It is not possible to 'forbid' entities to consume a drag event when they implement that event. E.g., you cannot prevent the Object Manager from accepting a BaseObject being dragged into it.

Cheers,
Ferdinand

Hello @kng_ito,

without further questions or postings, we will consider this topic as solved by Monday 05/06/2023 and flag it accordingly.

Thank you for your understanding,
Maxime.

Hi @m_adam,

Sorry for the delay in responding.
Yes, the problem has been resolved.