I just downloaded the WPF Q3 trial, to determine whether RadMap might finally be hostable inside WinForms.
Good news.. RadMap Q3 finally has the capability.
Bad news.. Simply running in WPF, the demo app that ships with the solution .. Q3 is *much* slower than either Q1 or Q2 of the 2010 release.
This is a *huge* difference. It's gone from real-time response, to a lag of 5 seconds to zoom in/out.
I've tested this on 3 different machines (all Intel i5's with 4 to 8GB RAM and NVIDIA graphics cards (1x 9800, 1x 210, 1x 240 .. all of these are 2009 or later models).
In every single test, the new Q3 version is 400% or more slower than Q2. In addition, I noticed that the CPU of the machines will not reach more than 15% (approx) while in Q1, Q2 I would regularly see the CPU hit 40% when moving rapidly around the map.
Will this be fixed in Q4, or will there be a hotfix to address the problem?
Good news.. RadMap Q3 finally has the capability.
Bad news.. Simply running in WPF, the demo app that ships with the solution .. Q3 is *much* slower than either Q1 or Q2 of the 2010 release.
This is a *huge* difference. It's gone from real-time response, to a lag of 5 seconds to zoom in/out.
I've tested this on 3 different machines (all Intel i5's with 4 to 8GB RAM and NVIDIA graphics cards (1x 9800, 1x 210, 1x 240 .. all of these are 2009 or later models).
In every single test, the new Q3 version is 400% or more slower than Q2. In addition, I noticed that the CPU of the machines will not reach more than 15% (approx) while in Q1, Q2 I would regularly see the CPU hit 40% when moving rapidly around the map.
Will this be fixed in Q4, or will there be a hotfix to address the problem?