Arrow keys dont work instantly when --default_widget_type is set to CPU about bottom HOT 7 CLOSED

Does this occur with the newest stable release (0.9.6)?

from bottom.

Just tested it - this is technically correct behaviour, you would have the same behaviour if you started on the process widget and selected the graph part of the CPU widget, which is what is selected by default if you do --default_widget_type cpu.

That said, I honestly don't remember why I made them disconnected - might have been for consistency since things like the process widget treat things like the search and sort "subwidgets" as separate widgets from the main process widget.

from bottom.

I suggest a simple line, that transitions one into the other, after the startup
Ideally, it would also save the position past closing the app, while I guess thats a separate issue.

Thanks

from bottom.

I suggest a simple line, that transitions one into the other, after the startup

Sorry, not exactly sure what you mean by this - do you mean like combining the two with a connector? I guess that's doable, though I don't know if I want to do that.

As for saving the position between invocations, yeah that seems reasonable to add at some point as an option. (EDIT: filed #1345)

from bottom.

As far as I understand, starts the app now in a state, in which it is impossible to move the cursor by arrow keys

And I understand, that there is another state, which allows that

Why not simply transition from one state into the other automatically?
At startup?

from bottom.

🤷 I don't really feel like that's a necessity, and I would rather address the crux of your issue (that you wanted to select the average CPU by default).

from bottom.

Closing as this is not a bug, and in favour of #1350.

from bottom.