Opened 11 years ago

Last modified 7 years ago

#2605 new defect

Can MathML blocks be nested in the XML dump?

Reported by: Bill Janssen Owned by: probably noone
Priority: high Milestone: Future
Component: Backend Version: trunk
Keywords: Cc:

Description

Matt and I were looking at the XMLDump code this afternoon, and we think there's an error, which would be fixed by this change. What we're seeing is <MathML> blocks embedded in other <MathML> blocks, which seems wrong. We think the wrong function is being called to express the vector's value.

Attachments (1)

XMLDump.mo.patch (499 bytes ) - added by Bill Janssen 11 years ago.
patch to XMLDump.mo

Download all attachments as: .zip

Change History (10)

by Bill Janssen, 11 years ago

Attachment: XMLDump.mo.patch added

patch to XMLDump.mo

comment:1 by Adrian Pop, 11 years ago

I think you can commit it as you're the only one using dumpXMLDAE as far as I know.

comment:2 by Martin Sjölund, 10 years ago

Milestone: 1.9.11.9.2

This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).

comment:3 by Martin Sjölund, 10 years ago

Milestone: 1.9.21.9.3

Milestone changed to 1.9.3 since 1.9.2 was released.

comment:4 by Martin Sjölund, 9 years ago

Milestone: 1.9.31.9.4

Moved to new milestone 1.9.4

comment:5 by Martin Sjölund, 9 years ago

Milestone: 1.9.41.9.5

Milestone pushed to 1.9.5

comment:6 by Martin Sjölund, 9 years ago

Milestone: 1.9.51.10.0

Milestone renamed

comment:7 by Martin Sjölund, 8 years ago

Milestone: 1.10.01.11.0

Ticket retargeted after milestone closed

comment:8 by Martin Sjölund, 8 years ago

Milestone: 1.11.01.12.0

Milestone moved to 1.12.0 due to 1.11.0 already being released.

comment:9 by Francesco Casella, 7 years ago

Milestone: 1.12.0Future

The milestone of this ticket has been reassigned to "Future".

If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.

If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".

In both cases, a short informative comment would be welcome.

Note: See TracTickets for help on using tickets.