As well I've taken to using the double-click to bring up a form. Secondarily I can bring up a different form using right-click eep.
-----Original Message----- From: "Brad Davidson" <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Tue, 24 Jan 2012 09:30:02 -0800 Subject: [RBASE-L] - Re: Limiting to Single Click: Listview Thanks, Larry, I’ll take this into consideration. It’s great to have the flexibility to meet ones expectations with a tool box of capabilities (ala R:BASE features)!Brad From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, January 24, 2012 9:23 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Limiting to Single Click: Listview I agree with Larry. Not all controls have a double-click eep, so I would avoid those and only use a control with a double-click eep to fire off another form. As Larry says, if you try to use the cursor keys or a pgdn/pgup, then it fires off a single-click eep as soon as you hit that cursor key. Karen In a message dated 1/24/2012 11:20:37 AM Central Standard Time, [email protected] writes: Personally, I don't think a single click on a list view should open another form. I only ever use the single click to update some detailed fields on the same form (and be aware that the single click EEP will fire when "arrowing" around the list view). I use the double click EEP to open another form. I find that this is much more in keeping with what users expect. I bet that's why your users are double clicking in the first place. If you were to implement this, my guess is that it would have the side effect of handling the double click at at the list view level anyway. -- Larry
