After almost a decade using Qt (I remember starting on mac os with an
article found on your blog Justin, about how to compile qt for maya/mac! ),
I am still annoyed by the same things: sometimes, a super common operation
(such as drag/drop) has to bee implemented manually, while very simple
ope
On Fri, Oct 16, 2020 at 7:12 AM vince touache wrote:
> oh that's weird. Did you try it via mayapy or directly via your python
> interpreter? I'll give it a try with python/qt outside of maya
>
Yea I was running it from just a normal interpreter, since I was using a
laptop that does not have Maya
On Fri, Oct 16, 2020 at 7:22 AM vince touache wrote:
> neat, works perfectly!
>
> w = self.nodesArea.takeWidget()
> if w: # just in case the scrollArea was empty
> w.setParent(self)
> self.nodesArea.setWidget(node.node.gui)
>
> much more elegant and simple than what I had, thank you so much J
neat, works perfectly!
w = self.nodesArea.takeWidget()
if w: # just in case the scrollArea was empty
w.setParent(self)
self.nodesArea.setWidget(node.node.gui)
much more elegant and simple than what I had, thank you so much Justin!
Le jeu. 15 oct. 2020 à 14:12, vince touache a
écrit :
> oh
oh that's weird. Did you try it via mayapy or directly via your python
interpreter? I'll give it a try with python/qt outside of maya
anyway, your github link is pure gold, I can indeed see that the scrollArea
apparently removed the widget ! I used reparenting a lot in the past, and
it always worke
I wasn't able to reproduce your problem from the code you provided. You may
need to consolidate it into a single file that can be executed, or be more
specific about the conditions under which you are executing it. But either
way, I agree with your idea that it is related to calling
QScrollArea.set
