Re: SSTab and TabStop Issue
- From: "The Merg" <howard_mergler@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 21 Mar 2006 21:18:02 -0500
Okay, it's kinda working now. However, if I just run my app, it will not go
to tab 1 from the last field on tab 0. If I put a stop point in the
FindControl function at the spot that it is setting the focus to the first
field on tab 1, it will change to tab 1 and set the focus correctly.
Does that make any sense?
- The Merg
--
Today's problems don't worry me,
I haven't solved yesterday's yet.
"Bob O`Bob" <filterbob@xxxxxxxxxxxxxxx> wrote in message
news:%23ls1Gb6SGHA.1160@xxxxxxxxxxxxxxxxxxxxxxx
The Merg wrote:
When I looked at your code, you seemed to use the frames in order to
dynamically determine the next or previous control for when the tab key
is pressed. As I only had two tabs, I just hardcoded in which control to
move to next (or previously) using the SetFocus method after switching to
the appropriate tab. Should or could that be causing the problem?
The frames are simply necessary.
The SSTab control has numerous quirks and a few bugs, and insuring that
each
tab has exactly one container control and nothing else [directly] on it
overcomes just about all of them, with zero further effort required.
Just Put The Frames In.
Bob
.
- Follow-Ups:
- Re: SSTab and TabStop Issue
- From: Ken Halter
- Re: SSTab and TabStop Issue
- References:
- Re: SSTab and TabStop Issue
- From: The Merg
- Re: SSTab and TabStop Issue
- From: Ken Halter
- Re: SSTab and TabStop Issue
- From: The Merg
- Re: SSTab and TabStop Issue
- From: Bob O`Bob
- Re: SSTab and TabStop Issue
- Prev by Date: Re: CommonDialog sets Windows Default Printer - is Mike Williams out there?
- Next by Date: Re: SSTab and TabStop Issue
- Previous by thread: Re: SSTab and TabStop Issue
- Next by thread: Re: SSTab and TabStop Issue
- Index(es):
Relevant Pages
|