Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DropElementWdg Issue - Tactic 4.9 #1763

Open
piplinecamel opened this issue May 10, 2023 · 1 comment
Open

DropElementWdg Issue - Tactic 4.9 #1763

piplinecamel opened this issue May 10, 2023 · 1 comment

Comments

@piplinecamel
Copy link

piplinecamel commented May 10, 2023

Hello,

the DropElementWdg does not work for us in Tactic 4.9.
If we have the Accepted Drop Type: restriction on, the element can not be dropped into the DropElementWdg column. The issue says that the asset type is not correct. But the element is part of the allowed Drop Type. 
When we don't have the restriction on, every element can be inserted, but nothing can be saved. The filled column will be empty after saving. 

We updated our project recently from 4.4 to 4.9. The DropElementWdg is used for a planer in a vfx template style project and worked in 4.4 fine. 
The view shows two sides, with two sTpyes. Both sTypes are also connected with an container vfx. Both base sTypes include the assets they should, and the container can be filled by using the csv import.

The XML code of the asset drop column looks like this:

<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.

Did anyone know if this Widget doesn't work anymore or if we missed something.
The code for drop_element_wdg is also there src/tactic/ui/table/drop_element_wdg.py

Thank you very much in advance.

@remkonoteboom
Copy link
Contributor

Really sorry, this has been a really busy week. We'll get somebody to take a look at this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants