Point selection problems

[Anonymous]

For viewing functions and in some cases selecting points to create a group
for example you will see strange behavior.

For example, if you import points from a file, select one point by an
implied window then use 3DORBIT or Object Viewer you will get all of the
points not just the one you selected. Also, when selecting points for a
point group by selecting points in the drawing, you will get nothing if you
make an implied window, however if you make an implied crossing window the
program will accept the points.

Kevin Breslin

[Anonymous]

Kevin,
Points in Civil3D are not objects, they are simply data - this saves
us over 90 bytes per point - the point group is the object. This is
what's causing the behavior you're seeing in 3DORBIT and Object Viewer.
The window selection issue is a known defect we're looking into.

Dan Slater


Kevin Breslin wrote:
> For viewing functions and in some cases selecting points to create a group
> for example you will see strange behavior.
>
> For example, if you import points from a file, select one point by an
> implied window then use 3DORBIT or Object Viewer you will get all of the
> points not just the one you selected. Also, when selecting points for a
> point group by selecting points in the drawing, you will get nothing if you
> make an implied window, however if you make an implied crossing window the
> program will accept the points.
>
> Kevin Breslin
>
>

[Anonymous]

>>Points in Civil3D are not objects, they are simply data

that's an interesting statement, because when you list
the point, under "Select objects:" you get both in the list:
AECC_POINT_GROUP and
AECC_COGO_POINT

thanks,

--
Strah @ Langan

"Daniel Slater" wrote in message
news:D3DE285CE68296A853A43FFA1CE59AB2@in.WebX.maYIadrTaRb...
> Kevin,
> Points in Civil3D are not objects, they are simply data - this saves
> us over 90 bytes per point - the point group is the object. This is
> what's causing the behavior you're seeing in 3DORBIT and Object Viewer.
> The window selection issue is a known defect we're looking into.
>
> Dan Slater
>
>
> Kevin Breslin wrote:
> > For viewing functions and in some cases selecting points to create a
group
> > for example you will see strange behavior.
> >
> > For example, if you import points from a file, select one point by an
> > implied window then use 3DORBIT or Object Viewer you will get all of the
> > points not just the one you selected. Also, when selecting points for a
> > point group by selecting points in the drawing, you will get nothing if
you
> > make an implied window, however if you make an implied crossing window
the
> > program will accept the points.
> >
> > Kevin Breslin
> >
> >
>

[Anonymous]

I suppose the "AECC_COGO_POINT" tag is a bit misleading in this case. The
point group actually prints all of this information in response to the list
command. Perhaps it would be clearer if we hadn't used a DXF style name to
label the individual points. If you look very carefully, you'll see that
the AECC_COGO_POINT tag is indented slightly more than AECC_POINT_GROUP (by
1 character). Also notice that the AECC_POINT_GROUP contains an entry for
"number of points selected". Both are indications that the point is really
not a separate object.

Chris Putnam
Software Engineer
AutoCAD Civil 3D Team