[0.4] How to load additional NodeSets about opcua-modeler HOT 10 CLOSED

Can you explain a bit more what you are trying to achieve?

from opcua-modeler.

Okay, I have a companion standard describing types (t.xml) and an own node set with instances of types described in (i.xml). Now, I cannot load and edit i.xml directly since the types are not there. Adding "t.xml" as a "reference node set" helps, however the existing instance in i.xml are not show since they were loaded before including t.xml

from opcua-modeler.

OK, we have an issue here. Does your i.xml file has a reference to t.xml somewhere? We could not find it in spec, but maybe that information is under tag?

maybe as a bypass you can import i.xml after adding reference? I do not remember if the functionnality was exposed.

from opcua-modeler.

it has an entry as NamespaceUris

I can of course import i.xml after reference, but then I am editing and exporting another file (that i currently merge in i.xml manually)

from opcua-modeler.

I really wanted to avoid having to create our own file format but it looks like we have too to solve this...

from opcua-modeler.

Why do you need two XML files when you can just put your types in a separate name space? This seems like a lot of work just to have separate files when you will always need both of them anyways.

from opcua-modeler.

added to master plan #3 This is critical

from opcua-modeler.

from opcua-modeler.

fixed in #51
Need more testing before merge as I add to add a new file type '.uamodel'

from opcua-modeler.

This now merged and seems to work

from opcua-modeler.