20 Aug 2024 |
jamwaffles | Single width lines don't look too bad either | 12:54:51 |
jamwaffles | This all looks so much better at 1x scale. Screenshots are at 5x | 12:55:10 |
22 Aug 2024 |
James Munns | 📣 Hello all! The 2024 Embedded WG Survey is now live!
https://www.surveyhero.com/c/uenp3ydt
This survey will be open for **four weeks**, ending **September 19th**! But please fill it out as soon as possible, and share (politely) in as many places as you'd like!
I'll be tracking where I share this here: https://github.com/rust-embedded/wg/issues/782#issuecomment-2304466766, please feel free to add other places you've shared it there. | 11:48:59 |
23 Aug 2024 |
dngrs | not relevant to the eg crate but "embedded graphics" as a topic: the palette crate has a std feature, but when I don't have that activated I get odd build errors, any ideas?
Compiling palette v0.7.6
error[E0277]: the trait bound `f32: Round` is not satisfied
--> /Users/ace/.cargo/registry/src/index.crates.io-6f17d22bba15001f/palette-0.7.6/src/angle.rs:127:40
|
127 | self - Round::ceil(((self + 180.0) / 360.0) - 1.0) * 360.0
| ----------- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `Round` is not implemented for `f32`
| |
| required by a bound introduced by this call
...
179 | impl_angle_float!(f32, f64);
| --------------------------- in this macro invocation
|
help: this trait has no implementations, consider adding one
--> /Users/ace/.cargo/registry/src/index.crates.io-6f17d22bba15001f/palette-0.7.6/src/num.rs:234:1
|
234 | pub trait Round {
| ^^^^^^^^^^^^^^^
= note: this error originates in the macro `impl_angle_float` (in Nightly builds, run with -Z macro-backtrace for more info)
I did check docs and source, sadly couldn't find any hints apart from this bit of macro expansion which is a bit too thin for me:
#[cfg(any(feature = "std", all(test, not(feature = "libm"))))]
impl Round for f32 {
| 17:53:23 |
dngrs | uuh | 17:55:05 |
jamwaffles | I think that just says you need to enable the libm feature no? | 17:55:07 |
dngrs | nevermind | 17:55:08 |
dngrs | In reply to @jamwaffles:matrix.org I think that just says you need to enable the libm feature no? yeah it seems so, weird though because to me it reads like this impl block will exists if libm is not enabled? my boolean logic seems broken. | 17:55:41 |
jamwaffles | It's strange that it would be there for "tests unless libm is activated" | 17:57:13 |
dngrs | no-std tests can be weird like that I guess | 18:02:07 |
dngrs | * no_std tests can be weird like that I guess | 18:02:15 |
2 Sep 2024 |
| Jonatan Borkowski joined the room. | 06:55:44 |
| Jonatan Borkowski | 06:58:02 |
| Jonatan Borkowski | 07:00:07 |
| @jborkowski-5690dcb416b6c7089cc1ccbd:gitter.im left the room. | 07:02:51 |
| Jonatan Borkowski set a profile picture. | 07:23:55 |
5 Sep 2024 |
| Dom 'shymega' Rodriguez joined the room. | 10:50:28 |
7 Sep 2024 |
| @aroonv:matrix.org left the room. | 16:17:12 |
16 Sep 2024 |
| trepidacious joined the room. | 18:03:40 |
trepidacious | I've been working with embedded-graphics-framebuf and mipidsi to drive an ST7789 screen (320x240) from an RP2040 under embassy, it gives okayish performance but it takes about 110ms to just fill_contiguous the frame buffer to the display. It looks like DMA might be used, but I've not found yet how to work out whether it will be? The SPI is running at 64MHz AFAICT, so theoretically it should manage to send a whole screen in say 24ms or so? | 19:16:21 |
jamwaffles | In reply to @trepidacious:matrix.org I've been working with embedded-graphics-framebuf and mipidsi to drive an ST7789 screen (320x240) from an RP2040 under embassy, it gives okayish performance but it takes about 110ms to just fill_contiguous the frame buffer to the display. It looks like DMA might be used, but I've not found yet how to work out whether it will be? The SPI is running at 64MHz AFAICT, so theoretically it should manage to send a whole screen in say 24ms or so? I don't know what the expected perf is from RP2040, but just to check the obvious, are you running with --release ? | 19:21:08 |
trepidacious | In reply to @jamwaffles:matrix.org I don't know what the expected perf is from RP2040, but just to check the obvious, are you running with --release ? Yes, not sure on the performance either, I've not done much SPI on the RP2040 | 20:56:57 |
23 Sep 2024 |
Alexandros Liarokapis | danielb: Hi there, thanks for your great crates. I want to implement a menu that depending on the selection changes the meaning of the main inputs. So normal navigation becomes state change and previous selection unselects the given entry. Do I need to handle this through shared state on a given entry's handler and then modify the incoming inputs ? | 12:12:57 |
danielb | oh wow I have no idea, embedded-menu isn't working knowledge for me right now 😣 | 12:14:07 |
danielb | easiest might be to hide one entry and display another in its place | 12:14:26 |
Alexandros Liarokapis | In reply to @bugadani:matrix.org oh wow I have no idea, embedded-menu isn't working knowledge for me right now 😣 It's okay, hard to keep everything in mind :) Thanks again! | 12:15:29 |
| mameluc joined the room. | 13:06:56 |
| David Vandenburg joined the room. | 13:45:33 |
| nandnor joined the room. | 13:54:04 |
| tegimeki joined the room. | 15:13:36 |