InfoPath Dev

Using opennetcf's mobile ink library, it became a simple task to include real INK controls in mobile apps using their managed code wrapper around the windows mobile ink api. Post here if anyone wants a knowledge transfer (no charge).  

What I've learned is that there is a difference and it is that the ink picture control contains pen state data. Without it being present in base64 encoded data, the inkpicture control won't render the image. I now have a way to include pen state data from my CF app and when placed back into Infopath, everything is OK.    

In Infopath 2003 SP2, can someone tell me why this base64 string renders OK in a picture control but not in an ink picture control? It's a 20px*20px GIF with a single black pixel in the center with all other pixels being white. R0lGODlhFAAUAIAAAAAAAP///yH5BAQUAP8ALAAAAAAUABQAAAITjI+py+0Po5y02osB3rz7D4ZBAQA7My XML file is below.  ...

Hi Patrick, Thanks for the welcome and your response.  I'm doing this project for a non-profit and funds are tight. My base64 representation of the GIF image data looks fine (image header and all).  Using dot.net, I can save the image data to a gif file and it looks fine in all of my graphics software.  Additionally, I ...

Hi, I have an Infopath 2003 form.  We've been using it with tablet pcs for awhile.  Recently, I wrote a "lite" version of the app using dot.net win mobile (6.1) platform for use on PDAs.  We use signature capture and the infopath form uses an ink picture control for it.  On my mobile app, I capture the ...