Standard design of Windows forms requires the use of tab to move from control to control, or use the mouse to jump to a control.
The top/left arrows move toward the beginning of text and the down/right move toward the end. They work in a similar way on drop down lists/combo moving up or down the list. I tested this on RRBYW demo and it is consistent with how my .NET apps behave. I did see that in RBASE you cannot tab past a drop-down, you must press enter to get to the next field. This is inconsistent with standard windows behavior and I can see how that could cause problems. While I personally do not like standard windows control behavior sometimes, (Probably because I'm ancient), sticking with the current standards as much as possible is an important UI consideration. I tell people, "That is the way all windows programs work, get used to it." People who are used to using windows programs will often be confused if you give them a non-consistent interface. It is better to stick with standard practice, and drag the curmudgeons along for the ride. Dennis McGrath -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Goldberg Sent: Friday, May 09, 2008 10:12 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: 7.1 to 7.6 The behavior changed when editing columns in a table somewhere between 7.1 and 7.6. I liked the old way but there was probably a reason to why they changed it. I have not figured a way to change it back. Maybe submit it as an enhancement. Dan Goldberg -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Lis Sent: Thursday, May 08, 2008 5:24 PM To: RBASE-L Mailing List Subject: [RBASE-L] - 7.1 to 7.6 I recently upgraded a customer from 7.1 to 7.6 and he asks: could you tell me why while in a table, I can not "arrow" from one cell to another after editing the cell, it makes me hit the enter key, then I can move to the next cell. 7.1 allowed me to do it. Is there a way to give him this request in 7.6? Bernie Lis
