v11 diagram konsistency and functionality

[skiwi]

• while a Note element can be linked to a connector a Text element cannot.

thus a Text element  cannot use features such as linked to connector tagged values

• how about allowing "Link to Connector Note"
• using a tagged value (_Bezier) to control element behaviour is wrong, it confuses business information with configuring the product.

If this is going to be the case at least let us multi-select the tagged values to be displayed, or mark some tagged values as never to be displayed.
[/list]

[skiwi]

How to change the order of constraints?

[Eve]

Great. Another random list of unfiltered wishes.

Text and Note elements are intended to be different things, why should they have the same functionality?

Linking to a connector note has been worked on but isn't ready for release.

The bezier tag on a connector is there so that a profile could set that as the style for its connectors. I don't think the idea was ever that it would be used to set the style for individual connectors, but it has provided a way around the restrictions that are otherwise in place. So I agree, it's not the way it *should* be done, but it's there.

Constraints are an unordered list, which I take to mean that ordering has no significance. Although it appears to be sorted on name for some consistency.

Regardless, there is no field available to provide a customizable ordering.

[skiwi]

Thanks Simon, how would you suggest we filter and order our wish lists.

I agree text element is different from note, but why should it not have the same functionality.

In fact why have two different elements at all, they could be one and the same if Note could be configured with a 0 width border, and transparent background.

Any why should constraints not be ordered. The control is already used in EA in many places. This could been one less control to maintain and support.

I'm simply trying to diagram a model, and am stymied by the seeming random allocation and implementation of features, for example, check the colour dialogue for a swimlane

well how about these, its hard sometimes to select a consistent colour

[skiwi]

Copy a note that has a link to a connector.

Paste as new - deselect the "include connectors" tick box

New note is created with link to connector!

Bug? or Feature?

[qwerty]

Great. Another random list of unfiltered wishes.

As I see it skiwi is very eager to wrap up wish lists in threads and not have them scattered around. <rant> What I also see is that Sparx spits out a lot of rather useless buggy features while not respecting user requests over many, many years. </rant>

q.

[skiwi]

Great. Another random list of unfiltered wishes.

You know, on reflection, a better response might have been:

"Great. Another customer likes our product so much they want to put the time and effort into suggesting how our product or services could be even better"

or

"Great. Gosh, wouldn't it be better if we could provide a means for our customers to suggest, discuss, and prioritise their wish list."

and

" I wonder how quickly we can tell our customers (both those who contributed to the suggestion, and those who might be interested in product enhancements) what we are going to do about this suggestion"


While there is good support on this forum, and through the website support channels, there is, I think Mr G Sparks, an opportunity to be more appreciative and supportive of your customer community.

[Eve]

"Great. Gosh, wouldn't it be better if we could provide a means for our customers to suggest, discuss, and prioritise their wish list."

Yes, my initial response was perhaps a little inappropriate.  You are in a forum provided by sparx systems. They board you're posting on has the description "Suggest and discuss, with other users, features you would like to see added to Enterprise Architect. To submit a request for a feature or facility directly to Sparx Systems, use the Feature Request link at the foot of this page."

So that response is exactly what we have already given. The problem is that time and time these threads pop up. Because they are a scattering of unrelated thoughts there's no effective way to discuss them. Then what happens is that for a few months every second request is responded to with a link to the thread that in many cases the only significance is that there are lots of other requests.

As I've said before. We don't have the resources to implement every suggestion, and some suggestions are simply not the direction that we want to take Enterprise Architect. I read your requests, I try to offer assistance where I can. But personally I find that this type of list impedes any discussion in multiple ways instead of aiding it.

[RoyC]

In other words, would you be so kind as to limit the content of a post or thread to discussion of ONE proposed feature? Please? I have added this point to the 'Suggestions and Requests' board description. It does make it a bit easier to talk about and cross-refer to the feature in question.

Great! Another customer likes our product so much they want to put the time and effort into suggesting how our product or services could be even better. Thank you!

[qwerty]

In other words, would you be so kind as to limit the content of a post or thread to discussion of ONE proposed feature? Please? I have added this point to the 'Suggestions and Requests' board description. It does make it a bit easier to talk about and cross-refer to the feature in question.

Great! Another customer likes our product so much they want to put the time and effort into suggesting how our product or services could be even better. Thank you!

I read that with astonishment :-? If there were one thread per wish it would most certainly go down the gully. There are a couple of skiwi-compiled threads that have a common title "Consistency". I gave that up long ago (in times when CCC-Paolo still posted regularly). skiwi obviously still has not and he has my full respect for that.

Sure, things could be worse and there could be no forum at all. But things can always be improved.

q.