sane-project-website/old-archive/1997-05/0154.html

109 wiersze
5.6 KiB
HTML

<!-- received="Tue Jun 24 17:34:47 1997 MST" -->
<!-- sent="Tue, 24 Jun 1997 17:27:39 -0700" -->
<!-- name="David Mosberger-Tang" -->
<!-- email="davidm@azstarnet.com" -->
<!-- subject="Re: sane compile probs with gtk" -->
<!-- id="199706250027.RAA08303@panda.mosberger" -->
<!-- inreplyto="5opme7$qf3$1@dumbo.und.zoff" -->
<title>sane-devel: Re: sane compile probs with gtk</title>
<h1>Re: sane compile probs with gtk</h1>
<b>David Mosberger-Tang</b> (<a href="mailto:davidm@azstarnet.com"><i>davidm@azstarnet.com</i></a>)<br>
<i>Tue, 24 Jun 1997 17:27:39 -0700</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#154">[ date ]</a><a href="index.html#154">[ thread ]</a><a href="subject.html#154">[ subject ]</a><a href="author.html#154">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0155.html">David Mosberger-Tang: "Re: xscanimage - how to make device default"</a>
<li> <b>Previous message:</b> <a href="0153.html">Christophe Zwecker: "xscanimage - how to make device default"</a>
<li> <b>In reply to:</b> <a href="0152.html">Michael J. Long: "Re: Microtek E3 Scanner Support"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
<i>&gt;&gt;&gt;&gt;&gt; On 25 Jun 1997 01:49:27 +0200, <a href="mailto:doc@rrz.uni-hamburg.de">doc@rrz.uni-hamburg.de</a> (Christophe Zwecker) said:</i><br>
<p>
Christophe&gt; 1. How can I invoke xscanimage from within gimp (btw<br>
Christophe&gt; could it be that gimp is kind of unstable right know? I<br>
Christophe&gt; somehow don't have the Gimp manpage, and in xscanimages<br>
Christophe&gt; manpage it says nothing...<br>
<p>
The forthcoming xscanimage man-page has the following section. If<br>
it's not clear or needs some other fixing, please let me know so I can<br>
correct it before sane-0.61 comes out.<br>
<p>
----<br>
RUNNING UNDER THE GIMP<br>
To run xscanimage under the gimp(1) , simply copy it to<br>
one of the gimp(1) plug-ins directories. If you want to<br>
conserve disk-space, you can create a symlink instead.<br>
For example, the command<br>
<p>
ln -s /usr/local/bin/xscanimage ~/.gimp/plug-ins/<br>
<p>
adds a symlink for the xscanimage binary to the user's<br>
plug-ins directory. After creating this symlink, xscanim-<br>
age will be queried by gimp(1) the next time it's invoked.<br>
From then on, xscanimage can be invoked through<br>
"Xtns-&gt;Acquire Image-&gt;Device dialog..." menu entry.<br>
<p>
You'll also find that the "Xtns-&gt;Acquire Image" menu con-<br>
tains short-cuts to the SANE devices that were available<br>
at the time the xscanimage was queried. For example, the<br>
first PNM pseudo-device is typically available as the<br>
short-cut "Xtns-&gt;Acquire Image-&gt;pnm:0". Note that gimp(1)<br>
caches these short-cuts in ~/.gimp/pluginrc. Thus, when<br>
the list of available devices changes (e.g., a new scanner<br>
is installed), then it is typically desirable to rebuild<br>
this cache. To do this, you can either touch(1) the<br>
xscanimage binary (e.g., "touch /usr/local/bin/xscanim-<br>
age") or delete the plug-ins cache (e.g., "rm<br>
~/.gimp/plug-ins"). Either way, invoking gimp(1)<br>
afterwards will cause the pluginrc to be rebuilt.<br>
----<br>
<p>
Christophe&gt; 2. is that bad that whenever I scan I get this in<br>
Christophe&gt; messages: Jun 25 01:36:55 dumbo kernel:<br>
Christophe&gt; ncr53c810-0-&lt;target 6, lun 0&gt;: extraneous data<br>
Christophe&gt; discarded. Jun 25 01:36:55 dumbo kernel:<br>
Christophe&gt; ncr53c810-0-&lt;target 6, lun 0&gt;: COMMAND FAILED (9 0)<br>
Christophe&gt; @00ffe018.<br>
<p>
No, that is "normal" with the ncr810 driver. The line-distance SCSI<br>
command is causing this, but I'm not sure why. It is the reason there<br>
NEED_MUSTEK_LINE_DISTANCE_WORKAROUND exists in the mustek backend. I<br>
noticed that this workaround is not necessary under OpenStep. Has<br>
anybody with a SCSI controller other than the ncr810 or on a non-Linux<br>
platform tried configuring with option --disable-ld-fix and had<br>
success with scanning color images? If so, I'd like to hear about it.<br>
<p>
Christophe&gt; oh, and I noticed that in the preview window and in GIMP<br>
Christophe&gt; itself aswell thw picture kind of gets broken and pieces<br>
Christophe&gt; move around abit, the pic gets mixed up. Is that due a<br>
Christophe&gt; buggy gtk ? Has anybody else experienced that ?<br>
<p>
Not that I'm aware of. If the problem is serious, maybe you could<br>
capture a snapshot that shows the problem and send it in (don't make<br>
the snapshot too large, though...).<br>
<p>
Christophe&gt; ok thx for sane anyways - I love it<br>
<p>
Nice to hear! ;-)<br>
<p>
--david<br>
<p>
<pre>
--
Source code, list archive, and docs: <a href="http://www.azstarnet.com/~axplinux/sane/">http://www.azstarnet.com/~axplinux/sane/</a>
To unsubscribe: mail -s unsubscribe <a href="mailto:sane-devel-request@listserv.azstarnet.com">sane-devel-request@listserv.azstarnet.com</a>
</pre>
<!-- body="end" -->
<p>
<ul>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0155.html">David Mosberger-Tang: "Re: xscanimage - how to make device default"</a>
<li> <b>Previous message:</b> <a href="0153.html">Christophe Zwecker: "xscanimage - how to make device default"</a>
<li> <b>In reply to:</b> <a href="0152.html">Michael J. Long: "Re: Microtek E3 Scanner Support"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>