[VBA] Test if selected element is root feature or subfeature

Hi brenks,

it's just a thought, unfortunately I have no time to test it now, but in my opinion if you create a feture, it will be always root feature. I checked xft help quickly and maybe GetParentAssociations methods can help you.

With regards,

Jan

Thanks, it's not helpful. My files are corrupted, there are features with multiple subfeatures that have same uuids and subfeatures actually don't know who is their parent. I wrote macro that rebuilds features but it works until subfeatures are in selection set. Maybe the solution would be to exclude levels on which subfeatures reside.


I think that VBA command
Set ModelReference = object.Copy (SourceModel, Name [, Description])
is the cause of our corrupted files

Hi,

Unknown said:

My files are corrupted

I have no experience with such situation, but I in my opinion if the file is corrupted (I guess it relates to a problem you decribed here), you cannot rely on some (many?) methods (which probably rely on relations defined by uuids).

I think the solution depends on specific condition of your project, but there is a possibility it cannot be solved using VBA only and MDL API has to be used. I found xfmElement_getFeatureUuids that returns both parent and subfeatures ID. I guess if there is no parent uuid returned, the feature is the root feature.

Unknown said:

I think that VBA command Set ModelReference = object.Copy (SourceModel, Name [, Description]) is the cause of our corrupted files

For what purpose do you use this method? You maybe right as this is MicroStation VBA API, which is probably not aware of internal strcuture and rules like uuids.

With regards,

  Jan

Hi,

Unknown said:

My files are corrupted

I have no experience with such situation, but I in my opinion if the file is corrupted (I guess it relates to a problem you decribed here), you cannot rely on some (many?) methods (which probably rely on relations defined by uuids).

I think the solution depends on specific condition of your project, but there is a possibility it cannot be solved using VBA only and MDL API has to be used. I found xfmElement_getFeatureUuids that returns both parent and subfeatures ID. I guess if there is no parent uuid returned, the feature is the root feature.

Unknown said:

I think that VBA command Set ModelReference = object.Copy (SourceModel, Name [, Description]) is the cause of our corrupted files

For what purpose do you use this method? You maybe right as this is MicroStation VBA API, which is probably not aware of internal strcuture and rules like uuids.

With regards,

  Jan