|
Post by Stefan on Jul 30, 2021 1:15:09 GMT -5
Say you have a line command pending and you issue a FIND command The resulting message says "+Multiple messages were triggered, press F1 (Help) to see them"
Leaving aside that F1 may not be mapped to "HELP", the HELP command does not display both messages. If you do enter HELP in the above scenario, you only get the 'Pending line command' message. SPFLite does not show you the message raised by the FIND command.
---------------------------------------------------------------------------------
Can I be cheeky and tag a suggestion to this post?
The colour of the error messages is set by OPTIONS SCREEN. I changed mine to yellow on a red background to make them more visible and it works well. But all messages, informational or warning/error, appear with a red background. The options SCREEN panel allows for BG1 and BG2 colours.
What do you think about using BG2 for 'informational' (RC=0) message and BG1 for warning/error (RC>0) messages?
If you agree, I recommend the following Documentation changes
Subject OPTIONS SCREEN Section: Screen Colours - Click Button to change Paragraph: Note: Some of these entries...
Action: Replace Note: Some of these entries may never actually use the BG2 entry. with For entries where banding does not apply, the BG2 setting can be used to enhance the display. For "FM Quick Launch Bar", the BG2 entry can be used to highlite the current selection. For "Error Messages", the BG2 entry can be used to specify a different background for 'Informational' messages.
|
|
|
Post by George on Jul 30, 2021 10:48:01 GMT -5
Stefan: The multiple message thing I tracked down, another wrinkle with the Pending Line Command logic and PFK handling. A typed HELP command would work, a PFK mapped command wouldn't. I won't describe it, but there is some logic as to why there would (or should) be a difference. I'll have a look at the error message coloring thing, shouldn't be hard (famous last words). George [UPDATE] Here's a sample of a normal and an Error message. Comments? [\UPDATE]
|
|
|
Post by George on Jul 30, 2021 14:29:23 GMT -5
Robert: Well, there WAS a difference between HELP typed in, and HELP from a mapped PFK. Be assured there are wrinkles in the SPFLite internals that a) aren't documented and b) even I don't know about till I start 'walking' the code to see what's happening.
Basically, over the years, we have reacted to a whole bunch of "ISPF does THIS and SPFLite does THAT" type 'problems' and the internals are crawling with all these exemptions, and 'watch out for' type things.
That's why I've thrown away any thoughts of 'maybe a re-write would make things simpler' task. There's simply no way to ensure all there wrinkles could ever be incorporated in a re-write.
I revised the message to remove F1 and just leave in (Help).
George
|
|
|
Post by Stefan on Aug 1, 2021 17:01:50 GMT -5
Thanks for the BG2 colouring support. Look forward to seeing that in next release.
Re the typed-HELP vs PFk-Help debate... I don't doubt your reading of the code, but neither my F1 key (mapped as "HELP") nor me typing HELP and pressing <ENTER> works when a line command is pending.
I only see two messages... the first is the "+Multiple messages were triggered, press F1 (Help) to see them". and when I type HELP and press <ENTER> or use the F1 key, I see the "pending line command" msg. Both are displayed (one after the other) in the top right message field.
I believe that entering HELP used to pop-up a window showing the 'multiple' messages, but that windows doesn't appear. I've just retested this with version 2.5.21186 by typing in a single 'C' line command before typing BADCMD a primary command and pressing <ENTER>.
mm...
|
|
|
Post by George on Aug 2, 2021 8:30:09 GMT -5
Stefan: Yes, with 21186 it doesn't work. That has been corrected for next release.
George
|
|