On Wed, 2003-08-06 at 00:38, Karl Heinz Kremer wrote:
> I had to change the "-lqt" linker parameter to "-lqt-mt" in order to
> get working
> profilers. The Makefiles do use the environment variable QTDIR, so as
> long as this variable is set correctly, everything should compile
> without
> any pr
On Mittwoch, 20. August 2003 00:33, Matthew Duggan wrote:
[SNIPSNAP]
> Hi,
>
> For the canon_pp backend we received two types of calibration
> information: a gamma curve, the format of which we didn't quite
> understand (but it works good if you just feed it back to the scanner
> later), and light
On Tue, Aug 19, 2003 at 02:23:10PM +0200, flori...@gmx.net wrote:
> Hello!
>
> I have problems compiling iscan 1.5.2!
What sources did you download?
> What am I missing?
>
> My system is mandrake 9.1 sane is compiled (Version 1.0.12).
You'll need the gcc-3.x experimental sources. Either the t
This is a multi-part message in MIME format.
--=_NextPart_000_0035_01C3671E.A14131B0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi Stef,
I have made the changes to make the Custom gamma option state to active =
but still it is not workin
Hi,
On Tue, Aug 19, 2003 at 02:39:37PM +0200, Gerhard Jaeger wrote:
> I remember, that there once was a discussion 'bout saving backend specific
> data somewhere, but I could not find this discussion anymore.
> My problem:
> I'd like to save calibration data from the devices locally, so that it is
On Tue, Aug 19, 2003 at 02:39:37PM +0200, Gerhard Jaeger wrote:
> Hi there,
>
> I remember, that there once was a discussion 'bout saving backend specific
> data somewhere, but I could not find this discussion anymore.
...
> this will be my fall-back solution, but the better one will be to save th
On Wed, Aug 20, 2003 at 09:58:51AM +0200, Henning Meier-Geinitz wrote:
> I'd use ~/.sane/some_unique_name, or, if you need more than one file,
> ~/.sane/backend_name/some_name. Better don't use /tmp, at least if you
> can't make sure that someone else can do nasty things with your files
> (e.g. s
Hello,
I noticed that each backend defines an union like that:
typedef union
{
SANE_Word w;
SANE_Word *wa;
SANE_String s;
}
Option_Value;
Sometimes with fewer fields, sometime with more. Would it be a good idea
to have it declared once for all backends in only one i
