Buck,

Thank you for your verification of the issue. I am going to open a PMR for
it.

Regards,

Thomas.




Von: kc2hiz@xxxxxxxxx
An: wdsci-l@xxxxxxxxxxxx,
Datum: 07.05.2014 17:53
Betreff: Re: [WDSCI-L] CTRL+0 does not work for certain member
types
Gesendet von: wdsci-l-bounces@xxxxxxxxxxxx



On 5/7/2014 3:45 AM, thomas.raddatz@xxxxxx wrote:

Today I actually wanted to change the key binding of command "c-0"
(close
Lpex editor) from CTRL-0 to CTRL-W, which is the Eclipse default
mapping.
By chance I noticed that CTRL-0 does not work for all members types. For

example:

CRTL+0 works just fine for members of type RPGLE, RPG, CMD, CLLE and
CLP.

But CTRL+0 does not work for BAS, MNU, MENU, PNLGRP and of course our
special types MAKPGM and MAKSRV.

For sure I did not test all member types but the problem is clear:
CRTL+0
does not work for all member types.

Confirmed. 9.0.1, Windows 7.

And yes, it is always the Lpex editor that was used for loading the
members (CTRL+SHIFT+A "Open a member in Remote Sytsems LPEX Editor"). I
already restored the defaults for all key bindings and I resetted and
restored the LPEX editor profile with no success.

It does look like Lpex.

Can somebody confirm this "feature" or does somebody know what is wrong
with my RDi 9.0.1? RDP 8.0.3 shows the very same behavior.

Last but not least here are some details from Plug-in Selection Spy:

Active shell: Workbench Window
Active editor class: SystemTextEditor
Plug-in: com.ibm.etools.systems.editor
(9.0.1000.v20131010_1356)
Active editor IID: com.ibm.etools.systems.editor

Sure seems like Lpex. They must do different key bindings depending on
member type.
--buck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.