Re: Twain, Image Capture, Intel, PPC
Re: Twain, Image Capture, Intel, PPC
- Subject: Re: Twain, Image Capture, Intel, PPC
- From: Dave Camp <email@hidden>
- Date: Thu, 22 Mar 2007 20:12:41 -0700
On Mar 22, 2007, at 7:47 PM, Jim Mooney wrote:
After writing a nice app that uses the Twain framework, part of
image capture, I moved to a intel based powerbook for development.
Everything compiles but the twain portions are broken only unless I
use a PPC processor as the target binary. If I select PPC and
Intel or Intel solely, the app cannot find the twain source to
prepare an image capture.
I also found that if I use 10.4 sdk this is the only case PPC
version can see the twain source when compiling on an intel
machine. If I use what I originally designed for 10.2, even the PPC
version can see the twain devices to select the source on the intel
machine. I am sure I am not the only one who has this problem as
the twain.org forum has several posts of problems. No answers of
course.
Anyone run into this problem and know what is going on? At a
developer event, an Apple developer looked over the project and
thought it was a setting in XCode, but I have flipped every stone
over and spent enough time convinced something is broken with Twain,
Xcode, and Intel machines.(all part of image capture framework) It
appears the twain binary is compiled for intel, but I am wondering
what happens when a PPC driver for the scanner gets called? Could
this be the issue? Most of the drivers I have seen all look
carbonish.
While Apple may be providing an Intel build of the TWAIN DSM in Image
Capture (I assume they are, I have not looked), it won't do you much
good without the scanner vendors supplying Intel builds of their Data
Sources. Only a PowerPC app can load PowerPC bundles.
You can check the format of the various binaries involved with 'lipo -
info path/to/binary" from the terminal.
If your scanner vendor isn't updating their code for Intel, there
isn't much Apple or TWAIN can do about that. Be sure to let your
vendor know that their code isn't working. Many of them (at least the
lesser known brands) aren't terribly Mac savvy and may not understand
that it only works in Photoshop because Photoshop isn't native yet. :-(
I have given up on reporting bugs since they never seem to address/
consider bugs I post. ie NSMailDelivery big problems two years and
no answer or recognition ie case still open( yet since the case was
opened, three or four methods were removed from the class ).
It's hit and miss. I've had quite a few of the bugs I report fixed,
but never as many as I would like.
I am guessing this problem will never be address since everyone buys
a scanner, uses it a day and then chucks it. Call me a cynic but it
is a bummer when you want to move forward and 6 months of work gets
chopped and the viability of the app is in question. Does anyone
know if Twain will be supported (let's limit this to one year out)?
This is all in a Cocoa app.
The TWAIN DSM is a pretty thin layer and rarely changes (I worked on
the Mac 1.9 release years ago for them). 99.9% of the code for a
scanner is in the vendor supplied data source. It's up to the scanner
vendors to stay on the ball and keep their code up to date.
Dave
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
- Prev by Date:
Twain, Image Capture, Intel, PPC
- Next by Date:
Re: programatically resizing a sheet, visually from the bottom up
- Previous by thread:
Twain, Image Capture, Intel, PPC
- Next by thread:
Re: Twain, Image Capture, Intel, PPC
- Index(es):