[Attached is a small script demonstrating the issue]
[Please note, I misunderstood the problem slightly here in my original post. The problem is more general: buttons that are children of a panel that is itself a child of the mainform will not have their click events processed until the form closes…a new demo script showing that is now attached in addition to the original demo script]
Quick Overview of Problem
In Rhino 8, if I make a custom panel and add it to my main form like single control, the click events on child controls of the custom panel are not processed until the entire dialog is closed. The same form can run in Rhino7 or Rhino6 and the clicks will be processed normally.
I have a large project (large for me) that uses custom panels, and I guess I need to know if this is how Rhino8 will be going forward or is it unintended behavior. Also, if it is unintended behavior, I guess a rough time estimate of it getting fixed might be nice as that would help me know if I should redesign my project to not use custom panels or if I should wait for the fix.
Long-Winded Context That’s Probably Unnecessary
I used custom panels to make dealing with DynamicLayout easier for my brain to understand so I can probably re-work everything…just…ugh…it’s gonna be a lot work.
I designed my project in Rhino 7 because there was some problem or problems with the Rhino8 editor. I think autocomplete was often not working and then randomly working, but honestly I can’t remember the exact reason, but as I do all my stuff in python2 for compatibility reasons, I didn’t think it would be an issue.
[this is the original script when I thought it was custom panels]
custom panel demo.py (1.7 KB)
[this is the new script showing that it is just panels in general]
buttons in a panel.py (1.6 KB)
system_info.txt (2.5 KB)
7 posts - 2 participants