Great tool! Bug: debugging from VS2015 with platform toolset VS2013 in Image Watch it states [invalid] for an image which is correctly displayed when debugging from VS2013. If platform toolset is VS2015 everything works OK.
THE best and most amazing plugin ever! Makes coding so much more productive, and more fun as well.
If you want one suggestion on what to improve, I'd say @mem(...). I don't needed it often, but when I'd need it, I most of the time can't get it to work. It's kind of documented, but I'm never sure: Do I put in the name of the variable? or '&variable'? or the address? or the address with 0x...? or...? and more often than not it's not working, and also not printing any error/debug information.
I think what would be useful as well is a small button that opens a menu that shows all the operators you can use, and their syntax - like a small documentation inside.
But those are just some tiny suggestions. It is incredible as it is!
This is indeed a game changer! Debugging in-memory images has always been so hard in VS. The simple power of Image-Watch visualization, combined with the efficient operators can turn hours of debugging to minutes or seconds.
I've been using Image Watch for quite time without any problems in all my OpenCV projects. However, now in one of them it is showing [invalid] for the vast majority of my matrices without any obvious reason (such matrices are of course not invalid at all). Reinstalling didn't work, and I also don't know why some of the matrices still show perfectly (though they're just a few). Are there any know issues or steps to try to troubleshoot this? I've found it difficult to get info about such problems and/or possible incompatibilities. Any help/suggestion would be greatly appreciated
I am using image watch with opencv 2.4.10 and vs.net 2013.
every thing was good. However, it stopped working and I do not know why. it always shows [invalid] I delete it and reinstall it but nothing happened. I even re-install vs.net but it still [invalid].
what could it be ??
I just found this awesome plugin ant it'll save me a lot of time while debugging my programs.
I have a question though, is it possible to display raw image with 1-bit per pixel (monochrome black and white) using @mem ? And if so, how ?
Would it be possible to setup Image Watch to get memory dumps from nsight as well as from cdb?
I tried making a debug visualizer for a cv::cuda::PtrStepSz<cv::Vec3b>, Image Watch detects the type and tries to visualize it, but it looks like it isn't correctly getting any information from nsight.
It's a great tool for debugging my program.
I have a problem though. The image variables that I see in the window are displayed in a seemingly random order. How are the variables ordered? Is it possible to view the image variables in an alphabetical order?
This extension has potential to be very useful to me. However, I don't have objects that represent pictures; I only have pointers to raw data (such as uchar *), paired with variables that hold width, height and stride.
It would be great if you could add possibility to look images in a generic way - add another radio button which will show fields that could be manually edited (picture address, width, height, stride, format).
Hi! Update 1.0.1071.0 (April 2014) introduced the @mem operator to support this scenario. It is described on our help page under "Image Operators". Let us know if this isn't what you were looking for, or if you run into any problems with it. Thanks! -Wolf
we are amazed by this extension and would like to thank you for your hard work!
We have a small wish however:
Due to the great extendability via natvis we were able to quickly visualize our internal image. Unfortunately the origin of this internal image format is bottom left instead of top left. This leads the the images being displayed bottom up in the Image Watch.
Would it be possible to add some feature to be able to configure the visualization in the natvis for such flipped images? We could imagine e.g. a dedicated flag or maybe a negative stride?
Please do not mind if such feature already exists and we couldn't find it :)
Thanks in advance!
thanks very much for your feedback! You are right, the feature you are mentioning does not exist at this time. And I agree that it would be very useful to have. I'll add it to our TODO list for one of the next updates.
Oh, I see from the help that I got to through the Image Watch window shows that the image types that this plug in has support from are not WIN32 objects. Forget it, this isn't what I'm looking for. I don't think the Extensibility section will allow for this either. :(