Welcome to the IDM Forum. This forum is meant as a user-to-user support mechanism where users can share knowledge and tips for all IDM software.
Since these forums are user-to-user based, IDM does not regularly read or reply to the posts in this forum. For problem reports, suggestions, or feature requests, you must email us directly. Our trained technical support staff answers most inquiries within 30 minutes.
Ultraedit Help wrote:Double clicking on a line containing the filename and line number will cause UltraEdit to attempt to open the file specified at the line number. If the filename is fully qualified the filename will be located and the number after this will be used for the line number. If the filename is not fully qualified UltraEdit will attempt to determine the filename from the first word in the line that contains a period. UltraEdit will then open the specified file in the directory of the active file. If the file does not exist in the directory of the active file, UltraEdit will try and open the file from the Project Directory if it is specified.
Mofi wrote:With a default directory set for file names with relative path, UltraEdit does not longer look for the file in the project directory or the directory of the active file. It would be good if UltraEdit would work as follows:
If the Default Path is not set by clicking once again on "Set Default Path for Relative Paths...", clicking on button Cancel, confirming the following question with Yes, and the file RelativePathTest.txt is moved from the directory DefaultDir to ProjectDir or ActiveFileDir, the file is found and opened on double click on the line in the output window. So 2. and 3. is already working, but unfortunately only when no default path is set.
- First checks if a default path is set and if this is the case looks for the file using the default path and the relative path of the file.
- If 1. does not return full path of an existing file, check if a project is loaded and a project directory is set. If this is the case search for the file using the project directory path and the relative path of the file.
- If 2. does not return full path of an existing file, check if a file with file name is opened and use the path of this active file together
with the relative path of the file.
- If 3. does not return full path of an existing file, check if there is any file open in UltraEdit having the same name (case insensitive on Windows, case sensitive on Linux) as the file in the current line of the output window and available path matches also after removing from relative path everything left LAST ".\" including the point.
A file is opened with full path C:\Temp\RelativePathTest.txt
The output window contains ..\..\relativepathtest.txt(1):
"\relativepathtest.txt" matches "\RelativePathTest.txt" - file found!
The output window contains ..\temp\relativepathtest.txt(1):
"\temp\relativepathtest.txt" matches "\Temp\RelativePathTest.txt" - found!
The output window contains .\relativepathtest.txt(1):
"\relativepathtest.txt matches" "\RelativePathTest.txt" - found!
The output window contains .\temp\defaultdir\..\relativepathtest.txt(1):
"\relativepathtest.txt" matches "\RelativePathTest.txt" - found!
Of course for UEX the compares would be case sensitive and therefore the examples above would return all 4 "not found in opened files".
It would be better if the project directory and the directory of active file would be also used to find a file with relative path if a default path is specified (UltraEdit remembers that path in uedit32.ini) and the file does not exist in the specified default path, for example because of a switch to another project.
4. would be an enhancement which takes into account, that lines with relative path in the output window are often caused by capturing output of a user tool executed for 1 or more already opened files.