[CONNECT EDITION] How Split a Shape Element

Hi Salvio,

there are several problems in your question:

• What version do you use? To say [CONNECT Edition] is simply not enough, there have been 15 versions of MicroStation CE release so far. And please, do not waste the space, to use e.g. [MStn CE U13 C#] as discussed in this forum best practices provides more information using less space.
• What API do you use? COM/Interop or "new NET"?
• What "split" means to you? Without further details (requirements or limitations) defined by you the issue cannot be discussed, because on this general level, there is infinite ways how a shape can be split. Should the shape by split to triangles, to defined number of smaller pieces...?
  At a code level, it's about to create new shapes, following defined algorithm, in memory, and in one transaction to delete old one and to add the new ones to a model.

With regards,

  Jan

Hi Salvio,

there are several problems in your question:

• What version do you use? To say [CONNECT Edition] is simply not enough, there have been 15 versions of MicroStation CE release so far. And please, do not waste the space, to use e.g. [MStn CE U13 C#] as discussed in this forum best practices provides more information using less space.
• What API do you use? COM/Interop or "new NET"?
• What "split" means to you? Without further details (requirements or limitations) defined by you the issue cannot be discussed, because on this general level, there is infinite ways how a shape can be split. Should the shape by split to triangles, to defined number of smaller pieces...?
  At a code level, it's about to create new shapes, following defined algorithm, in memory, and in one transaction to delete old one and to add the new ones to a model.

With regards,

  Jan

Hi Jan,

• The versions they use are as follows
  Microstation : ms10120040en_updt12
  SDK : mssdk10130048en

• 
  In the project I use both COM / Interop and "new NET" so any solution would be fine.

• 
  The Split operation (required) should consist of selecting a shape, applying a sort of matrix,
  and replicate the selected object for how many elements are in the array.

Thanks for your help,
regards

Salvio Montella

salvatore montella said:

The Split operation (required) should consist of selecting a shape, applying a sort of matrix,
and replicate the selected object for how many elements are in the array

Well, that's one of the more imaginative specifications I have seen!

1. What is 'a sort of matrix'?
2. How does a matrix help to split a shape?

salvatore montella said:

replicate the selected object for how many elements are in the array

3. What is the 'selected object'?
4. Where did 'array' come from?

Hi Salvatore,

salvatore montella said:

The versions they use are as follows

it's not very important when NET only is used, but it's incorrect (not supported option) to use different version of MicroStation and different version of SDK together! Why to do so dirty development thing?

salvatore montella said:

The Split operation (required) should consist

Sorry, but it tells not too much and nothing about how the shape should be split. As Jon Summers wrote: What is "a sort of matrix"?

salvatore montella said:

The Split operation (required) should consist of selecting a shape, applying a sort of matrix,
and replicate the selected object for how many elements are in the array.

It sounds like quite complex code, so it seems to be more like "write some code for me", especially when it very different from your original question that was "how to split a shape", whereas now it "select element, make calculations, save changes to design file", moreover applied to an array (which is also not quite clear how it should work).

I recommend to start with MicroStation SDK examples to learn how to implement element location (modification) class and to implement a minimum set of features (to be able to locate shape and something like to remove the shape and place a circle in a middle of the shape). Until it works, how exactly the split should be implemented probably makes no sense.

With regards,

  Jan