Michael Tang

I'm looking forward to the `0.6.27`, which should include #212 and close this issue out! Thanks for implementing this!

I can confirm that the `use-cargo-master` branch fixes this: https://github.com/kbknapp/cargo-outdated/issues/167#issuecomment-500106777

It's probably worth it to document which handedness `Transform::look_at` is meant to use (it might be a bug that the Matrix3 and Matrix4 aren't consistent here in their implementations of...

I don't thing perf is a big concern at all, DPI can change at most a few times a second (afaik, zooming in/out on the web is the quickest way...

@mitchmindtree My understanding is that `Clone` was removed to disallow users from having a way of modifying the `ScaleFactorChanged` event after the event occurs. If we want to re-introduce it...

(I wasn’t a part of the original event loops 2.0 discussions so I’m a bit clueless here) ~Since EventLoop::run passes a &Event (and Event is not clone), a user would...

Update: - New design uses a wrapper struct for just the `new_inner_size` - The wrapper struct is `Clone` (which should allow `Event` to be clone). - Uses interior mutability as...

@goddessfreya: While this PR isn't ready to review, but I would love your thoughts on the concept (replace the lifetime with interior mutability) to see if it's something we'd consider...

@Osspial no worries at all for the response times! I know we're all busy (and the world is especially weird right now!). I'll need to take some time myself to...

@Osspial: turns out most of my changes was just the "interior mut cool thing", which you've greatly improved. Latest changes: - rebased onto master - copy Osspial/scoped_arc_cell into code and...