Image Capture and Auto-Resize With Cropper

Having talked about the pain of capturing image snapshots, someone mentioned Cropper and its plug-in model so I thought I'd have a bash at creating a plug-in to optionally re-size on capture. Using these helpful articles (here and here) on using the GDI+ System.Drawing classes to do image re-sizing I was able to pull something together pretty quickly. I modified the Cropper Clipboard Format plug-in to optionally re-size to a user specified width/height using InterpolationMode.HighQualityBicubic for image reduction.

Below are a couple of images created from a 1329x913 Alt-PrtSc image. The first using my Cropper plug-in and the second using Paint.NET (which uses its own custom re-sizing algorithms and doesn't rely on GDI+). I'm not sure there's much to choose between them so for my purposes the plug-in looks like it could be a good solution. The Paint.NET image is a little smaller at 255kb vs 263kb for the plug-in.

I should also mention that Live Writer *does* let you save image setting defaults (on the Image Properties -> Image tab at the bottom - highlighted on the Paint.NET image below). I'd never noticed that before...



Comments (4)
  1. Quite an interesting example on the UI for image cropping:

  2. I believe WLW uses bicubic high quality internally as well. We used to have really poor resampling quality but should be fixed in the RTM and later. Are you seeing significant quality differences versus inserting the capture at full size and letting WLW do the resize?

  3. MikeO [MSFT] says:

    Hi Joe. No, I haven’t seen any issues – that wasn’t the driver for me. I wanted to further automate the process, add high quality drop-shadow (I’m not that fond of the drop-shadow effect in WLW) and create something that can be used outside of WLW as well. So for me, a tool that captures, optionally resizes and optionally adds a nice dropshadow is ideal. Mike

  4. Today has not been a great day. Back here I talked about trying to improve my workflow for getting screenshots

Comments are closed.

Skip to main content