Re: List of CL GUI prompting errors

A month has passed since I submitted my list of CL GUI prompting errors but
I have not received a response yet from IBM.  Since I hear talk of the next
service pack coming soon, I thought you might want to review this as soon
as possible.
I would appreciate it if someone from IBM could please respond.

Thanks,
Craig Strong

** Craig wrote:
I like CL GUI prompting because it limits what you see base on what you
type, quick push buttons, selections, help, etc but there are some errors
that can make it difficult.

The following is my list of CL GUI prompting errors in order of importance:

1. After prompting with F4 and going to another session in the Windows
taskbar, the CODE/400 Editor freezes.
I click on the Editor session in the Windows takbar but nothing displays.
The only option I have is to close the session and lose any work in any
programs I was working on in the Editor since the last autosave.  Even if I
remember and try not to swtich to another Windows session, if I get an
e-mail, I am automatically switched to the e-mail session and all I can do
is wave goodbye to my work since the last autosave.
NOTE: When prompting without CL GUI prompting, the local GUI prompts show
up for ADDLIBLE, CALL, etc (this is an error in itself seen in the post on
January "CL GUI Prompting haunting programmers").  These local GUI prompts
show up in a different Windows session and are fine because I can switch
between different Windows sessions and come back.  Maybe the solution to
the freeze problem is to modify the GUI prompting to function similar to
the local GUI prompting.

2. Prompting a command in a command is not supported.
For example, when prompting IF or MONMSG and entering a command instead of
DO in the EXEC, you cannot prompt the command within the IF or MONMSG.  The
green screen in the STRCODE session supports this.

3. Adding comments in a prompt is not supported.
Even though the comments are aligned correctly when entering them without a
prompt, it would be nice to be able to change them in the GUI prompt.

Inconvenience:
Lastly, GUI prompting for the first time after rebooting, causes a login
window and then it takes awhile before it actually prompts.  Why should I
have to enter a password if I am already connected and why should it take
so long?  After that it is fairly quick whenever I prompt.  It just seems
like all that first time processing could take place in the background
ahead of time.

I can deal with most of the errors listed except #1.  Any help would be
greatly appreciated.

Thanks,
Craig Strong