Re: Fwd: Plug-in changes for RDi 9.8 - Ctrl key Binding.

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Hi Craig

May I suggest that you submit an Idea for this? Then other of us could 
comment on it, vote for it, etc. And IBM would have something to 
consider - it's not typical for them to check these lists.

Regards
Vern

On 9/22/2023 1:46 PM, Craig Richards wrote:
> Apologies - looking at the default key bindings, I can see that with 9.8
> there are default key bindings for ctrl+pageup and ctrl+pagedown.
> I guess they weren't there in previous versions, but it explains the
> behaviour I was seeing (or not seeing...)
>
> Sorry, I should have looked more carefully before posting.
>
> It might be a nice enhancement when setting up a User Key Action to check
> for existing key assignments and disallow them.
> And/or to not simply fail silently where a duplicate binding exists.
>
> ---------- Forwarded message ---------
> From: Craig Richards <craig@xxxxxxxxxxxxxxxx>
> Date: Fri, 22 Sept 2023 at 17:47
> Subject: Plug-in changes for RDi 9.8 - Ctrl key Binding.
> To: Rational Developer for IBM i / Websphere Development Studio Client for
> System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
>
>
> Hi all,
>
> I've been struggling to get an old lpex extension plug-in to work with RDi
> 9.8.
>
> I could see that the plug-in was found but my assigned keystroke was doing
> nothing and there were no errors or warnings that I could find.
> (I had set up the User Actions correctly)
>
> I have been using ctrl+pagedown and ctrl+pageup since I wrote the plug-in
> but now they don't seem to be available.
>
> On a whim, I changed the User Key Actions to alt+pagedown and alt+pageup
> and it's all working again.
>
> As far as I can tell it's not due to a duplicate key binding as it doesn't
> appear in the log like ctrl+shift+a does.
>
> There is no warning when assigning ctrl+pagedown in the User Key Action
> (key c-pageup, correctly gets shown as Ctrl + Page Up)
>
> So, after wasting a lot of time trying to troubleshoot what might be wrong
> with my old plugin, it turns out that the plugin was fine, but
> something seems to have changed with the ctrl key binding.
>
> I thought it might be worth mentioning in case someone else comes across
> the issue.
>
> best regards
> Craig