[CONNECT U12] Monitor EC data change best practice?

Hi,

this my question is more about best practice, not specifically targeted to C++ or C#. C# is preferred in my current project, but when the solution will be available in C++ only, no problem.

Situation: There is an element with custom EC data attached. The data are available in Properties (Element Information) dialog and can be modified by a user. Such change is saved to persistent storage (DGN V8 file) by MicroStation automatically.

Question: Is it possible and what is recommended approch to monitor such change to be able to react on the change (e.g. to modify the element size/shape/etc.)?

I have not done any testing or research yet, but I can imagine that XAttribute changed event is fired when EC data are changed, but it seems to me a bit complicated (go through the whole path from XAttribute, test whether it's EC data or not and to what element it belongs). Maybe there is some other solution available, e.g. to monitor EC data particularly or to hook system responsible for rendering EC data in GUI?

With regards,

  Jan

Parents Reply
  • i.dgn's  are the only way in many cases to access the data generated by the vertical

    That was the original purpose of the i-Model: to eliminate app-dependent DGN structures that could not be displayed in vanilla MicroStation or other PowerPlatform viewer.

    there is a big difference between a dgn and i.dgn which has all the vertical's information exposed

    Whan an app user publishes (Bentley terminology) a DGN to an i-Model, the internal app-specific graphic structures are removed on being simplified to primitive DGN graphics.  Business information (i.e. EC Schema data) is retained.

    Because i-model is designed to be read-only (as implemented in MicroStation)
    I don't think this is correct at all. I think that read only is a voluntary restriction, not an inherent one

    It is correct.  That is one raison d'être of the i-Model concept.  i-Model is read-only by design.

    Do a web search and the role of GUID's also pop up

    A GUID is nothing more than a piece of data attached to an object.  One hopes and expects that a GUID persists, which in a read-only situation of course it does.  If someone copies and edits, say, an IFC or i-Model file, then one expects and hopes that the editor will persist the GUID of modified objects correctly.

    Editing, of course, introduces a risk.  What if the editor does not persist GUIDs adequately?  For example, let's say I copy an i.dgn to a writable .dgn file.  Then I edit that copy.  If my editing splits a widget into two parts, to which part should the original GUID be attached?  Or should something else happen, such as creating two new GUIDs?   How do we correlate the two new half-widgets with the original whole widget?  Those questions return us to the origin of this thread: Jan's question about monitoring EC Data changes.  Only if our code can monitor EC Data changes successfully can we think about devising a policy for propagating GUIDs when using MicroStation as an editor.

     
    Regards, Jon Summers
    LA Solutions

Children
  • It is correct.  That is one raison d'être of the i-Model concept.  i-Model is read-only by design.

    This is becoming silly. So, how do explain i-model Transformer? In any case, what the religious meaning  / intention of i.dgn's is secondary. What the users do with it will count for more. 

    Editing, of course, introduces a risk.

    Exactly. That's why there needs to be some tools to help persist and manage / resolve changes... GUID management has always been a hot topic.

    Sticking your head in the sand does not help. The need is there. 

  • So, how do explain i-model Transformer?

    As far asI know, i-model Transformer is designed similarly to ETL (Extract Transform Load) tools: No change is done at original data, but data are read, transformed (converted, merged with another sources etc.) and saved to new "data version" with own provenance information.

    That's why there needs to be some tools to help persist and manage / resolve changes...

    I think that's one from main topics behind iModelJS.

    Sticking your head in the sand does not help.

    I do not understand this comment and it seems to be offensive a bit.

    Because we are in programming forum, as developers we can discuss what is possible to do and what is possible to implement using existing APIs and what features are allowed by used formats. Nothing more, nothing less. We depend, or better to say we choose to depend ;-), on what Bentley decides that is the best to fulfill their business strategy.

    Of course there are alterantive solutions (every new product tells it solves all existing questions and issues ;-) and ideas how existing need can be solved, but in my opinion it's beyond scope of this forum. Fortunately anybody can go and to investigate own technology, but because after so many years there is still no technology that beats other and conquers the world, it's probably extremely complicated at the same time to design it, to implement it in acceptable cost and be able to sell it.

    Regards,

      Jan