|
|
Post by Colin on Jul 3, 2013 18:41:00 GMT -5
Just started using SPFLite (and it is fabulous. Thanks! 30+ years of ISPF time, so I feel at home. Yes, I will donate.)
Environment -
Win XP - SP3
SPFLite 7.0.3177
VMWare Fusion 5.0.3
Macbook Pro i5, 8GB
OSX 10.8.4
Action -
Editing new or existing text file, pressing 'W' jumps to next line.
Diagnosis -
Finally checked KEYS and discovered all letter keys were (PassThrough) except the 'W' which was (NewLine)... Changed and all is normal.
Comment -
I had just installed and started using SPFLite and not changed configuration (other than the initial options review, but no changes).
If this isn't how it was intended to ship, I thought I'd give a heads-up. If it was something inadvertent on my part, tell me what to check.
|
|
|
|
Post by George on Jul 4, 2013 11:23:09 GMT -5
Hi Colin,
This was a bug way back in the 6.2 release. (A typo, but nonetheless, a bug) which I corrected (or so I've thought all along).
Which option did you choose on the default keyboard pop-up A, B or C?
Robert passed this on, and I just finished testing this over again, and it SEEMED fine, but obviously something is rotten. Any extra info is appreciated.
George
|
|
|
|
Post by Colin on Jul 4, 2013 11:51:14 GMT -5
Hi George,
I don't recall the choices in A, B, or C. Where could I look to see those choices, to refresh my memory?
I originally downloaded the CNET version (which brought the bloatware), started it (which popped the initial options setup), then checked for updates and got the current. Possibly the update didn't replace the existing options?
All I have changed in options (since install) was the edit on key 'W'. Anywhere you'd like me to look I'll be happy to oblige.
Good work!
Colin
|
|
|
|
Post by George on Jul 4, 2013 12:07:07 GMT -5
Hi Colin,
Hmmm, I'm trying to remember just when I fixed the W bug. I know it was late in the 6.2 life cycle and I'm wondering if the version you got from CNet was old enough to still have the bug. Once you corrected the key mapping, and them moved on to a 7.0 version, you'd never see that initial choice pop-up again, since SPFLite would recognize your existing INI and KBD files. That would also explain why my testing with the 7.0 release all worked fine.
Maybe I never uploaded the corrected 6.2 version to CNet because the release of 7.0 was so close, and the bypass to correct it was so simple.
.
.
I just went and checked the Change log. Yes, the W fix was never released in 6.2, the first one was the 7.0 release.
Mystery solved, and the current 7.0 release is fine. Whew!
George
|
|
|
|
Post by Colin on Jul 4, 2013 12:39:08 GMT -5
Hi George,
Glad to hear it is no longer a mystery. SPFLite is certainly making my life easier. Thanks!
Just to be sure, should I uninstall/delete the 7.0.3177 I'm using, to eliminate what seems to have been old 6.2 configuration file content? (Assuming that the new install didn't replace it, which is why I had the key problem.) Is there anything else that might be suspect?
Thanks again!
Colin
|
|
|
|
Post by George on Jul 4, 2013 12:44:46 GMT -5
Hi Colin,
No, there's nothing you need to do. You're just fine as you are.
All that happened was that the very initial run of SPFLite mucked up the W key definition. Once you corrected that, any further SPFLite updates will NOT alter your settings in the INI, KBD and Profile files. A new SPFLite version update should almost always be painless as far as settings are concerned. At least, that is always our goal. If there is any user action needed, it will be mentioned in the announcement letter.
George
|
|
