What steps will reproduce the problem?
1. Create a second form on the test project (TestApp or TestVb).
2. Mark the second form as a mdicontainer & the default form.
3. Open the original form, setting it's MdiParent to be the new second form
above.
What is the expected output? What do you see instead?
It appears the DefaultApplicationId is getting lost in the mix of the window
handle. I cannot figure out how to run it on a MDI Child form. This line
always returns a NULL DefaultApplicationId '_dataSourceManager = new
DataSourceManager(DataSourceManager.DefaultApplicationId, messageHook);'. I am
guessing it sees the mdiParent form's handle instead.
What version of the product are you using? On what operating system?
TwainDotNet source code 2011-12-22
Windows 7 64-bit
Please provide any additional information below.
It works fine on a regular form. Awesome project by the way!
Original issue reported on code.google.com by hol...@gmail.com on 4 Feb 2013 at 7:02
Original issue reported on code.google.com by
hol...@gmail.com
on 4 Feb 2013 at 7:02