[Feature Request] Option to have Flux path be the internal one rather then using / #27

New issue

Open

opened 2025-04-28 16:59:07 -05:00 by LeCloutPanda · 0 comments

LeCloutPanda commented

2025-04-28 16:59:07 -05:00

(Migrated from github.com)

Having the option to show internal paths rather then the normal ones will allow making custom node browsers easier or quick access buttons for commonly used nodes.

I don't really know how to explain what I want but you can see below the OnActivated on the right has a different path then what the internal one is, having the option when search it displays the internal path instead or beside the normal path would be nice

For example something like this could work

Also having a option to toggle full or small path that doesn't include the [ProtoFluxBindings]FrooxEngine.ProtoFlux.Runtimes.Execution.Nodes.FrooxEngine would also be nice

Having the option to show internal paths rather then the normal ones will allow making custom node browsers easier or quick access buttons for commonly used nodes. I don't really know how to explain what I want but you can see below the OnActivated on the right has a different path then what the internal one is, having the option when search it displays the internal path instead or beside the normal path would be nice ![Image](https://github.com/user-attachments/assets/0f4148b6-5d0a-4191-8463-aea0b915e9e6) For example something like this could work ![Image](https://github.com/user-attachments/assets/2039cd47-9f43-43f1-a7f6-4b64c9b41298) Also having a option to toggle full or small path that doesn't include the ``[ProtoFluxBindings]FrooxEngine.ProtoFlux.Runtimes.Execution.Nodes.FrooxEngine`` would also be nice