Re: cuecat scanner prob: works in console but not in kde
On August 5, 2001 03:56 pm, David Aikema wrote: I was in kde when I first tried this and time and time again was annoyed to see the text cursor fly all over the place in kedit when I attempted to scan anything. Actually this seems to be the case with gnome as well. David Aikema ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc -http://linux.nf/mailman/listinfo/linux-users
Re: cuecat scanner prob: works in console but not in kde
On Mon, 6 Aug 2001 01:26:50 -0700 David Aikema [EMAIL PROTECTED] wrote: On August 5, 2001 03:56 pm, David Aikema wrote: I was in kde when I first tried this and time and time again was annoyed to see the text cursor fly all over the place in kedit when I attempted to scan anything. Actually this seems to be the case with gnome as well. That's with an unmodified cuecat? Interesting... -- ** Registered Linux User Number 185956 http://groups.google.com/groups?hl=ensafe=offgroup=linux 6:50am up 1 day, 7:26, 4 users, load average: 0.03, 0.43, 0.79 ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc -http://linux.nf/mailman/listinfo/linux-users
Re: cuecat scanner prob: works in console but not in kde
On Monday 06 August 2001 10:26, David Aikema wrote: bash-2.05$ cat /dev/null ^[[2~^[OD^[OA^[[2~^[[2~^[[2~^[[1~^[[2~^[[2~^[[2~^[[4~^[[2~^[OD^[[2~^[[2~^[[ 2~^[[2~^[[6~^[[2~^[OB^[[2~^[[4~^[[2~^[[4~ Doing the same in the console on another vterm resulted in the display of the actual barcode. Fairly typical. The keyboard encoding is coming in too fast for the gui app to handle, it's expecting 1 character every 15 minutes (at Kantoine's typing speeds). As a minimum, change your cmos to do something like 15 character look-ahead Ultimately, there should be, or might be, something you can tweak in the cuecat There's at least one pot on it to change the contrast sensitivity. -- http://linux.nf -- [EMAIL PROTECTED] _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc -http://linux.nf/mailman/listinfo/linux-users
Re: cuecat scanner prob: works in console but not in kde
On August 6, 2001 03:54 am, Jerry McBride wrote: That's with an unmodified cuecat? Interesting... The cat was modified to turn off decryption didn't feel like doing in software what could be done in hardware b/c it gets to be annoying when dual booting. David Aikema ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc -http://linux.nf/mailman/listinfo/linux-users
Re: cuecat scanner prob: works in console but not in kde
On August 6, 2001 05:05 am, Mike Andrew wrote: The keyboard encoding is coming in too fast for the gui app to handle, it's expecting 1 character every 15 minutes (at Kantoine's typing speeds). As a minimum, change your cmos to do something like 15 character look-ahead Hmn any aliases that I might find this in the bios settings as? I just got out of there and the only things I discovered that appeared to be keyboard related were a Gate A20 Option, which I just tried changing, and something regarding Typematic rates, which, it would seem to me would only apply if you wish to repeat a keystroke. Ultimately, there should be, or might be, something you can tweak in the cuecat There's at least one pot on it to change the contrast sensitivity. Hmn... will have to hunt around for something like that. David Aikema ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc -http://linux.nf/mailman/listinfo/linux-users
Re: cuecat scanner prob: works in console but not in kde
On August 6, 2001 10:53 am, Mike Andrew wrote: As an experiment only, you might try knocking out as many services and daemons as possible to pour the processing krunch into kde. It might not help one brass bit, but every indication is that the keyboard codes (not characters) are coming in too fast for a gui to handle. Linux does not use bios anything. Therefore all keycode translation is done by Linux. In the case of terms, they (generally) rely on the kernel itself whereas kde makes a meal of translating keystrokes into unicode before passing it thru an I18n (language) filter. In the case of konsole (eg) the reason why, it too, shows grabled characters is because kde is passing IT the char, because kde first needs to look for magic like alt F4 alt F2 etc. hmn... could this buffer setting be part of the kernel config then? You could also knockout gpm. It can be nasty it's monitoring chars for it's clipboard. gpm was one of the first things that I disabled. Point of sale readers generally have a binary that limits the character rate from them to the computer. I'll look at one tomorrow to see if it exhibits same behaviour and get back to you. Isn't there a windows app? that sets up this animal? The device operated fine in windows and, don't ask me why I forgot this (maybe I need more sleep or something), but the encrypted cuecat output spewed out fine into kedit so perhaps not a buffer problem after all maybe disabling the encryption also turned off some sort of charactern rate limitation set in the scanner. I don't think the windows app would have any effect on the use of this device in windows. AFAIK it simply picks up the output and tries to dig up something on the website. David Aikema David Aikema ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc -http://linux.nf/mailman/listinfo/linux-users
cuecat scanner prob: works in console but not in kde
On a recent foray of mine into the US I picked up a cuecat barcode scanner at a Radio Shack. I have since applied the modification to the cuecat so that it should spit out plain text instead of something encoded. I was in kde when I first tried this and time and time again was annoyed to see the text cursor fly all over the place in kedit when I attempted to scan anything. Then for some reason or other I switched to a console running on one of my other vterms and attempted a scan there which it performed flawlessly. I am still unable to scan any barcodes in kde(2.2beta) however. I opened a konsole window and tried something with the following results: (using a barcode from the back of Mr. Bandel's latest book as a sample) bash-2.05$ cat /dev/null ^[[2~^[OD^[OA^[[2~^[[2~^[[2~^[[1~^[[2~^[[2~^[[2~^[[4~^[[2~^[OD^[[2~^[[2~^[[2~^[[2~^[[6~^[[2~^[OB^[[2~^[[4~^[[2~^[[4~ Doing the same in the console on another vterm resulted in the display of the actual barcode. David Aikema ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc -http://linux.nf/mailman/listinfo/linux-users
