Re: CTRL-C issue

Buck,
I know I can "get around" this, but to me it's an issue. I shouldn't have to be that exacting when selecting rows for a copy. CTRL-C should be CTRL-C no matter where the cursor is positioned within the source member.
Greg

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck Calabro
Sent: Monday, January 26, 2015 3:31 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] CTRL-C issue

On 1/26/2015 3:01 PM, Greg Wilburn wrote:

I use mouse to select several lines of source code by click-n-drag... usually like this, and I'm usually copying from a blank row to another blank row (i.e. a block of code):


if shpr_nbr <> *blanks;
shpr_nbr = %xlate(lower:upper:shpr_nbr);
shpr_nbr = Txt_Scrb(shpr_nbr:digits + upper);
endif;

If during the click-n-drag, you release the "click" with the mouse cursor over the line sequence numbers (or very close to them), upon release you can see the cursor blinking to the left of the source line (with the text highlighted). If this is the case, CTRL-C will not copy.

9.1.1 behaviour confirmed.

Use Ctrl-Insert and the copy works. I couldn't suss out how to modify
the key binding to use Ctrl-C instead.

Right clicking the mouse and choosing Copy also performs the copy.