max_ishere

I looked at the docs for greetd and it looks like you can just not start a session after you create it. So basically if cached -> create_session() if success...

> What I need: > - Fix clap (I have done it manually, but still) #87

What if we join the user/session selection screens into one? Then there would be no need to skip anything. Here's how it will work: If config.start_session_on_startup then go to screen...

Also if on screen 2 the session is changed, that change will be used when starting the session. And when the user is changed, then the old session will be...

I am currently in the process of making this kind of UI, but given my current schedule there's no ready date.

Screenshots of the UI I proposed in text blocks. I use the smallest width because it is the easiest to get a consistent width on. **Autostart prompt** (for addressing the...

And I know what some that know how the UI used to work think, if you change the user, then what? Then, the UI goes to the "**Authentication not started...

And if the session changes, then nothing in particular happens. it just saves the selection to be used when the session is started.

If anyone wants to test it out: https://github.com/max-ishere/ReGreet/tree/703962cb5e644b14b8d7dcb66d2844a91bcf9824 Edit: Oops, forgot to git add all the changes...

:warning: Just realized is should have mentioned that the link above is just the UI, it doesn't actually interact with greetd IPC. So launch it in demo mode