Should automatically grab ENV vars to decide backend

To get results sooner I've opted for a texture-font.
This is awful for many reasons:

• Stuck to a limited subset of characters, namely Latin based.
• Stuck to one font
• Stuck to one rendering of said font, which may not scale nicely
• It's monospaced. I'm happy with this but most people probably won't be

For all these reasons we need to look into a real font rendering library that we can hook into.

Starting with steam -tenfoot

• Close window
• Resize. Probably offer native*2, native, native/2 presets?

Any others?

As this is not originally intended to be used on machines with more than one output we need to work out what (and how!) we should be doing with extra outputs.

While not a major selling point, the ability to set colours in the menu and a background image would probably be well received.

Worst case scenario allow a colour selection and base BG/Menu etc off only that.

Both XDG and X11 popups are currently not functioning

In backends x11 and winit Alt-Tabbing or using any key combination where the backend-window loses focus before the combination is over means the modifier keys cannot ever be released

Anvil was considerably more feature-full than needed. Quite a bit of the code base could be made more lean

Due to not checking titles thoroughly, and not completing a callback & update system X11 windows often go without a title.

Also any window that changes it after initial setting will not be seen in the compositor yet

x11 and winit backends use absolute mouse position and do not correctly scale or correct out-of-bounds if the mouse has remained motionless

Currently the rule enforcing all pointer/keyboard/touch goes only to the active window ensures no interactions with layershells are possible.

Idea 1:
Increase pointer clamp to output size & reimplement layershell pointer/keyboard/touch code.

Pros: No pros beyond fixing

Cons: Which output? Currently mouse is only relative to main window and shows on each output equally. Layer shells show individually on each output the mouse shows on all outputs. Clicks on a panel/notification could be clicks in-window on a different output depending on resolutions

Idea 2:
Return to a global-space mouse that only appears on one output at a time, but might be over the game window in any output.

Pros: Interaction with layershell windows per-output is possible

Cons: Probably need a tool to lay-out the outputs, as the anvil default of appending them to the right of previous outputs will be simply confusing to most users. Mouse DPI will change per-output if the game doesn't hide mouse & use relative.

Idea 3:
Document that this is the case and simply don't fix. Layershell will be a suitable HUD standard but devs setting up environments using Consolation will need to choose elements that will auto-hide or function without user input.