Hi,
I'm used to add option Strict on to my VB.nat code to avoid many mistakes. I can't do that with mapwingis which often uses "object". This causes late binding error with this option on.
As an example in
I think it would be good also if Mapwingis uses less this object type, it seems to me that it was possible to return here an array of integer .
Thanks,
Olivier
I'm used to add option Strict on to my VB.nat code to avoid many mistakes. I can't do that with mapwingis which often uses "object". This causes late binding error with this option on.
As an example in
Dim shapes As New Object
.SelectShapes(ext, 0.0, MapWinGIS.SelectMode.INTERSECTION, shapes)
.ShapeSelected(shapes(0)) = True ' late binding error
.ShapeSelected(cint(shapes(0))) ' will generate the same error
I would appreciate if someone gives me a trick to avoid it.I think it would be good also if Mapwingis uses less this object type, it seems to me that it was possible to return here an array of integer .
Thanks,
Olivier