topic Re: Maximizing window while zooming in a scene view in Qt Maps SDK Questions

Maximizing window while zooming in a scene view

HenrikVatnar — Wed, 20 Mar 2019 11:03:08 GMT

Using the arcgis runtime cpp samples viewer I see some strange behavior.

1. Start the Scenes/Display a scene example

2. Make sure the application is running as a smallish window.

3. Zoom in/out using the scroll wheel on the mouse

4. While the animation is going on(i.e. its moving in or out). Maximize the window.

5. I get a small sceneview in a large black maximized window. See attachment.

If you wait until the zoom/pan animation has stopped before maximizing everything works as expected.

Is this a known bug? Or is something maybe wrong with my setup? I'm running windows 10 and arcgis qt sdk 100.4 with qt 5.12.0.

Re: Maximizing window while zooming in a scene view

LucasDanzinger — Wed, 20 Mar 2019 18:19:16 GMT

Thanks for letting us know. I'll log a bug for us to look into this. I found that resizing the window "fixes" it. Maybe a temporary workaround to make it pop back into place would be to resize the window programatically after the resize and viewpoint animation is done.

Re: Maximizing window while zooming in a scene view

HenrikVatnar — Wed, 20 Mar 2019 19:37:10 GMT

Yeah that would probably work. I don't have any code in front of me right

now but I think that setting the view center/extent programatically with an

animation (make it take a couple of seconds) and doing the maximize while

the animation is running is actually ok. Not completely sure though. So it

could be something with how the mouse events are handled.

You think a fix for this might be in 100.5 or is that window already closed?

And thanks for another quick response!

Re: Maximizing window while zooming in a scene view

LucasDanzinger — Thu, 21 Mar 2019 16:34:24 GMT

I found the same thing - if I programmatically change viewpoint, it works ok, but it is something with the mouse interaction/events. We are only a week or so away from release, so it is looking like we unfortunately will not be able to fix this for this upcoming release (100.5)