Hannes Winkler

I'll make it so it's only reported in debug mode, though honestly I didn't think anyone would care.

Yeah right now flutter-pi just uses the first display it finds, though it uses KMS not dispmanx (dispmanx is deprecated AFAIK) Right now it's pretty easy to workaround, so lower...

Sure, output selection happens here: https://github.com/ardera/flutter-pi/blob/e60ccd19d753674dc9481d87a073dd7e9c9bf4f9/src/flutter-pi.c#L1267 . That loop will just select the first connected connector. If you want a specific connector like HDMI you can just skip all non-HDMI...

@Taha-Firoz Sounds awesome! Though if you do that, I think it's a good idea to write that stuff on top of the `feature/compositor-ng` branch. That's a huge refactor/rewrite of the...

> Your design seems to be a lot similar to [ivi-homescreen json configuration file](https://github.com/toyota-connected/ivi-homescreen/blob/c3abadee678da430203bc23b2a11c7718d857ad5/README.md?plain=1#L139) implementation. Since Joel is interested in eventually pulling flutter-pi in for ivi-homescreen's DRM implementation do you...

> What are you using for parsing json in C, futter-elinux is using Tencent rapidJson. I'm using `jsmn.h`, it's a header-only library, though tbh calling it a parser is probably...

@Taha-Firoz yes, that's fine by me. (Both things.) I could also migrate the platform channel code to cJSON too, seems nicer than jsmn.

You can create a draft PR if you want, so we can coordinate the work better :) Or you get your prototype going first, how you prefer. Looks pretty good...

Yes, `eglGetPlatformDisplay` is EGL 1.5 only. In earlier EGL it's called `eglGetPlatformDisplayEXT` instead, I'll change the logic so it falls back to that if the 1.5 version is not found

please don't close this, I'll close it when it's resolved instead