Re: setFocus() Win32Lib bug
- Posted by Irv Mullins <irvm at ellijay.com> Aug 09, 2001
- 388 views
> > If the cursor is on, for example, the 3rd position of a field and setFocus() > moves to another field then the cursor is on the 3rd position of the new > field. Is this not wrong? I would think that moving to a new field that the > cursor should be on the 1'st position of the new field. Is this a win32 bug > or am I wrong... Standard Windows behavior is to move to the first character position of the next entry field - IF the next entry field is empty.- Otherwise, it selects all the text in the next field, and places the edit cursor at the right end of that field. This is another Win32Lib bug, I'm afraid. Regards, Irv