DIM D501= LOCATION OF POINT PT501 SD=0.0000 UNITS=IN ,$
GRAPH=OFF TEXT=OFF MULT=10.00 OUTPUT=BOTH HALF ANGLE=NO
AX MEAS NOMINAL +TOL -TOL DEV OUTTOL
X 39.8049 39.8049 0.0150 0.0150 0.0000 0.0000 ----#----
Y -1.2775 -1.2775 0.0150 0.0150 0.0000 0.0000 ----#----
Z -1.5851 -1.5851 0.0150 0.0150 0.0000 0.0000 ----#----
T 0.0000 0.0000 0.0150 0.0150 0.0000 0.0000 ----#----
END OF DIMENSION D501
PT501 is a DMIS point, not a PCDMIS vector or surface point.
Have to leave them in program and not convert to a PCDMIS point.
I have a script the tests if a Cmd is a feature.
IF Cmd.IsFeature THen
Count = Count + 1.
PT501 is detected as a feature,
but the Cmd.IsFeature is detecting another feature incrementing
the counter when I don't want it incremented.
Would it be the MEAS/POINT,1/WORKPLANE that is considered
a feature and how would I test for that and not have the counter
incremented?
Thanks for your response Henniger123.
I would only mark the point features/vector points I wanted changed.
I the case of the programs I wanted to modify, vector points were added in certain areas,
so the vector point feature names were changed to PT255A, PT255B, PT255C ETC , ETC.
There might be 2000 points in the program that would intermittingly have sections
of points added with the above type changes added. I wanted to mark all original and changed points
and have them in numerical order.
Also, thanks for the code change. Much more concise and elegant if I might add.
That's the difference between an experienced programmer (yourself) and a novice (myself)
I once made a script that would order everything in numerical order by type just in case I skipped a bunch of feature name eg. PNT4... skipped a few... PNT32 the script would renumber all features with PNT[n] in order eg. PNT4... PNT5... and so on. It was a pet peeve of mine that PcDmis would throw numbers off if you created features and then deleted them (and other reasons I don't recall right now) and tried to recreate them. Unfortunately I left all that work at my last place of employment, I'm sure I can recreate it but I no longer have a seat of PcDmis handy to work on.
I once made a script that would order everything in numerical order by type just in case I skipped a bunch of feature name eg. PNT4... skipped a few... PNT32 the script would renumber all features with PNT[n] in order eg. PNT4... PNT5... and so on. It was a pet peeve of mine that PcDmis would throw numbers off if you created features and then deleted them (and other reasons I don't recall right now) and tried to recreate them. Unfortunately I left all that work at my last place of employment, I'm sure I can recreate it but I no longer have a seat of PcDmis handy to work on.