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.


Topics - Paolo F Cantoni

Pages: 1 ... 4 5 [6] 7 8 ... 76
76
Bugs and Issues / Virtualized Connector End not resizable
« on: May 16, 2017, 05:23:06 pm »
The virtualized connector end is NOT resizable.  However, it DOES track the width of the "meister" object, but not the height.

We found that his behaviour was JUST as annoying as not being able to resize at all!  Diagrams can be just as messed up by this...

This seems inconsistent at best.  I see no reason why the object shouldn't be separately resizable from the meister.

Reported,
Paolo

77
Suggestions and Requests / Alignment functions for Arcs
« on: May 16, 2017, 05:14:17 pm »
We have alignment functions for vertices (shapes), it would be really cool to have alignment functions for arcs.

Unfortunately, this would require multi-selection for arcs (which may not even be on the horizon).

If there's support for it, I can put in a formal feature request.

Paolo

78
In Movable? - In addition to Selectable and PrintableI (again -first mentioned in 2009!) talk about having the property Movable for vertices (shapes).  With the new line styles, it's now time to provide the same properties for arcs (lines).

In an enterprise situation, the diagrams can get very complicated.  It's really important to be able to "tie down" parts of complicated diagrams while another part id being worked on.

Reported,
Paolo

79
Bugs and Issues / Pinning ends and Line styles
« on: May 11, 2017, 05:10:10 pm »
I posted about being able to select a single segment of a multisegment line as the only part to move.

That got me thinking about the Pinning Ends problem.  It does seem (not fully tested) that pinning either end will change the line style to "Custom".  However, when that happens, the behaviour of the multi-segment line is different from the behaviour exhibited under the original line style.

It seems to me that some line styles have a "defined" pinned end (the lateral and tree ones for example).  So you can't change the destination end pinning.  However, even for these, the origin should be pinnable.  For the orthogonal styles, either or both ends should be pinnable.

Thoughts?  (before I submit a feature request)
Paolo

80
The newer line styles are quite useful.  I particularly like the "orthogonal" styles.  However, changing the line can be problematic. 

It would be really cool to be able to say "only change the segment I'm moving."  The other segments would not move (but only adjust with the change in the moving segment). 

For example, say you had a "U" shape.  If you moved the base of the "U", the uprights would not move, but merely get longer or shorter as you moved the base.  That is, the ONLY waypoints to change would be the ones on the moving segment.

Reported,
Paolo

81
General Board / Apple Mac, ODBC to SQL Server under Crossover
« on: May 11, 2017, 11:26:20 am »
<disclaimer>I'm like "Sergeant Shultz" when it comes to Macs - "I know nothink!"  :)</disclaimer>

We're trying to setup Sparx EA on a Mac and have got Sparx installed under Crossover on Wine.  We've got EA installed and some (very) quick preliminary tests on a local repository suggest it's working.  However, when we try to set up an ODBC connection to our SQL Server we get nowhere.  is there some "secret sauce"?

An ODBC connection IS required for connecting to a server based repository is it not?

TIA,
Paolo

82
The [F3] key is wonderful for quickly drawing repeated instances of arc metatypes from the toolbox on a diagram.

We have a LARGE number of arc metatypes in our MDG and so we wondered if we could use [F3] with an arc we'd just drawn with the QuickLinker.

We found that sometimes it does and sometimes it doesn't.  Some of the don'ts appear to be caused by EAUI (we have various Notelink based metatypes - and they consistently don't work - you just get an unstereotyped Notelink.  BTW: it works consistently when using the Toolbox arc).  But some just seems to be inconsistent - sometimes it will duplicate and other times, it will do nothing.

Does anybody know if the functionality is supposed to be orthogonal - that is it should work for both Toolbox and QuickLinker originated arcs?

If it is supposed to be the same anyone hav eany ideas why it might not be?

Paolo

83
I can guess the answer to this, but I'll ask anyway,

In the non-rectangular mode, you can define the area to be used for the vertex name using various spacer sub-shapes in a shape script.  However, these don't work in rectangular mode.  We have several widgets which expose vertex properties onto the vertex shape via shapescripting.  We need to expose these widgets in both views, but since some of them impinge on the vertex name area, it can get quite messy.

Is there any way to affect the sizing of the name area (analogously to the non-rectangular mode)?

Paolo

84
In a (fairly) recent post, I lamented the absence of User Specific Diagram Properties (which allow you to react in a Shapescript to a user selected value on a specific diagram).
In another post (today - 10-May) I liken these to conditional tagged values.

As I fired off that post, it struck me that there may be more to that analogy than may be first apparent.

Given that there are some issues with the existing implementation of User Specific Diagram Properties for vertices and a new implementation is required for arcs, it might be worth exploring the potential to "piggyback" on a lot of the Tagged Value functionality to make these properties more rigorous and consistent.  For example, TVs have types and controls for supporting those types.  We could add a property to the TV definition that makes it, say, active and thereby it would become a User Specific Diagram Property.

Thoughts?
Paolo

85
Can we get the width of the "Recent" section of the Start Page?  Quite a few of our descriptive file names are larger than the visible width.

In these days of large screens, there's no need to be so parsimonious.

Reported,
Paolo

86
Suggestions and Requests / Status for connectors
« on: May 02, 2017, 05:12:43 pm »
We're starting to miss being able to set a status on a connector.  For the moment, we are going to use a Tagged Value, but if it was a native function (and in particular, have a shapescript have access to getStatusColor()) that would be useful.

Reported,
Paolo

87
If you're in the Tagged Value Types dialog, don't try to change BOTH the Tag Name and the Definition and try to save the values, only the Name change will be updated, you need to go back in and change the definition AGAIN as a second step.

Reported,
Paolo

88
Bugs and Issues / Shapescript vs Local diagram rendering
« on: May 01, 2017, 05:16:07 pm »
I'm not sure that this is a bug so, before I report it, I'd appreciate any feedback.

There seems to be an inconsistency in the application of local diagram rendering versus Shapescript rendering.  I thought that Shapescripts provided the "default" rendering (for example - border/line color), but on an individual diagram basis, you could override that.

That no longer (if ever) seems to be the case.  The Shapescript takes precedence.  Can anyone "confirm or deny" which should take precedence?

Paolo

89
Bugs and Issues / Non-solid line doesnít get suppressed by label
« on: May 01, 2017, 05:03:34 pm »
For Associations, (which have a solid line), the label will "interrupt" the line and overlay the line so that the label can be clearly led.  With non-solid lines (such as "DASH"), this doesn't seem to be the case.

Can this be fixed, please?

Reported,
Paolo

90
As I've mentioned, we're maintaining our own MDG file outside of the Sparx provided mechanisms.

One thing we've thought about doing is to add additional properties (attributes) to the <Stereotype> section - this is to aid various automation and validation initiaives.  We added a new attribute (of our making) and EA didn't complain when we loaded the new MDG.
Code: [Select]
<Stereotype name="AbbrvtnOf" metatype="Abbreviation Of" notes="" cx="101" cy="70" bgcolor="-1" fontcolor="-1" bordercolor="49407" borderwidth="-1" hideicon="0" strictness="all" nature="Arc">
(See "nature" attribute)

We think we'll go ahead and give it a go.  Apart from the maintenance problem - which we already have anyway, are there any other downsides?

Paolo

Pages: 1 ... 4 5 [6] 7 8 ... 76