David Luzar

To start out: 1. If `` not rendered, render the default. 2. If rendered, render it empty. 3. Create a `` component that we'll use for our own hamburgerMenu items,...

Perhaps, though we need to ensure the naming of all the components we'll end up with is clear and distinguishable. Menu is pretty generic (but so is HamburgerMenu).

We used to have it colorized to be more obvious:  Perhaps we should go back to doing it. Otherwise, we use these icons because it's a de facto standard....

@anatoliibakhtin I love your designs! That said, the (4)/(5)/(6) are not obvious to me. I could easily explain the (4.1) to both mean either "send to back" or "send backward"....

@T3sT3ro looks cool, but super complex for icons. Bear in mind that when scaled down to the button size, you'd be barely able to see anything:  In the end...

@josephbuchma Testing on iPad vs Android, seems pretty much the same. If you didn't mention it reproduces on the perfect-freehand, then my immediate thought would be zoom differences as well....

> @dwelle I reproduced this issue in a live collab session, same devices (iPhone 12 on the left, Pixel 2 XL on the right) > > 20221219_224249.mp4 Do you happen...

Thanks! It looks like an issue with pointer pressure. On Android it emits touch events with pressure, where on iOS it does not. Perhaps we should ignore pressure from touch...

On Android, I'm getting (as per above link I shared) these numbers: ``` "pressures": [ 0.062745101749897, 0.062745101749897, 0.062745101749897, 0.062745101749897, 0.062745101749897, 0.062745101749897, 0.062745101749897, 0.062745101749897, 0.062745101749897, 0.062745101749897, 0.062745101749897, 0.062745101749897, 0.062745101749897, 0.062745101749897, 0.062745101749897,...

On an unrelated note, something I noticed in the previous PR (which is now also part of this one): these completely unrelated features should be made in separate PRs instead...