I have run a Find In Files with results to an edit window and it looks as follows:
- Code: Select all
Find 'ReceiveVe' in 'F:\Temp\Rs232Ve.cpp':
F:\Temp\Rs232Ve.cpp(1619): return ...
F:\Temp\Rs232Ve.cpp(1654): BOOL ...
F:\Temp\Rs232Ve.cpp(2010): if( ...
F:\Temp\Rs232Ve.cpp(2012): SendToErrorExtLogPipe( ...
Found 'ReceiveVe' 4 time(s).
Search complete, found 'ReceiveVe' 4 time(s). (1 file(s)).
If I now set the cursor anywhere inside F:\Temp\Rs232Ve.cpp(1619)
without selecting it and press the right mouse button, UltraEdit v22.214.171.1244 displays at top of the context menu Open "F:\Temp\Rs232Ve.cpp/1619"
and if I click now on this item, the file is opened and the cursor is positioned at start of line 1619. You don't need to select a file name. UltraEdit will always check the string at current cursor position if this is a file name (with line number) or a url when you press the right mouse button in the edit window.
If I select just the complete file name without (1619)
and click the right mouse button, the context menu contains at top Open "F:\Temp\Rs232Ve.cpp"
and opens next this file with the cursor at top of this file.
If I select only Rs232Ve.cpp
and click the right mouse button, UltraEdit checks in the background, if a file with that name exists in the current working directory. If this is the case, the context menu shows at top Open "Rs232Ve.cpp"
and I can open that file. But if the file does not exist in the current working directory, the context menu does not contain any entry to open a file "selected text
So your problem is that the file you want to open is not in the current working directory. What is the current working directory?
Well, normally it is the directory specified in the shortcut to UltraEdit at Start In
. But if you have not started UltraEdit with the shortcut, it is the program directory or the directory of the file you opened with a double click. It can be also the directory of the file you last opened. Or it is the directory of the file which currently has the focus. There are several configuration settings to determine what UltraEdit should use as current working directory.
So the feature works quite well. UltraEdit just can't find the file with the name you have selected because of missing the path and it can't find a file with that name in the current working directory of UltraEdit.
By the way: The line number could be also appended to the file name with /1619
instead of (1619)
And without testing it I think UltraEdit searches for a file with a relative path (file name without full path) additionally to the current working directory also relative to the project directory if a project/workspace is loaded which contains the path to the project directory.