Re: [platform-debug-dev] Proposal for launch configuration API change

[Jared Burns <jared-eclipse@xxxxxxxxx>]

Commenting on the second proposal:

I think this makes a lot of sense. It's simpler (less options) and more 
convenient (less to do).

- Jared

> A related change in the launch configuration area is to get rid of the
> ability to launch a configuration without explicitly saving it.  At
> present, if a user launches a configuration that has *not* been explicitly
> saved, the configuration is available for relaunch via the F9 key or the
> history list, but is not available to be edited via the launch
> configuration dialog.  This means that if a user creates and explicitly
> saves a configuration, then at a later time selects that configuration to
> launch and makes a change to the configuration, the original configuration
> is intact and has not been overridden.  The changed configuration has only
> been saved internally.  The proposal is to change this behavior with the
> goal of reducing complexity.  The 'Save & Launch' button would be removed,
> and 'Launch' button would be understood to imply also saving the current
> configuration.  In the example above, this means that selecting an
> existing configuration to launch, but changing an attribute value before
> launching results in overwriting the existing configuration with the new
> attribute value.  If the user wishes to create a second configuration with
> the new attribute value, they must explicitly 'Copy' the original
> configuration and make the change.
>
> Any comments should be directed to this list in the next several days.