On Thu, Apr 27, 2017, 8:31 PM Padraig Ó Cuínn <[email protected]>
wrote:

> Here it is what I have so far sorry for the delay.
>

Thank you for providing the start of the example code.

My main goal is to hook the Trees up for inheritance by classes.
> If you move one from the other it loses inheritance and gains from the
> attached one.
>

I don't follow what this means. Move one from which to where? Are you
talking about dropping items within the same tree on the left? Or dropping
them into the list or table on the right? I don't follow the reference to
inheritance here. I think you might be making rigging references which I am
not following. Someone else with relevant experience may understand this
goal better than me.

I don't want the topItem to be able to be dropped or dragged on certain
> items (i.e build) but on the others I want it so the topItem becomes
> rootNode in the configuration.
>

I get the desire to make some items draggable or able to receive drops.
Which configuration? Is the drop supposed to happen within the tree? I see
you have set drag drop to internal move. So I am not getting the relevance
of the right side stack.


> right now I want to hook up the stack (I just threw in the list widget and
> table widget for visual).
>

Hook up the stack to do what? What should happen here? I see your initial
tree items and list items and apparently a table which is not useful other
than  for visuals?

Sorry for seeming so dense. I just am not making the connections about the
behaviours you want. Items are supposed to get dragged around into some
configuration in either the tree or the list. And the stack index is
supposed to be changed by some criteria of the selection or the drops. That
is all I think I understand so far.


> https://pastebin.com/UQHrUcxt
>

Is there any more to this example that you haven't included, such as your
non-working attempt to implement the behavior you have described? So far
this is just a set of layouts, which I think I already understood from the
previous mails. It would be much easier if I saw what you were trying to do
with this currently passive layout.


>
> Thank you for your time and patience lads.
>
> On Tuesday, 25 April 2017 00:48:01 UTC+1, Padraig Ó Cuínn wrote:
>>
>> not a problem ill send you the tried code in the morning.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Python Programming for Autodesk Maya" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/python_inside_maya/07bc5b11-2f8e-44e8-9f72-69d5293a0d8c%40googlegroups.com
> <https://groups.google.com/d/msgid/python_inside_maya/07bc5b11-2f8e-44e8-9f72-69d5293a0d8c%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA1qtqr6N%2BZgTNLen-j_B7VSS9Uvd__Ch7Ue7CYzS-1ZEQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to