PeterStrick
Proposed New Features, and 1 Bug Fix - I can help
Today I'm proposing a small set of changes, and I can certainly help, as I have fairly decent VB.net and C# abilities. Ideally, ViveTool-GUI should be converted to C# as it has numerous performance advantages, but I understand that not everyone knows C#, so that can be discussed/considered another time.
My Proposals:
- Fix Features View Listbox: When searching and enabling features, the view often jumps to the top, even if "start search from this location" is ticked. This needs to be fixed because it's very easy to loose your place when toggling features off and on.
- A Local “Changed” File: Which should keep track of what the user changed and allows them to revert the changes. This would allow the user to revert all changes that they made. I tried using the CLI vive and using the reset config option, and it didnt' work.
- A "First Seen" Field Added to the Feature Dictionary and Listview: Along with adding this field, I propose changing the format to CSV. When the system is scanned, it can ask for the previous output file, and when this is included, any new feature IDs not included in the previous file will be given today's date of the scan. Optionally, a diff file can be created doing this. I assume this would make it easier for anyone creating .diff files as all they would have to do when scanning is supply the previous feature dictionary. The reason for this is a simple one, right now the current implementation does not allow for any way to know what features are old and which ones are new. Subsequently, right now, its easy for someone to enable feature IDs with old code pathways, allowing for many things to break.
A Local “Changed” File
A history feature logging the Value that was first seen would be doable
UI when thinking would be similar to this
| Feature Name | Feature ID | Original Value | Current Value | Comment |
|---|---|---|---|---|
| MeetNow | 123456789 | Disabled by Default | Enabled | (Comments Icon shown explaining what MeetNow does) |
| RandomFeature | 987654321 | Enabled | Disabled |
I propose changing the format to CSV
The Feature Dictionary comes directly from the ViVe Repository so unsure about that
Optionally, a diff file can be created doing this
Some diff files from the last Build to the next Build exist already in the mach2 Repository
Copied from the other Issue
I was actually thinking how cool it would be if I could help bring the project to WinUI3 UX without the Windows Store.
Migrating to C# and a new more open source UI Toolkit like WinUI3 / Avalonia was actually planned for Version 2.0
I didn't start using it until mid-2023 so perhaps you're referring to before then? In that case, I can understand, especially if it was a big change.
It was the v1 Github Projects which were per-Repository instead of the v2 Projects which are now per-Account
For Vive and feature flags, do you know a lot about them?
No one except Microsoft knows alot if them, all we can do is try them out and see what happens. If something interesting happens then report our findings back
what's old, and what's dangerous to enable
v1.7 has a Feature Comments System that allows you to comment eg your findings on a Feature Flag that will directly show up in the UI
This brings to me a couple of feature requests, which shouldn't be very hard to do, and I can help the best I can: I created a new issue here with my suggestions.
Yeah it's best to discuss those there