add a toast for uinput errors

[shocktail39]

this makes it more obvious if missing uinput permissions are the reason your keyboard and mouse aren't working.

this message shows up in wayvr's log, but the log can be a bit overwhelming for people who aren't experienced in reading logs. a simple wayvr >>test 2>>test followed by a sigterm as soon as i saw something, generated a 16K log file according to ls. this toast puts the error front-and-center as soon as wayvr starts, so when the user notices their keyboard overlay is busted, they already have a hint as to why it might be.

[shocktail39]

got any feedback? i know i changed the signatures of two public functions (specifically their return types) which isn't really ideal, but as far as i can tell, doing so was necessary to make the error live long enough to be displayed in a toast. i also am not entirely familiar with wayvr's codebase, so i might have missed a better way to do this.

[galister]

i think maybe raise the timeout, 10s might not be enough for such long text.

[shocktail39]

yeah that's fair. i'm in class right now and can't test before pushing, but i'll change it when i get home.

also, i noticed that quite a few of the setup functions give similar log warnings. i kinda want to display some of them too, but i'm not sure how to best display them to a user who doesn't know how to read logs. just spamming every error at once would be overwhelming, but a queue of errors one-after-the other might be overwhelming too, in a "oh god when the hell will it end" sorta way.

edit. actually, instead of a timer, is there a way to create a text display with an "ok" button at the bottom?

[oo8dev]

edit. actually, instead of a timer, is there a way to create a text display with an "ok" button at the bottom?

Not such thing exists yet in the code, so let's stick to the notification delay at least for now

[galister]

i think just bump it to 30s and call it a day.

[galister]

or without timeout, even