Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invert Execution Log orientation to descending #18017

Open
bubbajonez opened this issue Nov 14, 2022 · 3 comments
Open

Invert Execution Log orientation to descending #18017

bubbajonez opened this issue Nov 14, 2022 · 3 comments
Labels
Feature request GUI GUI-related issues/changes

Comments

@bubbajonez
Copy link

Suggestion

My brain follows the base form set for reading and writing in western civilization ever since reading and writing were invented in these parts of the world, and that means left to right, and top to bottom.

Ergo, having a log which shows stuff bottom to top makes no sense to my brain, since it doesn't follow said western civilization reading and writing base form.

Hence, please change it to top to bottom instead ? The log can automatically scroll down to follow log entries as they appear, and the user can manually scroll up if he wants to read older entries.

Thanks for considering.

Use case

No response

Extra info/examples/attachments

No response

@thalieht thalieht added the GUI GUI-related issues/changes label Nov 14, 2022
@Balls0fSteel
Copy link

I'll see if this is easy to do and whether the team approves or not (via PR). But I agree, I also always end up scrolling down only to realize, the new messages are on top. Not saying it's "bad" like this or anything, it's a design decision I suppose. We'll see.

@stalkerok
Copy link
Contributor

It would be nice to make this method the default, but leave the user the ability to change the settings as he sees fit.

@Balls0fSteel
Copy link

So I started working on this, but it's not that simple. Basically there is the log window, and you have to scroll to bottom there. There is an in-built function, also works great. Splendid.

But you would have to call this from somewhere else. And this is what I've been tinkering with. Somehow I have to use Qt Slots and emit to scroll each time a new message comes in. Also maybe it'd be good to do it opportunistically. Only do it when view is active and if user clicks the Log tab, so it does not waste cycles all the time by just scrolling and scrolling. Though, I don't think Execution Log holds that many messages at each run.

But, I always think. And then people come along and say they have 30,000,000 torrents running for 3 years now on 26 petabytes of SSD and I'm like, okay. So assuming "sane limits" here is usually not so helpful, ha.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature request GUI GUI-related issues/changes
Projects
None yet
Development

No branches or pull requests

4 participants