Attaching to 2 processes at the same time: only one seems to be remembered

[ashmind]

I attached to two processes at the same time using Debug -> Attach, but after I finished my debugging session, only one of them is available in ReAttach drop-down.

[erlandranvinge]

Yup, that's true. I think that's an overlooked story. I'll fix it, the reattach icon/dropdown should probably also be available except for the processes you've already attached to during "run"-mode. Also perhaps the ReAttach icon should always be enabled, but if you've got an empty history just open an ordinary "Attach to" dialog. To let newer users easier grasp how the extension is intended to be used.

[erlandranvinge]

I've been struggling with the UI on this one. First I thought of grouping processes attached in the same session together to make the user be able to ReAttach to multiple targets at once. But since you can add/remove attached processes (in the processes window for example) this did not end up as intuitive (with regard to add/remove targets) as I first thought. Now I've settled for a solution where all attachments made during the session are added to the history in reversed order (first attach also end up first in the history list). This way, when you ReAttach using shortcuts your first target is on top of the list, and you can easily reattach in the same order as your original session. This needs to be tested though. I don't want to ship anything that isn't easy and intuitive to use, and also want to keep the simplicity in ReAttach, i.e. no configuration/settings, it should just work as you might expect. I haven't been able to check in those changes yet unfortunately.

[ashmind]

I agree with your point. I should have made mine clearer: it is totally ok to have two separate records, the issue was just that second (third, etc) one was not recorded.

[erlandranvinge]

Yeah, that was the original issue, but my head spun off further into user experience and stuff. :/

[erlandranvinge]

Done as part of multi target support.