User Rank: Newbie
Joined: 11/4/2009
Posts: 6
|
Would it be possible to add logging of information for LS_E_BadArgument to help determine *what* argument was invalid? Right now I'm trying to get a memory created BMP file from an NSBitmapImageRep using representationUsingType. I suspect I have "one-off" errors somewhere that's messing up the header and data memory buffers, or a problem with the header/data size parameters, but I have NO idea where. Some kind of console information put out when a BadArgument error is returned might be helpful. Although how much would depend on the internal workings of the host software. Printing out the header values from within PrintDisc or PrintPreview at the time the error was generated might be useful for debugging header problems.
|
