Basic hierarchy in object list

Personally I never use meshes, only objects. I think the same do a lot of users.
We can have this function but only with option in settings.

I don't use meshes too, and work strictly with objects and their components. I don't even know what Nvil's meshes are supposed to do apart of complicating simple things.
So yeah, only as an option, please.

I do not use meshes either, but they are a part of the program and apparently
deeply nested in Nvils data structure.

In this case one maybe should make it impossible to duplicate items on mesh level?
Maybe it was even possible for IStonia to relocate those few functions which are
only available on mesh component level to Object Level?

If Booleans, Mirror, UV-Deform etc. were made available on Object component level
(even if they under the hood still remained functions which work on Mesh level)
one could entirely remove the Mesh component type from the GUI.
Would that make sense to you?

Another question: Is there a good reason for "hierarchical transforms" not being checked by default?
How can there be a hierarchy if children don't follow the parent node?

If Booleans, Mirror, UV-Deform etc. were made available on Object component level
(even if they under the hood still remained functions which work on Mesh level)
one could entirely remove the Mesh component type from the GUI.

I also think that we have to go away from meshes.
For examples booleans already works with objects there is command P_Boolean.
I very often have problem when want to mirror beacuse I can not set pivot for right Plane I have to set it with some special tools because of that meshes.
UV - dies it works? I tried it a lot time ago and it was not working as it should be so I leave it...
So yes objects instead meshes would be nice, at least mirror.

IStonia,
I tested this version and finde some bug, it creates folder and put objects inside it but also put this folder in first selected object. Check:


Also can you make tree to be expanded by default?

Also can you make tree to be expanded by default?

I don't know what you mean. If is just the top node "Scene Hierarchy"?

I mean when you start project your tree looks like this:


But would be great to have it like this:

Try this. The two problems should be fixed.
http://www.digitalfossils.com/Download/NVil-Oct-12-15.rar

Hm, nothing changed.

Hm, nothing changed.

Are you sure? Or I may misunderstand your problem.

When you started a new project. The top hierarchy node is expanded.
When you right click to create a new group, the new group's parent node is unchecked if it is unchecked before you right click it.

May be you do not upload modified version? I downloaded it twice.

When you started a new project. The top hierarchy node is expanded.

Yes you are right.

When you right click to create a new group, the new group's parent node is unchecked if it is unchecked before you right click it.

No. I mean that objects must be just inside folder not inside object. Just like files inside folder. And looks like it has to stay checked after creation.

Too bad that Set manipulator position nad Set manipulator orientation don't work with hierarchic transforms.
Any chance of solving this problem?

In Oct-10-15 version hierarchic transforms are broken.
To reproduce the bug: load the scene I provided under the post, enable hierarchic transform, select Object_Box, Object_Box_06 to _08 and move them someplace. The children of Object_Box won't move at all.

Try this and see if it has the two behaviors you want
http://www.digitalfossils.com/Download/NVil-Oct-11-15.rar

Looks good.

One more thing regarding manipulators.

Imagine the following hierarchy:

Code: [Select]

Box1
|-Box2
If you select Box1, which is the parent of Box2, and set the manipulator position to Selection (Manipulator Tools->Pivot(Selection)), its position is averaged between the parent and its children, instead of being located at the centre of the parent (which is the currently selected object).

IStonia, can you enable double-LMB click for renaming objects in the hierarchy tree?

IStonia, can you enable double-LMB click for renaming objects in the hierarchy tree?

May be not double but like in windows: First click, pause, Second click.

IStonia, can you enable double-LMB click for renaming objects in the hierarchy tree?

May be not double but like in windows: First click, pause, Second click.

In windows it's LMB+pause+LMB because double-clicking starts a program associated with a given file.
In Nvil double-click does nothing in the hierarchy window (well, it could be used for expanding parents), so why not utilize it for renaming?

In windows it's LMB+pause+LMB because double-clicking starts a program associated with a given file.
In Nvil double-click does nothing in the hierarchy window (well, it could be used for expanding parents), so why not utilize it for renaming?

May be you are right Double click on name would be nice.

Hm, maybe double-click should be used for expanding parents instead of renaming?
Or something between this. Double-click for expanding parents, but for children - it could allow for renaming. And for renaming parents, a delayed double click could be used? Just throwing in some loose thoughts.

than, I think LMB+pause+LMB will solve all problems.