Hi Dave,
This seems to work just fine. As you say, it's a massive XML schema, so I
can't easily verify that it's correctly generated but I will let you know
of any potential issues.
Many thanks!
//Olof
On Wed, Mar 14, 2018 at 12:53 AM, Dave Kuhlman
wrote:
> Olof,
>
> I believe I've found a fi
Olof,
I believe I've found a fix. After this patch, gDS correctly
generates the `buildChildren` method in class `logicalPortType` so
that the `range` child is built as an instance of class `range` and
not as an `unsignedPositiveLongintExpression`.
It does cause other differences in the generated
Olof,
I think your clue about the `range` type being modified or switched
is a good one. So, `logicalPortType` is ending up with a `range`
child that has the wrong type.
I did some debugging around that idea today. Tomorrow, I'll try to
find out when and how `logicalPortType` is ending up with
On Fri, Mar 9, 2018 at 12:53 PM, Olof Kindgren
wrote:
>
>
> On Thu, Mar 8, 2018 at 11:32 PM, Dave Kuhlman
> wrote:
>
>> Olof,
>>
>> I saw in another email from you that you solved your namespace issue
>> with the --no-namespace-defs command line option.
>>
>> Great.
>>
>
> I realize later that I
On Thu, Mar 8, 2018 at 11:32 PM, Dave Kuhlman
wrote:
> Olof,
>
> I saw in another email from you that you solved your namespace issue
> with the --no-namespace-defs command line option.
>
> Great.
>
I realize later that I had not solved it completely, but I'll leave that
for now. Still have some
Olof,
I saw in another email from you that you solved your namespace issue
with the --no-namespace-defs command line option.
Great.
Concerning the problem you describe below related to the differences
between classes logicalPort and partSelect -- Thank you for
providing that sample code and the
Not sure how to best describe the problem, but I found an issue where it
seems like I get the subelement of a node instead of the node itself.
The following input XML
adr_o
