D:\Folder
D:\Folder\File.txt
D:\Folder\EmptyFolder
D:\Folder\File
The problem:
I want to suggest 2 ways for solution:void wrote:A flag is also used to determine if the item is a file or folder.
Differences between the exported formats:
EFU exports the full path and filename, a flag to determine if the item is a file or folder, size and date information.
CSV exports the text that is visible in the Everything result list.
TXT exports the full path and filename.
I'll consider adding the option to open file lists from with a csv extension that contain the Name and Path columns.
I'll consider adding the option to open file lists from with a txt extension.
With both of these types it will be difficult to determine if an item is a file or folder result.
1. At first I was thinking about this solution:
Everything will have a built-in icon - half_folder_half_file icon.
So that:
D:\Folder - system default folder icon (childs detected)
D:\Folder\File.txt - txt file icon
D:\Folder\EmptyFolder - half_folder_half_file icon
D:\Folder\File - half_folder_half_file icon
But I'm afraid there will still be a problem with this kind of folders:
D:\Folder\EmptyFol.der (this folder looks like a file)
So this method will be good only if the user will be aware that the results are approximate.
2. Using "\" at the end of a FolderPath like this:
D:\Folder\
D:\Folder\File.txt
D:\Folder\EmptyFolder\
D:\Folder\File
D:\Folder\EmptyFol.der\
For keeping this "syntax", Everything (or other apps) will use a new extension like ".flist" .
This way, when a user encounters this type of file, he knows that this file contains a file list that keeps this "syntax".
----------------------------
Correct me if I'm wrong,
There is no down side if Everything will use this "syntax" for:
Copy FullPath (Ctrl+Shift+C), and
Exporting to TXT.