Talin
@CooCooCaCha I'm in agreement with you here - the UI should be rendered into an offscreen buffer, and then the buffer should be composited onto the main view with it's...
> So you want every node to have this compositing component on it, and have a system that not just propagates opacity but other things as well, sort of like...
Just to be clear, I am not in favor of the approach of modifying child opacities. While it might look OK in some cases, it will look bad in others....
Naming suggestions: * `QueryItemRef` (`Mut` is often used as a suffix, so why not `Ref`?) * `ValueRef` * `WithRef` * `RefWrapper` * `RefAccessor` * `RefAccess` * `Reference`
@alice-i-cecile Different kind of "path" I think. I don't think we're talking about filesystem paths here.
I've edited the title of the bug to reflect the current discussion.
> @viridia could I get your review here? So I guess I'm being brought into this because of the prior discussion about wanting to remove the use of `Path` and...
> I'm surprised by this. Isn't the whole point of `std::path` to be platform-agnostic? @bonsairobo The problem is that `AssetPaths` aren't really paths - they are URLs. They eventually get...
Sorry for not responding sooner, dealing with some health issues. The latest discussion is #10511.
An alternative approach would be for each preference item to be a separate resource, and have `Preferences` be a HashSet of resource ids. This would give you somewhat more granular...