David Bengali Posted June 30, 2017 Share Posted June 30, 2017 Hi, wondering if anyone has encountered this or knows of a solution: When I enable custom object info palette for a plugin object with vs.SetObjPropVS( vs.kObjXPropHasUIOverride, True ) #8 I find that trying to change the value of radio buttons in the object info palette crashes vectorworks. I have inserted all of the widgets with vs.vsoInsertAllParams() I'm not trying to do anything crazy; I am really just trying to get some separators onto the OIP. I am handling Event 41 as guided by the wiki: ... elif theEvent == vs.kObjOnWidgetPrep: #41 UpdateParametersState() ... def UpdateParametersState(): vs.vsoSetEventResult( vs.kObjectEventHandled ) #-8 Changing the value of other parameters in the OIP, including numeric fields and checkboxes, works fine. Most importantly, I see the same behavior when I try the example plugin provided at http://developer.vectorworks.net/index.php/Python_Sample_Point_Object_(complex) If I click the radio button for Male / Female in this PIO's info palette, vectorworks crashes. This leads me to think there is more going on than bad code in my own object. I am running VW2017 SP4 on Mac OS X El Capitan Quote Link to comment
Patrick Winkler Posted June 30, 2017 Share Posted June 30, 2017 Hi David, this is a known bug. I will push the report. regards 1 Quote Link to comment
David Bengali Posted June 30, 2017 Author Share Posted June 30, 2017 Thanks Patrick, Is there an advised workaround? I am discovering that various third party plugins are showing the same behavior as well and have thus become unusable. best, David Quote Link to comment
Patrick Winkler Posted June 30, 2017 Share Posted June 30, 2017 The only workaround I know is using a dropdown menu instead of the radiogroup. regards 1 Quote Link to comment
David Bengali Posted June 30, 2017 Author Share Posted June 30, 2017 that's great, thanks Quote Link to comment
JBenghiat Posted July 12, 2017 Share Posted July 12, 2017 The other workaround is to turn off developer mode when you're testing radio buttons. It's always a bummer when you forget though... I finally hunted down a VW plug-in that triggers this behavior, and this is slated for a fix. Possibly not until 2018, though. -Josh Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.