Adam,

Thanks for the reply.  Yes, I think it would be great to have CuteEditor have a maximum image size (both file size and image size).  At the same time, I'd also appreciate a more "advanced" solution (or even a hint as to how I can do this) that would allow me to override whatever code CuteEditor uses to actually save the image (so that I can pass the image through the standard methods my application uses to save files). 

For example, I could write a class that inherits from the base class of the image selector page, then I could have the image selector page inherit from the new class.  In the new class I could override some method and therefore intercept CuteEditor's handling of the image. 

Chris