system command - problem resolved

[Kenneth Brody]

Quoting Dennis Malen (Mon, 7 Nov 2005 13:16:28 -0500):

> 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.

I'm not sure what you mean by "open fields", and since you're not going
into update on the screen, I'm not sure why fields on the screen would
have any effect.

> 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.

So, Ctrl-L doesn't work if there are "open fields" on the screen?

[...]
> 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.
[...]

Well, the screen command does make a difference, in that you are taken
into update mode on the current screen.

Again, this sounds like a bug in your terminal emulator.  (Either that,
or the escape sequence you are sending does more than what you think.)

Upon return from the SYSTEM command, filePro will clear and redraw the
entire screen.  If part of the screen disappears, then the terminal
emulator has ignored filePro's redraw somehow, or something about the
escape sequence causes the terminal emulator to do something with the
screen even after filePro has regained control.

If you redirect the echo command to a file (following the directions
posted here numerous times recently), do you lose part of the screen?

If you do a simple "echo hello", do you lose part of the screen?

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com