I have seen that as I looked on your code:Ī selection with GotoLineSelect from line 2 column 22 to last line column 25 would work, but the line number of the last line is normally not known and so a fixed line number cannot be used.Īs I workaround for all the problems I have modified the macro now to this one which hopefully does the same as your one. I will report this horrible bug also to IDM.Īnd I will report also that GotoLineSelect with column number does not select the correct range from current cursor position to the specified line/column in column mode when selecting in reverse direction. I run several tests and I have seen that this bug also exists with UE v13.00+5, UE v13.00+2 (I don't have anymore v13.00+1 and v13.00), but not with UE v12.20b+1 or any other v12.20.
#Ultraedit column mode code#
If you look on the re-opened macro after editing you will find an additional double quote at end of the macro indicating that the macro code is interpreted as text. But if a user modifies the macro later in the editor, the compiler will interprete this as follows for your macro:Īnd the rest of the code of your macro is interpreted as simple text. Is correct recorded with the macro recorder. A string with an odd number of double quotes inside is not compiled anymore correct when closing the macro in the edit macro dialog. Okay, I found the horrible bug of the edit macro dialog of UE v13.00+? and UES v6.20+? which is causing all the problems you see. Could you try it on your machine (Version 13.00+4) and see if it also happens to you? Thanks. Specifically, I tried changing 1 39 to 1 38 and Replace FY07 with 2008 instead of 2007. Modifications to ReviseB or Split2 does not cause this issue. After that, pressing "Shift+1" only copies the macro text into the file starting at 1 1. The problem is ONLY if I try to modify "ReviseA" in any way on his PC. I can also email the file to the other person, open the macro file and run any macro as is there too. I can modify any macro and run with no issues. The "ReviseA" macro causing the issue is below. Should be no problem because it is really simple. ) and I will adapt my prog for your need on weekend. However, if you would need my program to make a "convert to fixed column width" via a user tool which can be used from within a macro, tell me what you need (number of columns, max line length after convert, separator character, file format. The prog first analyzes the file to get width of every column (Scan button in UE dialog) and then writes the new file with spaces for alignment and 3 spaces instead of the tab. line length of 512 bytes (without \r\n\0) and the separator character must be a tab char. My prog supports up to 16 columns with a max.
But this program was written for Filemon/Regmon/Portmon logs and so is not for general usage.
#Ultraedit column mode full#
I have once written for myself a small 'C' program which does the same as "Convert to Fixed Column" with appropriate settings (is not a full equivalent) which could be run by a user tool. I think because of the user interactions necessary or large number of parameters. I'm quite sure Key SHIFT is useless in the macro and maybe command StartSelect is better.Īnd command "Convert to Fixed Column" is not available in the macro environment. So this macro works only with this version of UE/UES or any higher version. GotoLine and GotoLineSelect with line number 0 to move the cursor to the specified column in the current line is supported since UE v12.20a+2 and UES v6.10a+2. This bug was fixed with UE v13.00+2 and UES v6.20+2 and so the workaround is not necessary anmore if you use this version or any higher. So delete the inserted blank line at top of the file, if you don't need it anymore and no selection is active with command DeleteLine. The following macro contains the same workaround. To solve this problem I always insert at top of the file an empty line and delete it when I don't need it anymore when I'm using the GotoLine or GotoLineSelect with a column number at first line. If the file is an ASCII file and not a Unicode file, and GotoLine or GotoLineSelect is used with line number 1 or at line 1, the cursor is always positioned to specified column number + 1 (BOM of Unicode files also taken into consideration for ASCII/ANSI files). Please note: The first versions of UE/UES supporting GotoLine with a column number have a bug. However, in your case it is better to select from last line of the file column 25 to first line of the file column 21. When working with selections in column mode it is normally better to temporarily delete all blanks lines at bottom of the file, so the last line of the file has no line termination and Bottom or SelectToBottom moves the cursor to end of content of last line with content.
0 kommentar(er)
