Spinner Jumps values

[bydesign]

Hello all

I have a spinner control that updates a textbox and calls a few subs from the spinner change event.

The problem is intermittent ... sometimes I can click one and the value will change by 1... other times it jumps 2 or 3...

I've tried different computers / mouses / people... all with the same results.

How would I limit a click to a value change of 1 while still maintaining the ability to hold down the mouse button for fast scrolling?

The code below is what I have... I've tried "DoEvents" between calls... no change in results...

spnPath_Change()

txtPath.text = spnPath.Value

Call Display_Path

Call Refresh_Form

end sub

 

[parry]

Hi, its unclear what you are scrolling through. Do you have SpinUp and SpinDown events as well? Perhaps it has something to do your called prcoedures - please post these.

 

[bydesign]

Parry, that's a significant amout of code to post... so I'll just give you the gist

spnPath_Change()

txtPath.text = spnPath.Value

Call Display_Path

Call Refresh_Form

end sub

txtPath.text is just a text box to display the spnPath.value

Dispaly path looks through all the sheets checking criteria... if it matches, the sheet is displayed

Refresh Form updates the userform based on the excel sheet that is now displayed... and enables, disables options based on sheet data


I have only used the change event... no others

I've also tried moving the code to the mouse up event

I suspect your thinking the same as me... something in one of the called events is causeing the problem... I've stepped through several times and I have not found what ever it is...

Since I can't find the actual problem, I'm going down the work around road... Thinking about a way to limit the value change by 1 unless the button is held down for 3 seconds??? I'm not sure how to approach this...

Thanks for your time.

 

[parry]

Im not sure what to suggest. I would change a few things in the refresh procedure as the way it repaints the form may make a difference. Perhaps you are clicking the buton before the search has completed and thats causing this. It may be better to have a command button that calls the procedures based on the spin value. An extra step for the user but it may avoid this problem.