Part of Screen Erased in Quick PH819C3

[georgia miller]

Dear John and all,

>To: georgia miller; Pickering, John (NORBORD); 'PowerHouse Listserv (new) '
>From: Pickering, John (NORBORD) on Tue, Mar 28, 2000 11:40 AM
>Subject: RE: Part of Screen Erased in Quick PH819C3

>
>Lovely problem! How do you test your fixes? Make a change and wait for the
>user to enter several hundred transactions :-)

EXACTLY!   I make the fix, then have her do her usual data entry, which she 
usually does all day everyay.  Except for this morning she is not entering.
I did put in the REFRESH ALL as suggested by several - Thanks! and now
she is to call me if the screen gets erased.  We'll know if it works by tomorrow.
If that doesn't work, then I'll maybe try changing some of the settings in 
QKGO.

>
>>No, control-G does will not repaint the screen.
>>Control-G does work at other times
>
>While I like Michelle from Cognos' suggestion of using a separate statement
>for the refresh statement after the run screen statement I wonder if it
>would help. If ctrl-G won't do it then why should the refresh statement. But
>we're talking about Quick here :-)
>
>
>>It is a regular subscreen.
>>From 3,45 to 11,80.
>>Main screen is From 1,1 to 24,24
>
>I have had funny happenings with less than full width screens so I stopped
>using them ages ago. Is there anyway you can revamp the screens so the
>subscreen uses all 80 columns?

Probably I could, These screens worked fine with 609D and 629E3.
>
>
>>We haven't been able to come up with any pattern
>>or anything but it happens AT LEAST once a day.
>
>Again, must be fun to test possible fixes!

Yup and that's why it's so hard to duplicate.  I can't sit over there
and watch what the user is doing all day either, to see what she is doing 
just before it happens.  That's why it hasn't been fixed for a year!

>
>
>>The Entry procedure is not
>>the default Entry Procedure.
>
>Don't tell Matt oh-not-zero :-)
>
>
>>(Note the REFRESH ALL was added to try to fix
>>the problem - maybe I should add it to the
>>Subscreen stmt too?)
>
>That should only make a difference in find mode.

I did it anyway
>
>
>>there is an Exit procedure on the subscreen:
>>PROCEDURE EXIT
>>BEGIN
><snip>
>>THEN WARN = "*W3 ...
>>END
>
>Is there any pattern between the disappearing background and the warning?

I don't know.  I can ask the user if she ever gets that warning or to keep track of whether 
she gets it when the screen is erased.
>
>
>>It will accept the data but the labels and
>>Id#s are missing.  Quick acts normal but
>>it's difficult for the user to continue
>>with the labels missing.
>
>Off the wall solution - humour-impaired readers please skip.
>Take a sheet of transparency paper and print the labels and ids on it. Cut
>it to fit over the terminal in the right place. Mount it in the frame of one
>of those anti-glare shields and let the user put it on whenever the
>background disappears :-)

That is funny!  Thanks John!!
>
>
>>Thanks for the help John!!!
>
>What help??
>
>
>If you get truly desperate, you could drive the main screen from a ghost
>screen in a loop, passing in a flag. If the user exits the main screen
>normally then you clear the flag and the ghost screen exits back to the
>menu. When you come back from the subscreen you set the flag, exit and pass
>the flag back to the ghost screen which then reruns the main screen. My
>implementation of this would depend entirely on how miserable the user was
>capable of making my life :-)

That's another reason it hasn't been fixed for a year.  Not really,
I was working on y2k stuff and couldn't spend much time on it.
Now I am catching up on my work again and trying to make 
my users happy.  Another reason is it only effects one user.

>
>Regards,
>John Pickering
>Toronto

I really appreciate all the input from everyone. At least my user knows
I am trying to fix it for her again.

Georgia

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.