Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
Hi, I have a question regarding the "EDIT" function in ALL-IN-1. A customer developed an application using WPS-PLUS as the editor. Due to the logic of that application, the files are copied to other files with a "WPL_TEMP" extention in their name. In a later stage the application invokes the WPS-PLUS editor with the "EDIT" function. Since the file extention is not "WPL", the editor assumes the file is not a "WPL" file (but probably an ASCII file) and tries to convert the file into WPS format. That action failes and corrupts the file. In the application programming reference, it is stated that the "EDIT" function examines the extention of the file, in order to determine it's internal format. That probably causes the problem stated above. Is there any workaround to this problem? Thanks, Yariv
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2806.1 | Create a "new" editor OR change the extension | TAV02::CHAIM | Semper ubi Sub ubi ..... | Mon Jun 07 1993 06:47 | 17 |
Yariv, Unless there is some undocumented qualifier to the EDIT command in which you can specify the format of the input file without EDIT having to to use the file extension to determine the file format, then I can see only two possible alternatives: 1. Using CLI, create a "new" editor which would be identical to WPSPLUS but with the extension that you desire. 2. Use the .WPL extension and tack on your TMP to the file name rather than the file extension. Thanks, Cb. |