03-23-2023, 09:11 PM
Hello,
for some reason the DropElementWdg in a shot planner view does not work for us with Tactic 4.9 - In a vfx template style project.
Issue: An asset can be dropped and will be registered as added, but after saving the changes, it will just disappear.
On top sometimes a message appears, that the drop only accepts drops from vfx/asset - the dropped elements are vfx/asset elements. Drop the asset again normally behaves like described above.
The XML code of the asset drop column looks like this:
The whole behavior looks similar to a bug from earlier Tactic versions, where saving the column definition could delete the action class section from the definition. But:
stays in the definition.
There is a many-to-many connection between shot and asset in place.
Does anybody have an idea why this is happening? Did I miss a change for this kind of action for Tactic 4.9?
Thank you in advance.
for some reason the DropElementWdg in a shot planner view does not work for us with Tactic 4.9 - In a vfx template style project.
Issue: An asset can be dropped and will be registered as added, but after saving the changes, it will just disappear.
On top sometimes a message appears, that the drop only accepts drops from vfx/asset - the dropped elements are vfx/asset elements. Drop the asset again normally behaves like described above.
The XML code of the asset drop column looks like this:
Code:
<element name="asset_drop" width="191px" edit="false">
<display class="tactic.ui.table.DropElementWdg">
<accepted_drop_type>vfx/asset</accepted_drop_type>
<instance_type>vfx/asset_in_shot</instance_type>
<display_expr>@GET(vfx/asset.name)</display_expr>
<css_background-color>#425952</css_background-color>
</display>
<action class="tactic.ui.table.DropElementAction">
<instance_type>vfx/asset_in_shot</instance_type>
</action>
</element>
The whole behavior looks similar to a bug from earlier Tactic versions, where saving the column definition could delete the action class section from the definition. But:
Code:
<action class="tactic.ui.table.DropElementAction">
<instance_type>vfx/asset_in_shot</instance_type>
</action>
stays in the definition.
There is a many-to-many connection between shot and asset in place.
Does anybody have an idea why this is happening? Did I miss a change for this kind of action for Tactic 4.9?
Thank you in advance.