Record navigation button speed

[Jim Stermer]

When using the record navigation buttons on the toolbar to move through records on the form, the toolbar button can keep up with the speed of quickly pressing the button. If I place a record navigation button such as (find next record) on the form, it will not respond to repeated presses of the button, you have to slowly press the button. Does anyone know how to make the form button behave like the toolbar counterpart.



Thanks


Jim

[forskare]

RE: Record navigation button speed

Jim,

I'm not sure it's the button. I tried this on my form and there is no difference in the speed. If you haven't already, try recreating the button.

kenn

[Jim Stermer]

RE: Record navigation button speed

Thanks for rersonding Kenn

I've tried it numerous times by using the Button Genie as well as using the Action scripts with a button. Either way if you quickly press the button, it will not advance the record everytime like the tool bar will. I have seen some posts here about Alpha not keeping up with keypresses.

FYI, the form name is Parts. The script Onpush attached to the form button is

:Parts.fetch_next()

My PC is a PIII 450mhz with 128meg. I don't think processor power is the cuprit.



Thanks again,

Jim

[forskare]

RE: Record navigation button speed

OK,

A couple more thoughts from this novice.

1. You differentiate a "quick press" and a "slow press". What do you mean by that? A click is a click. As soon as the mouse button or the key is released, the action is fired. In other words, how do you slow down the actual point of the contact with the click. It's like turning on a light. You can either move the switch slow or fast but when contact is made, the light's either on or off. Hmmmm. I've had too many of them off lately!

2. Have you tried a data base compact? That has solved a few wierd problems for me from time to time.

kenn

[Doug Chanley]

RE: Record navigation button speed

Jim,

I am not positive, but it may have something to do with the sensitivity
of your mouse. While your navigation button has focus, try pressing
the[ENTER] key...repeatedly & see if the button keeps up with the
enter key. If you adjust the double click speed faster for your mouse,
you may see some improvement in your button action with the mouse.

The script below is reported to be helpful if you are getting ghost buttons
when you repeatedly press a button....




''XBasic
ON ERROR GOTO error_handler

this.disable()
if eof()=.f.

parent.fetch_next()
else
end if
error_handler:
this.enable()
end

[Doug Chanley]

RE: Record navigation button speed

Jim,

I am not positive, but it may have something to do with the sensitivity
of your mouse. While your navigation button has focus, try pressing
the[ENTER] key...repeatedly & see if the button keeps up with the
enter key. If you adjust the double click speed faster for your mouse,
you may see some improvement in your button action with the mouse.

The script below is reported to be helpful if you are getting ghost buttons
when you repeatedly press a button....




''XBasic
ON ERROR GOTO error_handler

this.disable()
if eof()=.f.

parent.fetch_next()
else
end if
error_handler:
this.enable()
end

[Jim Stermer]

RE: Record navigation button speed

Thanks Doug,
I think you hit on the problem. The speed of the form button when using the enter key is accurate. When using the mouse, I loose some of the click actions. I increased the speed of the double click to max and it works properly but it's too fast to double click selections. Dropping the speed down one notch from max improves the action from the mouse but I still loose some click presses. It's still strange though that if you use the navigation buttons on the tool bar at the top of the screen, the mouse clicks work properly at any speed but when the button is put on a form, then there is this problem with the mouse.


Thanks again Jim

[Tom Scholis]

RE: Record navigation button speed

Jim, I have had the same experience across many machines of different types and speeds in many offices on different networks. For what it's worth, your not alone in the universe. I love the product but this one is a puzzle.

[Doug Chanley]

RE: Record navigation button speed

Jim,


As you say, fetching the next record with the mouse click on the tool bar syncs
up fine as does the enter key when used on the forms button......setting the
double click speed of the mouse improves the button action, but its still not
tit-for-tat.

I think that the problem is that the mouse button has 2 functions.... a single
click function & a double click function. Depending on your double click speed
& the speed that you click the button on your form you may notice that the mouse
pushes the button about half of the time. On the tool bar it pushes it every
time. The difference is that objects on a form use the double click function,
while the tool bar defeats the double click function.

An example would be in any field where the field rule sets the cursor at the end
or begining of unselected text. A double click in the field will select all of the
text in the field.

So your goal is to defeat the double click function of the mouse for your
buttons(only). I haven't messed with working out the details of doing this, but
I would start by looking for mouse events, I maybe even the OnKey event.

Good luck & post any positive results you come up with!

~doug

[forskare]

RE: Record navigation button speed

Just a thought, what kind of a mouse are you using and how long has it be "mousing"? Could it be that it's wearing out? After reading the last few parts of this thread, I remembered having a mouse do the same thing on a cad program, word processor, etc. I sent the mouse to the toilet and replaced it. Solved the problem. Ever watch a mouse swim in a toilet when it's flushed? Same principal, it's legs can only go for so long.

kenn

[Jim Stermer]

RE: Record navigation button speed

Thanks Doug.

I'll look into what you suggested.


Jim

[CharlesK]

RE: Record navigation button speed

My observations:

1. Both the toolbar buttons and user created buttons do not process the mouse click until the mouse button is released.

2. Watching a user button as I press and release the mouse button on it reveals that there is a considerable delay in redrawing the user button from the pushed to unpushed state.

3. Watching the toolbar button as I press and release the mouse button on it reveals that there is virtually no delay in redrawing the toolbar button.

4. In both cases, the record is fetched and updated on screen immediately upon the release of the mouse button.

I've tried this on two computers, two different brands of mice, with the same results. I believe it to be an optimization issue with A5's code for implementing user created buttons. The same thing happens if you try to click on A5's spin controls in any of their layout editors. If you click too fast, A5 misses some of the clicks.