-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
OpenGL backend does not support images #846
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Just chiming in here. I wanted to evaluate iced as an alternative to GTK4 when porting over my GTK4+C Linux audio manager to Rust. This backend makes heavy use of iconography for "normal" UX elements, for example various buttons for playback. The lack of support for images on the OpenGL backend is of considerable impact, as unfortunately I can't rely on the end user having hardware supported by wgpu. I fully understand that iced is experimental and not remotely comparable to something like GTK4 at this time, however my hope is that this will be treated with some priority for resolution before the grand 1.0 release. |
Just in case this helps you or anyone else: If you don't load images dynamically, i.e. they are known to you at compile/development time, you might be able to work around it using vector graphics. Specifically, one of my projects uses font characters for iconography, which works perfectly and is more painless once you want to change their scale. Edit: See Edit 2: removed the references to Svg, read on for the reason. |
@MCOfficer So Svg works? Per your OP it mentions:
Has this changed since April 26th? |
Ah damn, i might have told a lie there. I just quickly grepped the source and found this line in the glow backend, which I assumed was Svg support: But as it turns out, that line was last changed by the PR my OP refers to, so if hecrj says in this PR that Svg isn't supported, I gotta trust that. Sorry for causing confusion. |
Closing this in favor of #674. |
As per #354:
Also in that PR's discussion:
It's not ideal that I'm creating this tracking issue, but imo it's better than not having a tracking issue at all.
The text was updated successfully, but these errors were encountered: