Sebastian Dröge
Sebastian Dröge
I just noticed that there are *also* `data::params::AudioInfo` in addition to `data::frame::AudioInfo`, the first one not containing the number of samples. Two structs with the same name are also potentially...
Do you know where this is tracked? All serious discussions about "specialization" I saw were not about inheritance: https://github.com/rust-lang/rfcs/pull/1210
Also low-level parsers (like flavors) for the various formats would be generally useful separate from rust-av integration. Otherwise people are just going to write their own set of parsers for...
> Maybe there should still be a `ListStore` without a type parameter to support ones with a runtime dynamic type? Wouldn't that be `ListStore`?
What do you mean with not necessary? :) It's needed for correct usage of some APIs.
We don't have a bool parameter, that's the problem exactly :)
Also, basically all GTK signals that return `Inhibit`. You might want to connect to them and have your callback called after the default handling is all done already (and e.g....
Yes that's the dynamic one with `glib::Value`s everywhere. That's not very nice to use. `ButtonExt::connect_clicked` for example has no way to connect after.
That's exactly the question, how to handle that best :)