Subject Re: SpeedTip followup From Lee Grant <camilee@nospam.comcast.net> Date Wed, 22 Feb 2023 13:42:48 -0500 Newsgroups dbase.getting-started Attachment(s) img2formstock.PNG Ken, Can't explain it. I just did a "? Set("EXACT")" check, ran it, clicked one to change from "LightGrey" to "Fuchsia", "Fuchsia" to "Lightgrey", and tried to click it again, and there was no visible change, and it stayed on the "Lightgrey" for the remainder of my clicks. Pic below to show where I was after the "Lightgrey" was in effect. I don't know why the difference. I can understand that Tom's hardware/software emulation of a Windows environment could cause a possible issue, but not mine.  I guess my version of dBASE 2019 isn't as good as yours. :) It's one of those things that makes dBASE Plus.....interesting? :) Lee On 2/22/2023 12:03 PM, Ken Mayer wrote: > On 2/22/2023 7:22 AM, Tom wrote: > >>> Lee is correct. Fixing the spelling of the second "LightGrey" in the >>> iif statement now eliminates problem #2 as the color change can be >>> executed multiple times. This code replaced the use of a messagebox >>> as a test for the functioning of the onLeftMouseDown function. Thank >>> you for the sharp eyes Lee. > > This may be a case of the status of SET EXACT ... in the Command Window: > > ? set( "exact" ) > > If it is "ON", then that would cause the issue shown. I just changed the > IIF() to use "==" (the "exactly equal" operator) and see the behavior > noted. However, if I just left it as is, EXACT is "OFF" on my machine, > and it worked fine ... (I just put it back, changed == to =, recompiled > the form, and yep ...) > > Ken > >