topic Can I change command panel buttons? like delete some, add some? in 3ds Max Programming Forum

Can I change command panel buttons? like delete some, add some?

Waseem_Dabbas — Thu, 02 Jun 2022 09:33:03 GMT

Is there a way to rearrange the command panel buttons of a specific modifier so that I can delete some and leave only the ones I need to work with?

Using 3ds max For Architectural purposes could let you use not more than 10% from edit poly buttons, same thing for edit spline and others, I'm trying to find a way to make the user interface easier and adjustable, which I believe will increase the speed of work.

Re: Can I change command panel buttons? like delete some, add some?

Bob.Bon2000 — Thu, 02 Jun 2022 09:35:08 GMT

Max is running qt, so you can probably find QWidget with that name/text/icon/whatever and just widget.hide() it. Have a dig at qwidgets documentation.

Re: Can I change command panel buttons? like delete some, add some?

Waseem_Dabbas — Thu, 02 Jun 2022 09:41:41 GMT

I will make research for it, than you very much.

Re: Can I change command panel buttons? like delete some, add some?

klvnk — Thu, 02 Jun 2022 13:17:24 GMT

think you just need a scripted plugin that extends edit_poly and replaces the UI.

Re: Can I change command panel buttons? like delete some, add some?

Waseem_Dabbas — Thu, 02 Jun 2022 14:44:43 GMT

Sounds a good idea, any idea where to start from?

Re: Can I change command panel buttons? like delete some, add some?

Swordslayer — Fri, 03 Jun 2022 06:27:26 GMT

Extending Edit_Poly in a scripted plugin brings a level of indirection that breaks it in unpredictable ways (and you can no longer access the subobject levels from the modifier stack dropdown), you'd spend more time trying to make it work and pass along notifications than recompiling the modifier from the SDK samples with edited UI.

As for Qt UI, only a few new modifiers are full Qt, edit poly still keeps the old Win32 one. The rollout containers are Qt widgets and you can hide them with pySide2 (you have to do that everytime you activate the modifier) and you can technically manipulate the rest via user32 methods.

A mix between the two that should take a bit less time and takes away the indirection (and would keep working on other machines) is to use custom attributes with your customized UI that would work the same way as scripted plugin (with some of the same shortcomings like having to reimplement 'skip loop/ring' as the mxs exposure is broken but without breaking notifications or modifier stack subobject access). Inside its rollout open handler you can hide (or collapse) the other rollouts and you're left with only your custom rollout.