As it has been discussed in the past [1], running Weston
without any input device at launch might be beneficial for
some use cases.
Certainly, it's best for the vast majority of users (and
the project) to require an input device to be present, as
to avoid frustration and hassle, but for those brav
Test for all the possible lengths (up to 8), specifying which are
expected to be valid and how they should be interpreted.
Sprinkle some `#` and `0x` around randomly to make sure those work at
any length too.
Signed-off-by: Eric Engestrom
---
tests/config-parser-test.c | 160
Valid colours start with an optional '0x' or '#', followed by:
- AARRGGBB
- RRGGBB
- A R G B
-R G B
- XYXYXY
- XX
Signed-off-by: Eric Engestrom
---
I just stumbled back on this discussion from a few months ago, and
decided to give it a go.
Once again, I apologise for length of th