Hey Pmeems,
I'm currently using 4.9.3.5 and calling the map in LabVIEW. I know its not the most common platform. I would be happy to share the code, however it is part of a giant project so posting only a piece of code wouldn't be representative of the entire code. The map loads correctly when it first runs and multiple times after that. However as time passes or the application is continuously stopped and started, the map won't display correctly at all zoom levels and will show blank white spaces.
Some background on how it is being used. The map is loaded and then points are added to the map, at different. Different images are assigned to each point, which is done by creating multiple categories and assigning a category to a point shape. All these points exist on a single shapefile, which exists on a single layer.
I'm mainly checking to see if anyone else sees this issue on another platform and can rule out LabVIEW. As mentioned I do see a creep in memory usage even when removing all points, and triple checking to make sure all references are closed, so I believe with that the memory creep is causing some issues of MWG displaying correctly.
Many Thanks,
SAzizi
I'm currently using 4.9.3.5 and calling the map in LabVIEW. I know its not the most common platform. I would be happy to share the code, however it is part of a giant project so posting only a piece of code wouldn't be representative of the entire code. The map loads correctly when it first runs and multiple times after that. However as time passes or the application is continuously stopped and started, the map won't display correctly at all zoom levels and will show blank white spaces.
Some background on how it is being used. The map is loaded and then points are added to the map, at different. Different images are assigned to each point, which is done by creating multiple categories and assigning a category to a point shape. All these points exist on a single shapefile, which exists on a single layer.
I'm mainly checking to see if anyone else sees this issue on another platform and can rule out LabVIEW. As mentioned I do see a creep in memory usage even when removing all points, and triple checking to make sure all references are closed, so I believe with that the memory creep is causing some issues of MWG displaying correctly.
Many Thanks,
SAzizi