Community
Participate
Working Groups
I20030113 I first thought there's a severe bug in Debug: after importing the latest build and clicking on the Run (and later Debug) buttons in the toolbar nothing happened, no UI feedback and the Debug view was empty. I then remembered that I recently chose to always wait until a build is finished (Debug preference). Going to the Process view I saw tons of Launch jobs waiting. There needs to be better feedback. I suggest to show those launches in the Debug view.
Consider showing launches in progress in the debug view.
Fixed in DebugUIPlugin by adding a dummy launch during the join. Please verify, DarinW.
This is a good start. I'd like to get the label improved, or warn the user when they attempt re-launch a config that is already waiting for a build.
The launch shows up in the debug view immediately, so I don't think we need to warn (harass?) the user any further in this case. I'll look into the label, but I'm not very optimistic given the way the framework works.
I agree with Jared that a warning dialog would be a pain and I agree with Darin that there has to be some indication in the Debug view (icon and label).
Fixed in DebugUIPlugin. I now copy the config in memory to create a working copy with a name that includes "(waiting for build to finish...)" and use that config in the placeholder Launch. Please verify, DarinW.
Verified.