eadocX Support

[eadocX Support]

Ha! Found it.
It’s my old friend, the Word HTML interface – ‘helping’ by removing leading blanks. Just added   to make sure it gets the point.

Fixed now- just building & uploading – look for v2.2.1.04 on eaDocX.com shortly – might take a while, as my internet seems to have knocked-off for the holidays…

[eadocX Support]

OK – looking at it now – it’s not quite doing what I remember – Generator seems to be ignoring CRLFs as well.. 🙁

[eadocX Support]

This is related to the way that EA saves this text, and how it makes it available at the API. Sometimes it adds suprious, invisible whitespace , expecially when the text has been copy/pasted from other tools.
So, we remove it – it usually gives better results. Except in your case.
Not a great solution, but you might add the psedo-code into a tagged value ?

[eadocX Support]

Tricky in EA or tricky in eaDocX? I can fix the latter – the former is harder…..

[eadocX Support]

Stefan,
Good news! This is an eaDocX feature, for all the reasons you describe.
There is a printable attribute for Classes, Attributes and Methods which is Element Features, which will print a hyperlink to another Class (or other element e.g. Requirement), Attribute or Method, which I think should give you the traceability you need. Search on “Element Features” in the eaDocX help, and that has all the details.
Thanks
Ian

[eadocX Support]

Fixed in new version 2.2.1.03 now on eaDocX.com

Thanks for spotting this!

[eadocX Support]

Thanks for the tip – I’ll give it a try.

The sorting problem is a real pain – I agree. I will have another look.

[eadocX Support]

The only way to print the same element in many ways is to use eaDocX Element Reports.
These have their own formatting, either Table or Inline.

[eadocX Support]

Excellent!
I’ll look at that, and plan to include it in v2.3 – due later next month.
Thanks for the tip :-))

[eadocX Support]

Not much, really:-)
The first problem is that I can’t figure out how to get the numbering to go beyond 1.x: how do you get to 2.x ???

If I knew that, I’d have a go at getting the x.y formatting to print properly.
e
As for the sorting, I’ve just tried to add a ‘sort’ to the Message.Sequence number, and it seems to come out OK. I was using a table to print the messages, added the SequenceNumber as column, then added sort.

[eadocX Support]

You’ve found the same un-explored corner of the EA-API as I have: EA allows this for their RTF generator, but don’t make a rotated image available at their API.
We’re going to look at a temporary switch from Landscape to Portrait – just for the diagram – in the next release, but that doesn’t help you much at the moment – sorry.

[eadocX Support]

Sorry it doesn’t do what you want. I’m looking at allowing you to specify the Word table style (for the next release) but that seems to be a bit fragile In MS Word) as well.
Your idea about allowing code snippets is a good one: I’ll see if I can can build it into the next vesion as well.

[eadocX Support]

I can’t reproduce this error. Did you notice that eaDocX will only let you print Tagged Values where a TV exists in your model, for the element you’re printing? So, if you give a TV of ‘wibble’ to a UseCase, you can only print the ‘wibble’ tagged value for a Requirement when there is at least one Requirement whihc has the ‘wibble’ tagged value.
I wonder if that’s part of the problem?

[eadocX Support]

The Generator doesn’t specify where tables appear – we just insert them into Word, so I think there must be a setting in Word somewhere which controls the indentation of tables. Maybe a ruler, or tabs controls? Sorry we can’t be of more help 🙁

[eadocX Support]

There is an error in the Sparx API for SQL reports, so that whilst they allow us to run a report from the API, we can’t get the results back!
I’m encouraging Sparx to fix this, but no luck so far – perhaps you could help out by submitting a question to the Sparx forums (as I have) noting this ?
The API calls in question are
Project.RunModelSearch , which returns ‘void’
and
Repository.RunModelSearch(), which doesn’t say what it returns.
Hmmmm – this last bit makes me wonder if the second one really does return something – it’s just Sparx aren’t telling us: i’ll have a look

[Author]

Posts