Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - PeterHeintz

Pages: [1] 2 3 ... 50
1
Bugs and Issues / Re: MSSQL Connection Warning [-2147217900]
« on: October 11, 2018, 09:53:48 pm »
Thank you Simon!
Great guess!
Yes, the root cause was an add-in.

2
Bugs and Issues / MSSQL Connection Warning [-2147217900]
« on: October 10, 2018, 07:12:11 pm »
Hi,
a college of mine gets the following waring when connecting to MSSQL DBs:

Microsoft OLE DB Provider for SQL Server [-2147217900]
Incorrect syntax near the keyword ‘RowCount’

He gets this warning for both SQL repositories he connects too, but other users do not see this warning.
Further on, the warning seem not to have impacts on the work within EA.

Any ideas?

3
+1 because I miss that feature e.g. to state if a diagram was already reviewed or not.

4
General Board / Re: Status property of diagrams
« on: October 09, 2018, 08:15:03 pm »
Well Geert, but views might also have a kind of status.

However Geert is right when saying, you should focus more on your requirement elements and there states. Your requirements are your requirements and you can have many diagrams showing the same requirements.

5
No, there are now build-in constraints in EA which disallow to connect ports of incompatible types. You have to take care about that.

6
General Board / Re: RTF Scale Diagrams over footer
« on: September 27, 2018, 06:06:56 pm »
So I think it is time to create a bug report.

7
General Board / Re: RTF Scale Diagrams over footer
« on: September 27, 2018, 01:48:49 am »
From my investigations I get the impression, that the scaling problem starts if one has more than one line in the footer.

Geert do you have footers with more than one line?

8
General Board / Re: RTF Scale Diagrams over footer
« on: September 25, 2018, 09:32:36 pm »
I use a notebook with its monitor connected to and external monitor.
So I switched off my external monitor. However the problem still exists. :'(

However I was wondering why you do not know this.

I tried a Sparx document template with footers, and this works :).  So the problem seem to be in my template, but currently I have no idea what switch causes that, maybe something about page break or keeping things together.

9
General Board / Re: RTF Scale Diagrams over footer
« on: September 25, 2018, 05:14:39 pm »
Hi Geert,
I just tried it in Word. The result is a bit different, but still not ok.

In Word I see the header and footer, but the diagram is cropped rather than scaled to see the footer.

Anyhow, currently Word is not an option for me, because of our cover page needs to have a graphics for whatever reason and some overlaying text coming from the model. Doing that, is very tricky and I did not get to manage it for Word.

10
General Board / Re: RTF Scale Diagrams over footer
« on: September 25, 2018, 12:58:02 am »
Hi Geert,
in my document templates I have defined headers and footers containing some meta-data.
As expected, my generated PDF’s always show the headers then the generated model content and last the footers.
The document generator manages how to scale diagrams and when to create page breaks to have the headers and footers visible at any page.
This worked for me all the time, but not for a college of mine.
The difference is that my diagrams are all in A4 landscape format but the format of my college is A4 portrait format. Problems occur on diagram more or less entirely filled (to the end of the “diagram page”).
In such cases, of an entirely filled A4 portrait format diagram, the PDF shows the header (so it is scaled somehow), but not enough, because it overlaps the footer (not visible any more).
It seems to me to be a bug, but maybe there is some workaround.

11
General Board / RTF Scale Diagrams over footer
« on: September 24, 2018, 08:14:13 pm »
When you render diagrams in rtf, those get somehow scaled to fit on a page. However when I have “long” diagrams those overlay my page footer.
Is there a way to avoid this?

12
Bugs and Issues / Re: State machine diagrams in EA 14 and 14.1
« on: September 19, 2018, 12:06:39 am »
I am also not happy with those changes, as I have stated in a post before. I have lots of SysML diagrams, and for SysML having a Frame is standard. Especially when having parameters in activities you need something anyway.
Over the years I used to put some context information on my diagrams as well. To clearly separate context information from the real stuff, I have the context outside of the frame.
Now I need to use some other mechanism to separate the real stuff from the context information. I am pretty sure, that I will find another solution, this is not the point, but the new solution causes me to review all my diagrams, regarding understandable layout, and if you have lots, you start thinking if it is worth to switch to a new version.
I get the feeling, that Sparx is trying to make EA more standard compliant and so it seem that adding new features is not the outshining focus any more (what would be good!).
For sure there are issues to address to make EA more complied with OMG. However regarding the inside/outside frame issue, the standard is not absolutely clear. But anyhow, I ask myself who gets a real benefit (not formal benefit like “I belief that it complies with OMG”) from this new solution.
I cannot see any benefit at all, but changing stuff lasting many years, typically have some impacts, and for me heavy bad impacts for nothing is not a good thing.

13
Hi Richard,
yes, due to the fact, that the UML specification is not always very precise in some areas one can come to this interpretation.
When using SysML, frames are standard. Both UML and SysML define frame names for different major diagram types (Class, Use Case, …). On the other hand both standards explicit allow having “mixed different kinds of diagram types” (whatever that exactly means).
The standard says nothing in such a mix, if a frame is allowed or not and if allowed how this should be handled. So, if nothing is defined, it is under the responsibility of the tool maker, to define a solution and the many years lasting solution is now changed.

For years, (in EA) the diagram was for me the whole pane what you see when you open the diagram. Now when you create a now diagram it is the pane you see, as long as there is no frame shown. If the frame is shown, it is not the pane anymore but the frame in the pane.
On the other hand when you link in a pane to another diagram, and you show that diagram as a frame your diagram is still the pane and not the frame. Just somehow odd.

My major issue is, that I have several standard SysML diagrams (having frame)  with some small amount of different type stuff.

Example: In activity diagrams it is hard to trace who catches a message sent and who might have sent a message catched.
In this cases when having a accept event message, I put the send signal messages defined somewhere else, outside the frame and connect send and accept by a trace relation.
This makes pretty clear what happens in the activity (what is in the frame) and what is just there to show relation to things outside (outside of the frame).
Now it is not possible to show this such explicit anymore and all those existing diagrams get grubby when updating to that version.

I know, due to other rendering changes on BDD’s, IBB’s, .. (e.g. compartment visibility), that I stitch to the point where I need to clean up almost any diagram after updating from V13 to V14.x. And when you have over thousand diagrams affected this issue becomes a show stopper.

14
Hi Richard,
what do you mean?
Do you mean, that if you have diagram frames, all stuff must be in the frame according UML2.5 or elements can be outside the frame as well?

15
Suggestions and Requests / Re: search via sql
« on: September 05, 2018, 04:37:39 pm »
When opening the link, I get a message that it is deleted.

Pages: [1] 2 3 ... 50