mvToolbox  
Features
  Overview (Power Point)

Testimonials
  Read
  Post

Downloads
  Free Trial
  Current Modules
  New Revisions
  Terms of Use
  Documentation

Buy

Product Activation

Support
  User FAQS
  User Forum
  Contact Support

Company
  Contact Us
  News
  Alliances
  PICK Links

Frequently Asked Question

Post a Question
Search FAQS

Problem pasting into telnet client window - how should I have done it

Post 9 [28 Jul 2004 10:57PM]
Name
Arnie
City
Philadelphia
State
PA
Email
URL

Hi Bro,

Thanks for fixing LX.

I found something else, but it must be partially my lack of experience with VGER (I gotta tell ya, I love that Trek reference!). What I did was scraped the bottom of this thread where you pasted the text for VGER$LX. My intention was to do a compare (can't any longer because I have overwritten the original that was in VGERBP), so I used QL to create a list of programs in VGER BP. Then I opened the original VGER$LX routine and at the command line entered NEW to open a new blank window. I left the file name VGERBP but the new record name was VGER$LX.ROY. The window opened. I then pressed F11 to open VGER and just clicked the paste icon to paste what I copied from the email. Actually, before doing that I pasted the text into Notepad to make sure the longer lines were really wrapping. Pasting the text into VGER didn't go so well. After 62 lines it started over again with line 1. Then it counted up 123 lines and kept overwriting that line. the paste was going so slow that I eventually just closed the session. I ended up using Windows Explorer and overwrote the original VGER$LX subroutine.

It wouldn't compile because line 995 was uncommented and it was for D3 syntax. I used VGER to comment that line and uncomment the line for UniVerse above it. I used BAS in the toolbox and compiled the program. Then the LX command worked properly from LPR.

Instead of pasting the newer version from the telnet client window into the new VGER window, what should I have done to get my copy from the clipboard into the VGER window?

BTW: I like to use Dynamic Connect, which is wIntegrate without all the features and client/server capabilities. I just put the keyboard file into it and modified the color scheme (I like green screen and so forth) and it works just fine that way. This means that both your color and keyboard WIS files for wIntegrate work just as well in Dynamic Connect, as I expected. You can suggest that for U2 customers that do not own any of the telnet clients you have files for. Dynamic Connect is free and part of the clients CD shipped with U2 database CDs.

Send To Printer

What you did is exactly what I might have done. You certainly do learn quickly. I have been working on the generalized input routine lately to put in such things as being able to use arrow/page keys within an input block, or to be able to click on a position and go to it. It looks like the law of unintended consequences has struck. It appears the changes I made had an unexpected effect on the full screen program at the page boundary. I did not test that particular scenario, as it is not one that I would normally use. I will look into it and get a fix to you.

There is an alternative though. As you found out, the pasting process in big pastes is slow because of the large amount of overhead involved repainting the screen. I have the disadvantage of not being able to tell the difference between typed characters and pasted characters. I wrote some code to be able to download pasted text directly into a window. The command is ASCII.RECV. There are two versions of it. One version uses an INPUT statement to enter the pasted text. After I wrote it, I became aware that some flavors filter out special characters, like the esc character, from the line that is input. Ergo a second version which uses byte-by-byte input. The version you have is the first version I wrote. I am not sure if the flavor you are using filters the input line, so, in case it does, I have attached the second version in a zip file. This is important because the sequence "esc esc " ends the input. If the first version does not work, use the second.

There is a specialized interface for all VGERBP modules. It is EV. Every dynamic command has VGER$ as a prefix. This was done to ensure I did not overwrite anyone else's programs. The part to the right of the $ is call its command name. With EV you only have to enter the command name, i.e., EV LX would open VGER$LX, or EV ASCII.RECV for VGER$ASCII.RECV.

There is a command to set all the triggered code properly. The command is PREP. When editing an mvToolbox module, type PREP UNIDATA (or D3 or UNIVERSE, depending on your flavor) and it will set the triggered lines properly. In LIST.EDIT, put your cursor on the module and type PREP D3 (UNIDATA / UNIVERSE), or if you are doing all, type PREP ALL D3 (UNIDATA / UNIVERSE).

What I would suggest, would be to paste the code into a ascii text file on the server, and create a VOC entry pointing to its folder. Then you would have a staging file for future enhancements/fixes. All you would have to do is save it there, and edit it directly, or just copy it over to VGERBP. There are a NUMBER of ways to get it into VGERBP. Look at these commands: OVL, COPY.TO, SAVE, and LOAD.

Thank you very much for the feedback, and the information about Dynamic Connect. I have attached a zip file with the changes you suggested yesterday, and the second version of ASCII.RECV. I am looking into the pasting problem.