Piotr Podusowski
Piotr Podusowski
I suppose `tile_url` could return `Result`/`Option`. `max_zoom` could be then removed.
On a second thought, we need to know zoom limits before setting it and attempting the download.
I'll try to play with it and see where it ends up.
Just to clarify. You want walkers to render lower zoom levels using tiles with higher zoom?
This is how `TileSource::max_zoom()` works. It will not download tiles exceeding it, but you can still zoom in (up to currently hard-coded 26) and it will render it from whatever...
It's ok, I figured. :) The thing is that both `min_zoom` and `max_zoom` can mean two things - either lock zooming beyond that point or not downloading tiles beyond the...
Well, they differ in API, but whichever is chosen, we still need to render unavailable tiles somehow. For `max_zoom` it is already done - i.e. walkers will just [magnify available...
Does hiding the keyboard work as expected for you? I have ported it to 0.29 to test it with my winit/egui stack and it crashes with: ``` 07-14 14:27:00.856 15745...
> Do you by any chance somehow create the `EventLoop` of the main thread? Like inside the `std::thread` or something like that? @kchibisov No, I don't think so. It's a...
I've created a demo based on winit 0.29 and egui, showing a crash here: https://github.com/podusowski/winit/tree/pr3787-with-egui-crash it's in `demo_android`. To run it, call ``` make -C demo_android run-on-device ``` I haven't...