I've noticed when using update processor in the d3 version 7.5 for
linux, the input is a line off.

For example, if I wanted to edit attribute 1 in a file dictionary, the
input will have to be done on line 2 or it will effect the line above.

Has anyone else experienced this, am I doing something wrong?

"Specific" wrote
update processor in d3/linux 7.5 , the input is a line off.

Doublecheck your declared rows per screen is right by
hitting carriage return at tcl : prompt -- you should see the
time and date on the line above the cursor, but just :
with no timedate on the row bearing the cursor.

Term

shows current setting,
term ,25 will declare 25 rows per screen, for example.

Your whole term type could be a bad choice, like wy60
in a situation that vt100 would be a better choice,
but it is unlikely update would be working as well as it does
if that were the case.

Oh, and you may just have a low quality screen handler,
like the telnet command that comes free with windows.
And I admire putty for the nice utf8 character handling of
man pages, but really hate to use it for update edit sessions...

The time and date display correctly above my cursor in TCL. My
environment as of right now is on a windows machine using putty
configured with 80 cols and 24 rows.

Here is what happens:

TCL> ud my.customers name

Update processor opens up with cursor on line "attribute-count," the
cursor should start at "dictionary-code"

If I were to edit here, it would actually alter the dictionary-code.

I've tested this on putty and linux terminal.

Any ideas?

Frank Winans,
Term in tcl output:
Terminal name: d3-mon
Product name: D3 Console
Terminal Width: 79
Terminal Depth: 25

I changed putty to that configuration and it seems to have fixed the
problem.

Thank you very much =)

On Jul 11, 2:55*pm, Specific <domp... (AT) gmail (DOT) com> wrote:
The Update Processor needs to have the terminal depth (rows) set to 24.

On Jul 11, 11:54*pm, IsItMeOr <terriat... (AT) gmail (DOT) com> wrote:
That's what my previous configuration was set at and it didn't work,
however, setting my terminal height to 25, matching the term-type for
the port, seems to have worked perfect. If you could clarify why the
update processor needs to have a terminal depth of 24, let me know and
I can change the settings. Right now it seems to be working as it
should.

I would like to thank the community again for a quick response, and to
let you all know how glad I am to have found a group that is still
alive.

The update processor doesn't care what the page depth is - it just has
to match whatever your text window size is. I run a wintegrate session
at 132 wide x 60 deep with no problems. My terminal settings match
that. All good.
Aloha!

On Jul 12, 3:28*am, Specific <domp... (AT) gmail (DOT) com> wrote: