At 17:12 2013-05-21, Ken Dibble krdib...@stny.rr.com wrote:
Why exactly this works, I have no idea. It does get gotfocus
firing again after the page activates though, and the code
executes properly. I sure hope that it does not break anything
else. I hate kludges.
I'm not following
In my findings of event firing order, I've noticed there is a difference
between using a mouse vs. the keyboard to navigate:
Text boxes on a form:
Keyboard :
TB1.Valid
TB1.LostFocus
TB2.When
TB2.GotFocus
Mouse:
TB1.Valid
TB2.When
Dear Vixens and Reynards:
Well, after a bunch of fumbling around, I came up with a
solution of sorts. It is a bonafide kludge with all that that
entails. I hate kludges.
In my page class, I added to the refresh method that if there
is an .activecontrol, then .setfocus() to it.
Why exactly this works, I have no idea. It does get gotfocus firing
again after the page activates though, and the code executes properly. I
sure hope that it does not break anything else. I hate kludges.
I'm not following this extremely closely. However, later versions of VFP
have
4 matches
Mail list logo
