at once.
The drawback is, it does lack relevant editor capabilities like multiple cursors, search and replace, etc.
This little tool does the following:
- It is invoked via a .xys script
- It passes the file that was written by the .xys script to an external text editor of your choice
- When the file is saved (from inside your text editor), it updates the content of the "Edit Item Names..." window
- It automatically activates this window (if configured via the .ini file - It's ON by default!)
- It monitors the "Edit Item Names..." window and quits itself, once this window was closed
When the script is started for the first time, it creates an .ini file with the same base name as the script after using a "startup wizard".
This will ask you to find and select two things (and opens a file requester for both):
01. Find and select the "xyColumnEdit.exe" file
02. Find and select the text editor (that should support a "column edit mode") to use
The .ini file could e.g. look like this afterwards:
Code: Select all
[General]
Tool=@Tools\ColumnEdit\xyColumnEdit.exe
Editor=C:\Program Files (x86)\Sublime Text\sublime_text.exe
ActivateWindow=1
Temp=R:\TEMP
Tool
, Editor
and Temp
entries support portable paths!The root path is
<xypath>
and in this sample .ini, the Tool
entry was saved relative to it.The script would resolve it internally to
<xypath>\@Tools\ColumnEdit\xyColumnEdit.exe
...The
ActivateWindow
and Temp
entries are using default entries (1
and the %TEMP%
environment variable) on first script start.If you would like the script to save the file that contains all items to rename in a different location you could change the
Temp
entry in the .ini file afterwards.If you don't want to auto-activate XY's 'Edit Item Names' window, set
ActivateWindow
to 0
.The attachment contains the .xys script
ColumnEdit.xys
and the compiled AHK script xyColumnEdit.exe
...Please note that you can't use your old .ini file when switching to v1.3 (or up)!
Current version: