U++ forum: Welcome to the forum

Search on this site

Search in forums

Home » U++ Library support » ArrayCtrl, HeaderCtrl & GridCtrl » ArrayCtrl: Why editing row still needs Ctrl+Enter?

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

ArrayCtrl: Why editing row still needs Ctrl+Enter? [message #18798]

Tue, 21 October 2008 22:53

Mindtraveller
Messages: 917
Registered: August 2007
Location: Russia, Moscow rgn.

Experienced Contributor

Should plain clicking the row activate it`s edit mode with editor controls shown? I think average user won`t search for untrivial key combination to edit some cell...

I remember having met this issue about year ago when I was needed ArrayCtrl. Now I needed it again, used arrctrl.AddColumn().Edit(option) and found that it is still needed to push Ctrl+Enter to start editing. As it was year ago when we discussed this topic.

Please think of usability.
Not even to mention the case where app for touchpad console computers with no keyboard is being developed Smile

[Updated on: Tue, 21 October 2008 22:55]

Report message to a moderator

Re: ArrayCtrl: Why editing row still needs Ctrl+Enter? [message #18941 is a reply to message #18798]

Sat, 01 November 2008 23:39

mirek
Messages: 13975
Registered: November 2005

Ultimate Member

Mindtraveller wrote on Tue, 21 October 2008 16:53

Should plain clicking the row activate it`s edit mode with editor controls shown? I think average user won`t search for untrivial key combination to edit some cell...

It does. You just need two clicks (and not doubleclick).

I believe this is the same way as is used elsewhere (e.g. we have been completely inspired by Visual Studio behaviour back then Smile

.

Single click is problematic - you would not be able to move cursor without editing.

Mirek

Report message to a moderator

Previous Topic:	whanaction whenarrayaction
Next Topic:	GridTest

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Apr 19 15:37:02 CEST 2024

Total time taken to generate the page: 0.03626 seconds