Devolutions / Devolutions/UniGetUI
[ENHANCEMENT] Reverse the order of the Operation History log
- Dominant language
- C#
- Stars
- 26.1k
- Forks
- 924
- Avg merge
- 15h 52m
- Merged PRs (30d)
- 52
Description
### Please confirm these before moving forward
- [X] I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
- [X] This improvement refers to an existing feature. If you want to suggest a new feature, please use [this template](https://github.com/marticliment/WingetUI/issues/new?assignees=marticliment&labels=new-feature&projects=&template=feature-request.yml&title=%5BFEATURE+REQUEST%5D+%28Enter+your+description+here%29)
- [X] This improvement is not a bug. If you want to report a bug, please use [this template](https://github.com/marticliment/WingetUI/issues/new?assignees=marticliment&labels=bug&projects=&template=bug-issue.yml&title=%5BBUG%5D+%28Enter+your+description+here%29)
### Describe the improvement
How important this is questionable, it is however the reverse order compared to all other logs in WingetUI which is sometimes confusing because of having to orient yourself by checking the timestamps first. Reversing the log would mean the text field should probably scroll to the bottom when opened so that the newest operation is seen first. Other issues raised by reversing the log could be "reattaching" to the bottom of the log if you have previously scrolled up.
### Describe how this improvement could help users.
WinGetUI logs are always viewed oldest to newest, top to bottom.
Contributor guide
Assessment
This issue has not been assessed yet.