Replies: 1 comment 1 reply
-
I've updated my impl of a workaround here |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello! First off, I am very excited about this project, thank you to all the contributors for all of the hard work so far! I've played around with elm a decent amount and love the architecture design, so seeing an implementation in rust is 💯 .
The project I am currently hoping to use
iced
in will be an application that runs on the beaglebone black device. I've been able to get the counter demo application compiled + able to run on the device, but the program fails at runtime.I've done a decent amount of debugging locally on the device and discovered that it is actually running into a problem during
glutin
's process of finding an available frame buffer configuration; glutin is not able to find a matching config and returnsCreationError::NoAvailablePixelFormat
. From the default implementation of thePixelFormatRequirements
struct, it looks like it is going to try to find a configuration that matches:The problem is, there is no config that matches that (or at least, it doesn't find one), based on what I am seeing from
glxinfo
(truncated to only include the8x8x8
color buffer configs).Anyways, I was just wondering if anyone has run into this kind of issue before, and secondly, if expanding
iced
to support those additional fields would be acceptable?I did manage to compile the example application and run it successfully after applying this diff, which I would be happy to submit a pull request for!
Beta Was this translation helpful? Give feedback.
All reactions