Sparx Systems Forum
Enterprise Architect => Suggestions and Requests => Topic started by: marcelloh on January 08, 2009, 11:08:19 pm
-
I know that ALT-F4 should close the application, but a warning message would be nice. I use ALT-4 a lot, and when I'm not focussed, I use the wrong keystroke.
Perhaps the nicest way, is an option-flag in the EA-options, that make the closing behave like it does now, or with an extra warning if a project is open (even if it's saved!)
-
Perhaps the nicest way, is an option-flag in the EA-options, that make the closing behave like it does now, or with an extra warning if a project is open (even if it's saved!)
Good point- I suggest to trigger a feature request at the Sparx support page.
Oliver
-
This is the requests & suggestions page, so why post it somewhere else?
-
Because posting here you are depending on someone at Sparx to read it and copy it over to the enhancement request system, but if you log the request it will flow directly into that system.
-
Aha, so posting in this forum has no use then?
-
No, that's not quite correct.
This is a user forum, so think of it as just that. Posting here is a good way to invoke discussion. Sometimes you will find other users have a viable workaround, or can add value to a suggestion based on their own experience or outlook.
The Sparxians are active members of this forum as well, and often participate in the above discussions. Sometimes they can shed light on why Sparx has taken a particular route in development of EA, other times they can provide answers we might not think of, given that they have an in-depth knowledge of the product internals.
By making a feature request directly to Sparx, you get the request into the queue for consideration. Even though it might not make the cut, Sparx will consider the request. That can be an important difference from a discussion here. Another reason for making a feature request is that multiple request for the same feature may increase the perceived (by Sparx) urgency of the issue. This might help a given request 'bubble up' towards the top of the list. In any given release of EA there has to be a cutoff on the number of changes that can be accommodated, so the higher the priority the better chance for a given feature.
Finally, it may help to link a feature request to a forum discussion thread. Doing so is a 'local' best practice some of us follow. This may help the Sparxians to link to the discussion of a given request. If many other forum members get involved in the discussion the request might be taken more seriously. It might also become more refined, in the forum, making it easier for Sparx to target a product update.
David
-
The Sparxians are active members of this forum as well, and often participate in the above discussions. Sometimes they can shed light on why Sparx has taken a particular route in development of EA, other times they can provide answers we might not think of, given that they have an in-depth knowledge of the product internals.
To be precise on some (rare) occasions Sparx has reacted on forum posts and took the initiative to file an internal feature request themselves or just implemented it.
But this is not the default way- it drastically increases your chances to be heard (and to make a long story short) one files that feature request.
Oliver
-
But, as noted, filing the request doesn't invalidate discussion here. In addition to workarounds and alternatives, one might find from the discussion that one didn't really want what one thought one wanted or one might realize that the current thought was only one piece of a bigger issues ... e.g, anything dealing with shapescripts.