Leonardo Gibrowski Faé
Leonardo Gibrowski Faé
> If the issue on main is distinct (which seems likely) I can make a separate issue for that if you like No no, this is perfect. If the issue...
Possibly fixed with PR #439. If you guys were willing to test it, I'd appreciate it.
@YaLTeR Are you sure that's really the issue? `swww` always uses the latest advertised mode: ```rust fn mode( &mut self, sender_id: ObjectId, _flags: wayland::wl_output::Mode, width: i32, height: i32, _refresh: i32,...
Well, sure, but the protocol says that `non current` mode are deprecated. I could add a `match` statement preventing it from using anything other can current, but I don't think...
Solved by #467
I believe the problem with this is that it wouldn't reload the image if the output's configuration changed. That was the original reason for that commit.
I also do not understand how this could possibly be the solution to #386. There seems to be a more fundamental issue we have to address.
Alright, we may have the proper fix for this in PR #439, actually.
The "dataset" is just 100 1920x1280 images, nothing special. This is the relevant code: ```rust let config = RuntimeConfig::local(threads as u64 * 5).unwrap(); let env = StreamContext::new(config); let result =...
Thank you for taking the time to look into this! The full code for the first case looks like this: ```rust use raster::filter; use serde::{de::Visitor, ser::SerializeStruct, Deserialize, Serialize}; use std::time::SystemTime;...