system command - problem resolved

Mon Nov 7 13:00:41 PST 2005

My thanks to John & Ken and to Brian White for his lengthy response on the 
approach for how to validate the use of the back slash (everyone should keep 
that for a how to primer).

The processing now works.

First, what I meant by "open fields" was that they were not restricted 
fields. The screen could be put in update mode.

Ctrl-L did work in both types of screens. With unrestricted fields we had to 
add the Ctrl-C and then use the Ctrl-L manually.

I experimented with the screen command because of a prior request from the 
list.

Ken I never got to the point of testing the "echo hello". I did try the 
sleep command and that had no effect.

Once I received John's e-mail it was easier to test his suggestions first 
which was a combination of using the "noredraw" and the "display" command.

We tried system command without noredraw and used the display (@sn) command. 
That did not work. We then added noredraw after the system command and left 
in the display command. That did work. We then removed the display command 
and left the noredraw in. That also worked.

The following is what now works:

Then: le="echo";lg="\"\\033&o";pa="Fvar 
searchnum="{@rn{";CompileFile(\\"260268.cs\\");\\015\""

Then: system noredraw le<lg{pa;le="";lg="";pa="";end

Ken and perhaps John and maybe some others asked me to test "noredraw" when 
I first started to list the problem. I did and it did not work. The only 
problem was that the processing line was incorrect at the time, as we were 
then trying to determine the correct sequence to use the back slashes. After 
we fixed that problem and the processing executed properly except for 
getting hung up we never went back and tested the "noredraw" again until it 
was just suggested again.

I can't thank you all enough.

If I left anything out that anyone wants to know, please identify what it is 
and I'll respond to the list.

Thanks again,

Dennis Malen
516.479.5912

----- Original Message ----- 
From: "John Esak" <john at valar.com>
To: "Dennis Malen" <dmalen at malen.com>
Cc: "Fplist (E-mail)" <filepro-list at seaslug.org>
Sent: Monday, November 07, 2005 2:46 PM
Subject: RE: system command - problem resolved

> Dennis,
>
> 1) Like Ken, I need to know what you mean by "open fields on the screen".
>
> An @key does not take you into any field on the screen unless you
> specifically tell it to do that.
>
> 2) Also, I need to know what the purpose of the "screen" command is. Were
> you using this to try and clear things up after the @key is finished?
>
> 3) Can you tell me the difference in what happens when you do:
>
> Then: system le<lg{pa;le="";lg="";pa="";end
>
> and
>
> Then: system noredraw le<lg{pa;le="";lg="";pa=""; display (@sn);end
>
> and
>
> Then: system le<lg{pa;le="";lg="";pa=""; display (@sn);end
>
> Do any of these clear up the problem?
>
> John
>
>
>> -----Original Message-----
>> From: Dennis Malen [mailto:dmalen at malen.com]
>> Sent: Monday, November 07, 2005 1:16 PM
>> To: john at valar.com; pmahler at malen.com
>> Cc: Fplist (E-mail)
>> Subject: Re: system command - problem resolved
>>
>>
>> John,
>>
>> Just got in from Chicago.
>>
>> For further clarification when we execute the program and use
>> control L in a
>> screen that has no open fields, then the control L manually solves the
>> problem. If the user executes the processing from a screen that does have
>> open fields then we have to manually do a control C and then a
>> control L. My
>> concern is that if I do a pushkey and do a control C often to release the
>> screen I was under the impression from prior listings that that approach
>> should be avoided and I do not know why that was the case.
>>
>> Here's the code we use:
>>
>> @keye
>>
>> Then: le="echo";lg="\"\\033&o";pa="Fvar
>> searchnum="{@rn{";CompileFile(\\"260268.cs\\");\\015\""
>>
>> Then: system le<lg{pa;le="";lg="";pa="";screen;end
>>
>> Note: I get the same result with or without "screen" on the second then
>> line.
>>
>> Hope this helps.
>>
>> Dennis Malen
>> 516.479.5912
>>
>> ----- Original Message -----
>> From: "John Esak" <john at valar.com>
>> To: <pmahler at malen.com>
>> Cc: "Fplist (E-mail)" <filepro-list at seaslug.org>
>> Sent: Wednesday, November 02, 2005 6:47 PM
>> Subject: RE: system command - problem resolved
>>
>>
>> > The only reason I can think that the cursor would go into that
>> open field,
>> > is if you are telling it to somehwo in the @key processing. Does this
>> > processing just END or does it hit a screen, popup, restart, update or
>> > anything like that? Is there any reason why you can't just post the 
>> > @key
>> > code here? It would help to solve this one quickly.
>> >
>> > JE
>> >
>> >> -----Original Message-----
>> >> From: filepro-list-bounces at lists.celestial.com
>> >> [mailto:filepro-list-bounces at lists.celestial.com]On Behalf Of
>> >> pmahler at malen.com
>> >> Sent: Wednesday, November 02, 2005 4:27 PM
>> >> To: Kenneth Brody; Dennis Malen
>> >> Cc: Fplist (E-mail)
>> >> Subject: Re: system command - problem resolved
>> >>
>> >>
>> >> Dennis is out of the office until Monday, so we are not going to do 
>> >> any
>> >> programming on this issue until Monday, but any input for then would 
>> >> be
>> >> greatly appreciated.
>> >>
>> >> Ctrl-L will redraw the screen.
>> >>
>> >> We have something else interesting in that if the screen has an
>> >> open field
>> >> the system goes into update and places the curser in the field on the
>> >> screen. You can Ctrl-C out of the screen and then Ctrl -L to
>> >> redraw but of
>> >> course we would not like to do that.
>> >>
>> >> If the screen has no open fields then just the Ctrl -L is needed.
>> >>
>> >> Thanks for your assistance
>> >> Paul
>> >> ----- Original Message -----
>> >> From: "Kenneth Brody" <kenbrody at bestweb.net>
>> >> To: "Dennis Malen" <dmalen at malen.com>
>> >> Cc: "pmahler" <pmahler at malen.com>; "Fplist (E-mail)"
>> >> <filepro-list at seaslug.org>
>> >> Sent: Wednesday, November 02, 2005 3:42 PM
>> >> Subject: Re: system command - problem resolved
>> >>
>> >>
>> >> > Quoting Dennis Malen (Wed, 2 Nov 2005 14:53:01 -0500):
>> >> >
>> >> >> John,
>> >> >>
>> >> >> After the program properly goes to windows and pulls up the correct
>> >> >> program, we want the user to minimize the screen and continue with
>> >> >> filePro. What's happening is that when the window is minimized the
>> >> >> cursor is in the middle of the screen and only half the screen is
>> >> >> displayed. The user has to hit enter and the cursor goes to the
>> >> >> bottom where it should be. The only problem is that half the screen
>> >> >> is still displayed. The user must press another key for a different
>> >> >> screen and then manually come back to the screen they were in order
>> >> >> to redraw the screen.
>> >> > [...]
>> >> >
>> >> > Sounds like a bug in your terminal emulator.
>> >> >
>> >> > Must you press Enter, or will any key suffice?
>> >> >
>> >> > Does pressing Ctrl-L cause the screen to redraw?
>> >> >
>> >> > --
>> >> > KenBrody at BestWeb dot net        spamtrap:
>> >> <g8ymh8uf001 at sneakemail.com>
>> >> > http://www.hvcomputer.com
>> >> > http://www.fileProPlus.com
>> >> >
>> >> >
>> >>
>> >> _______________________________________________
>> >> Filepro-list mailing list
>> >> Filepro-list at lists.celestial.com
>> >> http://mailman.celestial.com/mailman/listinfo/filepro-list
>> >
>> > _______________________________________________
>> > Filepro-list mailing list
>> > Filepro-list at lists.celestial.com
>> > http://mailman.celestial.com/mailman/listinfo/filepro-list
>> >
>> >
>> >
>>
>
>
>
> 