BUG: MapRegion.GetMap with circle area and scrolling

Hexalog · Post by **Hexalog** » Wed Apr 02, 2008 12:49 pm

Looking at 3.2.2897.29193 dissasembly, I believe the code could be modified as follow (see comment):

...
if (scrolling
   && ((i < 2) || (polygon.PointStyle != PolygonStyle.Circle)) // The correction
  )
{
  if ((i == 0) || ((i % 2) == 0))
  {
    polygon.Coordinates[i] -= bounds.Left;
  }
  else
  {
    polygon.Coordinates[i] -= bounds.Top;
  }
}
...

Sorry if this has been already corrected or reported.
Best regards.

Narcís · Post by **Narcís** » Thu Apr 03, 2008 10:32 am

Hi Hexalog,

Thanks for the information. Could you please give us some more details about the exact problem and send us a simple example project we can run "as-is" to reproduce the problem here?

You can either post your files at news://www.steema.net/steema.public.attachments newsgroup or at our upload page.

Thanks in advance.

Hexalog · Post by **Hexalog** » Fri Apr 04, 2008 7:12 am

Sorry no sample project available. However this is fairly easy to understand without. The error exhibits in ASP project when scrolling is active and map contains circle polygone shapes.

In this case the circle radius of the polygone shape is decrement as well which is of course wrong hence the fix I suggested.

Narcís · Post by **Narcís** » Fri Apr 04, 2008 9:46 am

Hi Hexalog,

Could you please then export your chart to a .ten file so that we can load and test it here?

You can export the chart like this:

Code: Select all

WebChart1.Chart.Export.Template.Save(@"c:\temp\mychart.ten");

Thanks in advance.

Hexalog · Post by **Hexalog** » Fri Apr 04, 2008 3:48 pm

Oh well

! I made a quick and dirty sample project.

To see the problem, open the source code of the HTML page generated and look at area's coords attribute. Circle radius is negative instead of the one we set (expected value mentionned in the annotation).

Filename of the uploaded file is: BrokenCircleMapInTeeChart.zip

Thanks. Have a good week-end.

Post by **Marc** » Mon Apr 07, 2008 1:50 pm

Hello,

Thanks for your observations and suggestions. Part of the solution lies with code sample you sent over. There's a little more we'll need to take a look at to resolve a couple of related issues so we're checking those now. We will hopefully be able to include a fix for the next maintenance release.

Regards,
Marc Meumann