Robert Meek wrote: > Old habits die hard! I can't get my fingers to stop typing > apostrophes, but geesh, did everyone take a course in word and > sentence structure while I was asleep, cause all of a sudden, and > after at least 8 years on this list everyone is suddenly worried > about my possessive pronouns! <g> I could have sworn this was a > Delphi list!
I commented on it because it clearly wasn't a typo -- it was a consistent mistake made several times throughout the message. If I hadn't had anything to say about the actual subject of your message, I assure you I wouldn't have commented on your spelling, either. > In any case, I'm not sure you understood me because I don't know what > you are referring to when you say "invisible controls"! The controls on the other pages of the tab control. When the focus is on the last control on a page, you want the Tab key to switch to the next page and send focus to the first control on that page, right? > As I said, I'm not really worried much about the Tab key being able > to take the user from one Frame to another via the TabControl > component's Tabs, so for now at least I turned that ability off. If > it becomes a problem for heavy keyboard users I'll override the > method in a descendant and disallow the use of the Tab key in that > particular instance. But it's getting from the last control on any > Frame, all of which are parented by the TabControl to the two buttons > parented by the form that is causing me the problem. Visually, it > looks as if one should be able to continue tabbing from one to the > other, but it doesn't work that way, It doesn't? That's what I thought it did. Where does the focus go instead? I thought I understood what you wanted in your previous message, but now I've decided I have no idea. What was the default behavior in your program, how does it behave now, and how do you want it to behave? > If I add special handling to perhaps setfocus down to the first > button on the form when the user clicks the tab key from within the > last control of each frame that might do it but that solution just > doesn't seem to sit right with them either because it interrupts the > flow as one works his way through the pages of the wizard. If it's a wizard, then does it have "Next" and "Back" buttons? If so, then pressing Enter should do the same as pressing the "Next" button. That's not a double-key combination. -- Rob _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
