search

Neos-Metaverse / NeosPublic

A public issue/wiki only repository for the NeosVR project
194 stars 9 forks source link

Add disable options in each Tip component for any Builtin Context / Arc menus generated by the Tip #3301

Open kazu0617 opened 2 years ago

kazu0617 commented 2 years ago

Is your feature request related to a problem? Please describe.

This is often a problem, especially if you are developing a multi-tool tip, or if you are modifying the tip a little bit, even if it is not a multi-tool tip. For example, consider what percentage of people who first use the LogiX Tooltip understand about traversal. Also, it should not be necessary for everyone to have all buttons visible all the time, even in the Component Tooltip.

Relevant issues

These one is just only focused with Inspector / Node Browser, but current issue is more general arc one. https://github.com/Neos-Metaverse/NeosPublic/issues/2850 https://github.com/Neos-Metaverse/NeosPublic/issues/2851

I checked with General Radiant Menu Feedback but nothing about this issue, but Of course, this issue mentioned about Radiant UI so I written it. https://github.com/Neos-Metaverse/NeosPublic/issues/449

Describe the solution you'd like

I want each Tip Component to have an option to disable any menu generated by the Tip.

We currently use a very primitive method (we know the order in which they are generated, so we remove Arcs based on the order) to remove such menus, but all Tip without RawDataToolTip is hardcoding which Arcs are generated. However, I have hard-coded which Arcs are generated for all but the RawDataToolTip, so I should be able to turn around and provide an option to disable them (of course, I may have to think about making it even smarter in the future).

Describe alternatives you've considered

Another alternative might be to include an option to disable them in the redesigned configuration UI, but I personally don't see the need to go that far (for example, because a custom tooltip doesn't need a button to show the built-in inspector node browser, but a standard tooltip obviously does).

Additional context

This may be able to integrate any custom inspector related issues, so please let me know if I forgot to write the relevant issue.

epicEaston197 commented 2 years ago

this can also be very useful for getting rid of buttons you don't like I'm definitely all in for this