01-29-2013 02:43 PM
SAS/FSP was recently removed from the mainframe for $$$ reasons.
I am converting the FSEDIT code to a Windows XP platform.
The enduser (with no SAS skills) likes to cut-and-paste long text fields with a customized FSEDIT screen. With the 3270 emulation tool, it was very easy. With XP, I can get cut to work using ctrl-c, but I can’t find an easy solution for paste. The keyboard shortcut isn’t working (ctrl-v). I’ve played with the insert key too. Has anyone figured out how to get this to work?
I recognize that there are better options than FSEDIT, but the user is very comfortable with this method.
01-29-2013 04:05 PM
re: ctrl-c and or ctrl-v not working
Annoying problem if you rely 100% on keyboard shortcuts! I had the same problem and the fix is very easy. You will need to uninstall your keyboard driver and restart your computer and your CTRL keys will function once again. To do this:
1) Click Start
2) Control Panel
3) Printers and Other Hardware
5) In the Keyboard Properties window, click Hardware
6) Click Properties
7) Click Driver
8) Click Uninstall, click OK
9) Restart your Computer
01-29-2013 04:11 PM
Actually, I think it is an FSEDIT thing. The Windows "native" paste commands don't seem to work there.
You can get the function by mapping STORE and PASTE in your FSEDIT command window. With the FSEDIT window active, open the KEYS window ('KEYS' command will do it) and then map STORE and PASTE to the desired keys.
Also, you may need to apply the WNAVKEYUNMARK command per the SAS note I referenced.
01-29-2013 06:57 PM
Thanks for the quick feedback. Aside to Art: Ctrl-C and Ctrl-V works outside of FSEDIT, including SAS Display Manager.
I guess I forgot to add which version of SAS, which is SAS 9.3 TS Level 1M2.
The field itself is 160 characters and wraps for several lines.
Working from the SAS 9.1 problem note, the closest I got was a partial paste. Using MARK (XP ctrl-C worked too) and Store, PASTE (Ctrl-R) would only paste the first line. As already mentioned, the Windows Ctrl-V does nothing, although it should according to the Problem Note.
I will open up a trouble ticket,
01-29-2013 09:30 PM
01-30-2013 02:57 AM
Concerning the keyboard and a reinstall, we are talking about at least three machines (one laptop and two desktops) with the same behavior. I would have to get approval from another department for such a change.
I will put together a small fsedit program to mimic my example and post tomorrow.
02-07-2013 06:00 PM
Here is the code I promised last week... Reminder, the code cut-and-paste works on z/OS and not Windows.
libname screen 'c:\sas.fsp.screen';
if _n_=1 then long_comment=repeat('XY',80);
proc fsedit data=class_with_long_test screen=screen.longtext;
/* if you are interested in learning fsedit, see http://www2.sas.com/proceedings/sugi22/HANDSON/PAPER163.PDF */
Again, thanks for the comments,
01-30-2013 09:54 AM
I wonder if it is related to marking and non-markable area.
I know these are OUTPUT window but it may be a similar issue.