CueCat output has bad first character
ForumCueCat questions and help
Melde dich bei LibraryThing an, um Nachrichten zu schreiben.
Dieses Thema ruht momentan. Die letzte Nachricht liegt mehr als 90 Tage zurück. Du kannst es wieder aufgreifen, indem du eine neue Antwort schreibst.
1rajid
When I use my new CueCat (just arrived yesterday) on my MacOS 10.6.5 system, it scans the code and produces the "jibberish" in the search window just fine, except that there's always one initial character, which shows up as a box. If I remove that character, then the search works. With the character, the search always fails.
Has anyone seen this? Is there a workaround?
Has anyone seen this? Is there a workaround?
2jjmcgaffey
Huh. It's probably the control character (Alt(Cmd)+F10 or something like that), which has been giving some people on Mac or Vista systems fits because it opens another program (a camera, a backup, something). I've never seen anyone say that it showed up as a character before, though.
The only workaround I can think of offhand is the one I always suggest - declaw/neuter your CueCat. Then it won't produce gibberish or control characters, just straight numbers. That makes it more useful elsewhere (outside LT), makes it easier to see what it's giving to the search, etc.
There's a Wiki page on declawing your Cat here, or Google 'declaw cuecat' and several dozen pages will show up.
The only workaround I can think of offhand is the one I always suggest - declaw/neuter your CueCat. Then it won't produce gibberish or control characters, just straight numbers. That makes it more useful elsewhere (outside LT), makes it easier to see what it's giving to the search, etc.
There's a Wiki page on declawing your Cat here, or Google 'declaw cuecat' and several dozen pages will show up.
