AutoHotkey Community

[Sephiroth2906]

We use a data entry system here at work that utilizes barcodes. I wrote a program that lets me scan a barcode with the wand that then puts it into the retrieval program without me opening that window, opens the image and resizes it, and it usually works just fine, but, sometimes it puts this:

0)))%(!*)d01

when it should have sent this:

000059180d01

into the retrieval program.

I attempted to put a shift up into the reload portion of the program in case that was the issue, but it does not help. Not that the output really looks like the shift key is pressed, but I cannot think of anything else. Any ideas?

[sinkfaze]

You probably just need to replace the errant characters before they're sent:

[Murx]

[TLM]

If Shift down is being sent inadvertently from somewhere other than the script, sending a ShiftUp may become unreliable.

You could watch the variable containing the incoming numbers for chr(#) 33-41 and simply remap them to #'s 48-57. Because the numbers are consecutively parallel, a simple math formula can be used to convert back to digits.

A simple function that finds and displays the character differences:

[Sephiroth2906]

[sinkfaze]

[TLM]

[[VxE]]

Shot in the dark:

[Sephiroth2906]

You know, I thought after the past few days everything was golden, but just now the script returned the shifted characters again, so the addition of sinkfaze's code didn't do the trick (that's a first for me ). So, any other ideas anyone might have would be most welcome. Again, I do not know why the leading zero and everything from the letter "d" on comes back unshifted or if it is even significant, but I am at a loss here.

I am going to throw VxE's code in there and hope, but it may be a couple of days before I can get a feel for whether or not it is working, because the stinking error is so darn infrequent and I cannot force it.

A semi-humorous, semi-sad aside,

I showed this to the elected official in charge of our office as a solution to a problem created by the new software that was purchased here. That was the first time I ever had this problem rear it's ugly head. *sigh*

Looks like I still have some work to do

[TLM]

Hey Seph..

Remember, sinkfaze's script was based on the static literal string

[Sephiroth2906]

[TLM]

Ahh I see, I look for that function.. ok
_________________
paradigm.shift:=(•_•)┌П┐RTFM||^.*∞

[Sephiroth2906]

Well, that didn't take very long. VxE's idea unfortunately also did not work either. Any other ideas you might be able to think of that I could try?

If it helps any, it seems to usually happen when I have not used the program for at least a few hours, say, the first time that day or when I have been performing other duties for several hours. It does not seem to make any difference if I have had the code running for all of that time inbetween.

Thanks!

[Sephiroth2906]

I just had the issue pop up again, and I discovered that there does not appear to be anything wrong with the variable itself, as the shift + portion of the script that resends the value has the characters come up just fine. So the issue looks like it is showing up only on the controlsend portion of the script.

Still fishing for ideas, if anyone has them

Thanks for all the help thusfar!

[sinkfaze]

Put the shift up directly in the Send/ControlSend statements?