Possible Bug in e_Key

[AudioSam]

I think this could be considered a bug....

I have a function set up using e_key to move an object.
When e_Key is pressed once the key event fires twice.
This means when trying to move the object one pixel it actually moves 2 pixels.

I checked it with a button set up with same function and it only moves one pixel.

Let me know what you find in checking this.

Thank You ,
AudioSam

[AudioSam]

After I checked the e_Key against a Button in the original app
I thought it was a bug.
I was going to make an apz file to show what it was doing.
With the same code the e_Key does not fire twice on the example app I was going to make.

Still I dont know why it worked correctly in the second example file and not the first app.

Sorry for not checking better before posting.

Thank You,
AudioSam

[Desolator]

You can't release the button fast enough so it counts as two key strokes. This can be tested using System.SilmulateKeyPress.

[RizlaUK]

Yes it is a bug, it has already been reported to IR

buffman and blue posted a workaround in the original post

http://www.indigorose.com/forums/showthread.php?t=18612

[SiNisTer]

Hey I noticed that bug too but only with a Dialog Message, and guess what...
I think the bug has to do with where you App is running from or rather from where the App icon is (i.e either Standard Taskbar, Tray, or Hidden...)
Is you App running from System Tray? cos, I was working on an project which displays a message when the user hits the 'Enter key' and it worked fine in Standard. But then when I changed it to run from System tray without changing a single code or any other setting, the message fire twice...That was sometime back and actually forgot about reporting it until I saw this post...

[AudioSam]

That problem was happening in an App.
I put the same code on the button with no double fire.
Then I posted the message.
I then thought ok, so that someone can look, I'll make an example.
I put all the code in the example.
Didn't change anything , but the e_Key worked fine then.
I know for sure it was fireing twice because I had it set to
show me in a label object.
The code was for one pixle over, yet it it was showing me two pixles
each time I hit any e_Key.

If your going to be around for awhile I will send you a pvt message.

Thank You,
AudioSam

[Buffman]

This bug has been fixed in the latest version (6.0.5.0)...

[SiNisTer]

I have to disagree on that mate, cos I initially picked up that bug while I was working on a project built with AMS 6.0.5. I am not aware of weather or not this bug lies in previous versions, but I now know for sure that it is still a bug in the currant version...and I personally think that this issue should be addressed and solved right away...