>>>Works nice.
>>>
>>>IMO the best here is to add a property "SmallChange", that will contain the STEP for updating the control. "LargeChange" will be used when user clicks on the TrackLine, and will give a bigger step.
>>
>>
>>I agree. I was just giving it a try until you have the Small/Large change properties done.
>>
>>I'm also working on the keypress code. I think it should work the same: Arrow key increments small change and PgUp/PgDown increments large change.
>
>
>
PERFECT !>
>
>>Have you decided on a property name for the max range and Small/Large change values?
>
>
>Sorry, but I didn't get what is the purpose of "MaxRange", can you better explain this to me ?
>
>
>I'll be offline from now on, I'll leave work now.
>In 2 hours I hope to get back into this.
>
>Please before going to bed upload your latest version, so that I can continue from there.
>
>TIA
>
>Cesar
Ok, I found a problem and have coded a simple solution.
Download the latest changes here:
http://www.geocities.com/kevin.marois/slider/xslider.zipOpen the control and search for the word "PROBLEM", and then the word "SOLUTION".
Also, see the code in MouseWheel and in txtFocus.KeyPress. Both are commented out, but I'd
like to get your opinion.
Everything makes sense in someone's mind
public class SystemCrasher :ICrashable
In addition, an integer field is not for irrational people