Comments
4 comments
-
That's a good point, it's a more common situation than we first hoped, so I think we can do something about how usable it is.
Thanks, -
Thinking about that dialog a bit more, perhaps the OK button is a bit misleading?
I would expect OK to dismiss the dialog after committing changes. If you add assemblies to be debugged then pressing OK actually takes you on to the next "page" of the dialog which shows the decompilation progress. (I think this is skipped if it's already in the cache, although something seems to flash by?) When that's done you have to press Close to dismiss the dialog. Therefore, in this case, OK doesn't do what I expect.
I wonder whether the dialog should follow the two-step model better, or if the progress could be added to the grid on the first page, or something else? -
We've fixed the usability when you have an existing pdb. Let me know what you think.
-
It's better, but not great. If you select multiple files in the file open dialog, or "select all" in the grid then you get a pop-up modal dialog with yes/no for every file. Each one has to be cleared with yes or no. At the very minimum a 'Cancel' or 'No all' option, but this doesn't tell me which ones are the problem.
Again, I have lost the state (the list of files I have added), so after deleting the PDBs I'll have to pick through the list to select them again.
Add comment
Please sign in to leave a comment.
The usability issue is that all I can do is to close the dialogue and then go back to the menu and bring up the dialog again (which takes some time), find the assembly in the list, tick it and then attempt the process again (after deleting the PDB file). Usability could be improved by:
Offering to overwrite the PDB, perhaps
Being able to return to the previous step in the dialog, so I can manually delete the PDB and then have another go