"sasha mal" <[EMAIL PROTECTED]> wrote: > What you are saying is that it costs too much to fix the slowdown and > my solutions are not good because of some reasons I have no idea of.
What part of "what you propose is going to induce horrible side effects for the frontends and it's not portable accross all the platforms supported by SANE" don't you understand ? > However, having or not having time resourses on your side is > absolutely irrelevant to the question whether something is a bug or > not. Again, what part of "if this can be fixed it'll probably require a massive amount of work and redesign of the current SANE architecture, and it's definitely not worth it" don't you understand ? > Don't tell me that you want an A4 page to be scanned in 20 minutes if > a slightly You can't expect a parport scanner to be fast, because the parport is dogslow to begin with anyway, and these scanners are nothing more than gross hacks. > You see, I would even spend a couple hours on hacking the code if I > (1) could get support in terms of explanation and (2) knew exactly > the time to spend on it, but (3) your minunderstanding made this > definitely impossible. Read the code, read the SANE standard, identify and get to know all the SANE frontends, identify all the platforms supported by SANE, read up on your proposed solutions and get a clue all by yourself. I know what you propose won't work, I know it's not worth the effort, ergo I'm not spending any more time on that. JB. -- Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
