Hi Bob,
Since I mentored this implementation of concurrent states:
The original intention is, that when a concurrent region is selected, the
Delete button deletes the composite state that contains the region, and the
"Delete Concurrent Region" button just deletes the region.
All this was done in the presumption that for the user a concurrent state is
just another composite state with a dashed line in it. I.e. the user is kept
unaware of the creation/deletion of regions as separate UML entities.
Regards,
Michiel
----- Original Message -----
From: "Bob Tarling" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, May 02, 2008 1:18 AM
Subject: [argouml-dev] Why do we have ActionDeleteConcurrentRegion?
ActionDeleteConcurrentRegion seems only to be available as a visible
action from PropPanelCompositeState where it is used to delete the
CompositeState being displayed (if it is a concurrent region). But
there is also a delete model element button which will do the same
thing (and in fact reuses that same action).
Is there something I'm missing here? Can I just get rid of the
redundant button on that panel?
Bob.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
No virus found in this incoming message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 269.23.7/1409 - Release Date: 1/05/2008
8:39
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
