"Elements" view not showing all available valid elements.

[DanielH]

I seem to have an issue whereby the 'Elements' view is not showing an element when it should show it. I have the following schema in place:

Code: Select all

<xsd:element name="description">

  <xsd:complexType mixed="true">

    <xsd:sequence minOccurs="0" maxOccurs="unbounded">

      <xsd:element ref="measurement"/>

  </xsd:sequence>

  </xsd:complexType>            

</xsd:element>



<xsd:complexType name="measurement">

  <xsd:simpleContent>

    <xsd:extension base="xsd:decimal">

      <xsd:attribute name="type" type="measurement-type" use="required"/>

      <xsd:attribute name="display-unit" type="xsd:boolean"/>

    </xsd:extension>

  </xsd:simpleContent>

</xsd:complexType>

When the caret is placed inside a description tag, then the measurement element should appear in the Elements view - see the image:



Is there something wrong with my schema? or my XML? or something else?

[DanielH]

Interesting thing to note is that the content completion picks up that I can insert a measurement tag at the location, but the Elements view doesn't.

(Sorry for the big pic - I had meant to just link to it but accidentally clicked Submit instead of Preview).

[adrian]

Hello,

Thank you for the feedback.
We have tested, but could not reproduce this behavior in Oxygen v13.2.
What version and build number of oXygen are you using(Window -> Preferences -> oXygen)?

The XSD sample you provided is shallow and the element and complexType are not connected, so I don't know with certainty what's the relationship between the two. I can only guess you have a measurement element that connects them:

Code: Select all

<xsd:element name="measurement" type="measurement"/>

Note that some XML well-form errors, can confuse the context for the Elements view, so that could be a possible cause for this problem.

If you want to help us investigate this, please send more detailed samples(XSD+XML) to:
support AT oxygenxml DOT com

Regards,
Adrian

[adrian]

Hi again,

In case someone else encounters this, it turned out to be a bug. I have logged this to our issue tracking tool and it will be analyzed and resolved in a future version of Oxygen.
We will post a notification here when a bugfix becomes available.

Regards,
Adrian