Sharing WISP Lite Ink with the Desktop

September 29, 2007 — 1 Comment

I just finished writing a new article on sharing ink data created on a windows Mobile 6 device using the Mobile Ink Library with a custom desktop application and OneNote 2007.

If you have used the Mobile Ink Library then you’ll probably want to know that I have made changes to the class library but I have marked methods obsolete to keep backward compatibility.  I’ve also posted the ‘technical overview’ of the Mobile Ink Library which is basically the same as the previous blog posts on WISP Lite and Mobile Ink Library but updated with the new updates.

Here are some screen shots on sharing ink with a custom desktop application:

And here are some screen shots on sharing ink data with OneNote 2007:

I have yet to update the SVN Repository but will update that in a couple of days.  I have update the installable source located here. 

I’m done inking for a while but the source is in a good state to be used in projects IMO.  I have been working on another open source project that will hopefully be released in the coming days plus a new commercial product so stay tuned!

One response to Sharing WISP Lite Ink with the Desktop

  1. Hi Mark,

    Thanks for your work on the mobile Ink managed wrapper and the excellent documentation and samples.

    I’ve been trying to use the library recently and have suffered frustration due to the "managed code" bug you mention in your blog.

    However the workaround you detail doesn’t really seem to be complete enough to overcome the bug in all situations.

    I am trying to do text recognition after writing over picturebox controls displaying an image when the mouseup event fires. I find that implementing your workaround helps, but doesn’t solve the complete problem. I find that it "works" every second time, but not all the time.

    Surely there is a "real" solution" to this problem in the managed code wrapper, rather than the ‘band aid’ fix that you are proposing.

    It works fine using C++ in unmanaged code, but who wants to program like that these days?

    Many thanks again for your excellent work – just hoping there is a better and more permanent solution available soon.


Leave a Reply