Desktop Menu Overhaul

[Kreolis]

These are external links to screenshots of the menus in desktop mode.

BAR MENU

Only menus that are different form the bar menu are recorded. TABLET MENU

Lets discuss how and what we want to change

[Kreolis]

Tablet:

• unify all menus to not use scrolling but pages instead (scrollings is not so nice in VR)
• make appearance the same
• popups or dropdowns?

[ksuprynowicz]

Maybe instead of pages we could allow scrolling with controller analog sticks, like for example VRchat does?

[Kreolis]

That is also a option. But scrolling with laser is not good. But still I think paging might be better. I hate the scrolling vrchat also (its better but not good, because e.g. it does not remember the position)

[ksuprynowicz]

For some cases labelled pages (like tabs) would indeed make most sense. Unlabelled pages on the other hand would be extremely difficult to browse for me (so for example world list). I love browsing worlds in VRchat just by scrolling - I can just press downwards on controller and look though them this way. Woud it be possible to at least keep is as an option for such case?

[Kreolis]

Agreed scrolling on worlds is fine, but please with the stick. However I really hate scrolling in settings menus.

[ksuprynowicz]

I think that for settings menus tabs with thematically sorted optiond would indeed be best. In some menus scrolling will be unavoidable though as a fallback, especially list of audio sources, which is normally short on Windows, but can get very long on Linux.

[AleziaKurdis]

Scrolling in vr is possible if you have a decent area to do it (not those thin scroll bar from desktop UI) This is why there is a "Sidewalk" area in the place api and the more api. But it has indeed it's limit. Pager can be very annoying too on very long list. (remember the explorer app)

Smaller menu but more hirarchical maybe? another thing that has it's limits.

The scroll using the thumbstick... it work well with Vive desktop. it seems to be a good option.

[daleglass]

The menu API needs an overhaul before any reorganization is possible, because the current API uses the literal menu names and paths as the argument. This means that moving or renaming anything is going to break the current code.

[Kreolis]

buttons for on and off states on settings instead of sliders: