Suggestion: Add Resource export_group() as Tabs.

[khirsahdev]

It would be nice if you could use export_group() as tabs only for resources. I was able to add something similar with AI since I don't have enough knowledge with Plugins, but I think I broke all the classes as tabs. But it really helps with nested components being too long. Here's a snapshot of what I have.

Basically I can choose mode for use classes or export_groups(Specifically for resources), currently I'm using the export_groups mode since the other broke and I wasn't able to fix it.
I also have a quick eye icon, that toggles on/off the tabs function to see everything.

Would it be possible to integrate this kind of function?

Below shows a screenshot of separated export_groups.

Below shows a screenshot of merged export_groups by using a simple icon to toggle on/off the tabs function.

[PiCode9560]

I don't really use resources much, so I'm not really sure what were you proposing.

It would be nice if you could use export_group() as tabs only for resources.

You're suggesting that the export_group should only be a tab on resources and should be nested in the class tab when on node?

From the screenshot I'm guessing you want to only see the tabs for your custom resources, and hide other built in classes in one tabs.

But it really helps with nested components being too long

Can you clarify what is the issue you're trying to solve? Reducing the amount of tabs displayed?

[khirsahdev]

The goal is similar, to separate them into separate tabs to avoid scrolling too much, so that it supports not only classes but also export groups.

This would also help with any node that has lots of settings like particle effects etc.

The hide feature and categorization is just QoL, incase someone prefers to see only exportgroups or only classes as tabs.

[PiCode9560]

Oh wait, I got it, you're talking about export_group, not export_category. So I feel like this is not needed, because the tabs is supposed to only hide categories, not whatever sub-properties. Also, if the group is too long, can't you just collapse it? Another thing is, if the tabs show groups, then on nodes like the control node which has lots of groups, the tabbar will be filled with them. What do you think?

[khirsahdev]

You certainly have a point. I guess I was too desperate in trying to manage too many nested resources.

If there were too many export groups it would cause confusion.

I really do love the way that tabs could separate things into tab for a cleaner look, but this scenario certainly isnt ideal and wont work as nicely.

Thanks again for your input!

[PiCode9560]

You could collapse all groups (from the manage object properties) to make it easier to find the group you want. Furthermore, maybe we could add an option to make groups collapse automatically when the tab is switched. Does this sound useful to you?

[FloatVip]

You could collapse all groups (from the manage object properties) to make it easier to find the group you want. Furthermore, maybe we could add an option to make groups collapse automatically when the tab is switched. Does this sound useful to you?

What you suggested is excellent, but on one condition: if we click on one group to uncollapse it, the other groups should collapse. This way, things will be very organized and clean. I believe this suggestion could be added as an option in the settings.

Edit : Also, the group that remains open stays open even if we click on another node.