It would be useful to pin the debug image so that it does not disappear after one moves the mouse pointer out of the image window. That would make debugging easier as one wouldn't have to constantly Ctrl+hover the mouse over the image name. However, making the image not disappear as the default option is not a good idea in my opinion.
If multiple images were supported, one could choose and pin all the images he/she needs to watch during program execution. That would make debugging even easier.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I agree, this is indeed a useful feature. However, it is almost impossible to implement based on debugger evaluation add-in. You see, an image is accessed used a VS-generated structure, which persist only during the call to the add-in. I.e. when the text representation for a variable is formed. Even if I pass it to a some sort of dedicated process working in a separate thread, accessing this structure will most possible lead to a crash, since it is actually allocated for each formatting.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It would be useful to pin the debug image so that it does not disappear after one moves the mouse pointer out of the image window. That would make debugging easier as one wouldn't have to constantly Ctrl+hover the mouse over the image name. However, making the image not disappear as the default option is not a good idea in my opinion.
If multiple images were supported, one could choose and pin all the images he/she needs to watch during program execution. That would make debugging even easier.
I agree, this is indeed a useful feature. However, it is almost impossible to implement based on debugger evaluation add-in. You see, an image is accessed used a VS-generated structure, which persist only during the call to the add-in. I.e. when the text representation for a variable is formed. Even if I pass it to a some sort of dedicated process working in a separate thread, accessing this structure will most possible lead to a crash, since it is actually allocated for each formatting.