Distinguish node icons according to their "position" in the object tree

[guiroehe]

Hello,

currently the tree uses different icons for objects, code nodes, and general nodes. However, as objects have two "modes" (i.e. a "folder" node - colorful - and "object property" - grayed), sub-nodes will have different behaviors depending on which mode they were created (e.g. "dropscript" does not execute if placed under an object in the "folder" mode, which is appropriate, but can be overseen by an user).

It would help to have a visual distinction for the sub-nodes in this case, to facilitate modeling and error reduction.

This also would help users to understand better the syntax required "/" or ">" when accessing nodes.

Thank you.

[joerg_vogel_HsH]

Gui, > is a direct visual sign in tree view, when you mark an object node. If you highlight a node, copy it by shortcut or right mouse button menu and then you paste it in a script window or any other editor you get a complete path from Model root node.

[guiroehe]

Hi, @Joerg Vogel ,

thank you, but this is not what I meant. Please see the pictures below:

[joerg_vogel_HsH]

Node A is an attribute Node of MyProcessor1 (top level)

Node B is subnode of object MyProcessor1

The small gap distinguishes between attribute tree > and object subtree /

[guiroehe]

Hi, @Joerg Vogel ,

precisely. It would be simpler for users / customers if those had a slightly different signature, so they still can convey their nature (circles, shapes, etc.) but visually be distinct. This is a suggestion for software improvement based on best practices of user friendliness and clarity.

Thank you for stating clearly the meaning of each node. The only part missing in my suggestion is adapting the icons.

[joerg_vogel_HsH]

Gui, in the meantime you can do something similar by wording and capitalization- e.g Object level starts with an upper case letter, attribute level subnodes starts with a lower case letter.

[guiroehe]

Thank you, @Joerg Vogel ,

that is a good suggestion. Please keep in mind this was posted in the forum as a suggestion for HMI improvement.

Thank you once more.