In VB:
Dim ftr as MapXLib.Feature
For Each ftr in map.Layer("TargetLayer").AllFeatures
...
Next
-Original Message-
From: Hamish George [mailto:[EMAIL PROTECTED]]
Sent: 06 March 2000 09:16
To: [EMAIL PROTECTED]
Subject: MI Mapx - How can you
Why
not create a second map control which handles the layer, but is not visible to
the user?
-Original Message-From: Gareth Hardman
[mailto:[EMAIL PROTECTED]]Sent: 01 March 2000
07:25To: [EMAIL PROTECTED]Subject: MI Making layers
invisible to the user in the MapX
I have had the same experience. I suspect the features.add can only be used
to add to the map. Maybe you need to use a simple VB collection rather than
a layer collection if you simply want to hold a collection of features
without putting them on the map.
-Original Message-
From:
I downloaded the 4.01 patch from the web (www.mapx.com) yesterday and
successfully installed it at the second attempt. The result works OK in VB6.
The only problem I have noticed with v4 is that SearchAtPoint seems only to
find one object from a layer even though there are several at the
I have a couple of medium-sized Mapinfo native tables (1 mb and 3mb .map
files). The last few records I added to these tables (using MI Pro 5.0) are
visible are visible when using MI Pro (version 5.5 now), but do not appear
when I user a MapX (3.5.2) application. As far as I can tell the rest of
-Original Message-
From: Mike Saunt [mailto:[EMAIL PROTECTED]]
Sent: 04 October 1999 11:22
To: '[EMAIL PROTECTED]'
Subject: RE: MI RECORDS NOT VISIBLE IN MAPX
Mike,
I have opened and closed MI and MapX many times and the problem persists. I
also tried removing the layer and putting it
