Missing standard edit shortcut accelerator

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hi all,

in the implementation of "CXTPSyntaxEditCtrl::PreTranslateMessage"
in release 12.0.1 the shortcut for "Cut" using "Shift+Del" is missing.
Only the other shortcut for it ("Ctrl+X") is implemented.
This is in contrast to e.g. "Copy" and "Paste" where for both
cases all both official shortcuts are implemented.

 It would be nice to change for the next release
    if (bCtrlKey && pMsg->wParam == (BYTE)'X')
into
    if (bCtrl && pMsg->wParam == (BYTE)'X' ||
        bShift && pMsg->wParam == VK_DELETE)

OK, in the meantime I have to somehow workaround this
with an ACCELERATOR table from the resource (like it is done in the
MDITextEditor sample), but for dialogs, etc. an own ACCELERATOR
table from a resource is simply ugly (and somehow superfluous
work, if it could already be in the standard).

So maybe it could be corrected for the next release, just to
have it correct out of the box.

Regards

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
peerschindel Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 12 July 2008 Status: Offline Points: 11	Post Options Post Reply Quote peerschindel Report Post Thanks(0) Quote Reply Topic: Missing standard edit shortcut accelerator Posted: 21 July 2008 at 10:09am
	Hi all, in the implementation of "CXTPSyntaxEditCtrl::PreTranslateMessage" in release 12.0.1 the shortcut for "Cut" using "Shift+Del" is missing. Only the other shortcut for it ("Ctrl+X") is implemented. This is in contrast to e.g. "Copy" and "Paste" where for both cases all both official shortcuts are implemented. It would be nice to change for the next release if (bCtrlKey && pMsg->wParam == (BYTE)'X') into if (bCtrl && pMsg->wParam == (BYTE)'X' \|\| bShift && pMsg->wParam == VK_DELETE) OK, in the meantime I have to somehow workaround this with an ACCELERATOR table from the resource (like it is done in the MDITextEditor sample), but for dialogs, etc. an own ACCELERATOR table from a resource is simply ugly (and somehow superfluous work, if it could already be in the standard). So maybe it could be corrected for the next release, just to have it correct out of the box. Regards