Home Website Youtube GitHub

Customize the quick function of setting and updating mgear component types

Hello mgear user.

I customized a quick function of setting and updating mgear component types for my team, which can easily and quickly set and update to the related component types in the manager.
This function supports setting and updating “multiple components of the same type at the same time”.

They are located in Shifter Guide Manager and Dag Menu respectively. Both entrances can quickly update the component type selected in the viewport, but they are located in different positions, so that users can freely choose the function entrance according to their preferences.

What it looks like in Shifter Guide Manager:

00

What it looks like in DagMenu:

01

Let’s take a look at how it works.

In Shifter Guide Manager, you can directly update the component type selected in the Manager to the component selected in the viewport.

in_manager

In DagMenu, there will be a “Select Related Component Scope” selection window before setting the update. This design is for users to set and update across types according to their needs.

I think the types in the current manager are roughly divided into two types, one is what I call “Default”, which is the current majority of component types (or the type before the EPIC component appeared or called “Old”), and the other is called “EPIC”, which is the component designed for the UE engine.

For example, users can update the “arm_2jnt_01” setting to “EPIC_arm_01” and vice versa. Although the mixed use of non-EPIC components and EPIC components has no practical application in our team, and I don’t know if other mgear users have practical applications, the “Select Related Component Scope” selection window is designed to give users maximum flexibility.

The following gif should be able to clearly demonstrate what I mean:

in_dagmenu01

I am willing to hear your voice, and any questions or suggestions will be greatly appreciated.
(English is not my native language, the above text comes from Google Translate.)

5 Likes

@fury_Night This is a very good idea!
In the past it was a planning to create compatible component options, like softimage version. But I never implemented it on mGear.
If you want to send a pull request on github. I would love to check it and merge if I don’t see any issue with the current implementation.

Thanks!

1 Like

Thank you very much for your kind words! I’d be more than happy to submit a Pull Request for this feature and would be honored to contribute to the mGear community.

While I’ve never used Softimage before, the ‘like softimage version’ you mentioned has piqued my interest. Purely out of curiosity and to broaden my perspective, would you be able to share some related diagrams or demo videos if it’s convenient?

Looking forward to your reply - I’ll start preparing the code submission right away!

in the componen/guide.py you will find an empty list called compatible


I never finished the implementation
In softimage you can see the compatible is added in the guide

and the list was available in the type section:

2 Likes