- This button creates folders for each file type in the current folder.
- It then moves each file into it's corresponding folder.
AutoBoxxed.dcf (2.3 KB)
5 Likes
Interesting, but what's the idea behind it?
I use it to organize my downloads directory which gets out of hand all too often.
1 Like
So it's a sort of label. Thanks.
Not bad. I will try that now.
Maybe you could modify the code that it autoboxes only the type of the selected item. For example exe only, when Shift-clicking the item. So both variations would work.
1 Like
This error message will never be shown, because WScript is not available:
WScript.Echo "Error: Folder does not exist - " & folderPath
WScript.Quit 1
In Opus 13, this button will pretty much do the same:
Rename TO="prefix {{=UCase(ext)=}\*" IGNOREEXT
1 Like
Certainly users can customize the script to suit their workflow needs.
Maybe some users, yes. It looks like Opus is getting more and more a tool for people who can code. That's a pity.
What does that mean? You want the prefix to be optional?
I have a folder with all kinds of incoming stuff, images, text, executables, etc.
What i mean is, it would be handy, if i could select an exe file, and the script would only autoboxx all files of that type, rather than having all the rest also autoboxxed. Maybe with Shift as a modifier key to restrict autoboxxing files only for selected extensions.
Something like this?
Rename FROM={sourcepath}*{file|ext} PATTERN=* TO="{file|ext2}\*"
Yes, something like this. In the original script i like that there's that "autoboxx" name part, which looks a bit better than having a folder just nakedly named exe. Another quirk could be, if that script could recognize file type groups, so it would grab, for example, txt/rtf/doc in one go.
Rename FROM={sourcepath}*{file|ext} PATTERN=* TO="Your prefix here {file|ext2}\*"
So you want to select one .doc file, and the command moves all files from that file type group into a folder named "Documents"? That would probably require a script, but since there are not so many file type groups, we could insert them directly, e.g.
Rename FROM={sourcepath}grp:Documents PATTERN=* TO="Whatever prefix - Documents\*"
Well, that's only an idea, as how to extend that script idea. I'm already happy with the simple version, and we also have grouping already, which only requires a few simple steps to achieve some similar results.
Here is a front end to @lxp's suggested code:
//https://resource.dopus.com/t/folderize-directory/56613/5
@filesonly
//I listed my top eight file type groups containing a single extension
//Modify the list to your most common file type groups that contain a single extension
@Set Grp {dlgstringS|Create a New Folder of Files of a Selected File Type Group\n\nPlease enter the file type group: pdf, txt, wpd, html, 7z, png, mp3, doc.}
Rename FROM={sourcepath}grp:{$Grp} PATTERN=* TO="Folder of ''{$Grp}'' file type group files\*"
Go REFRESH=expanded,source,state,filterclear
You will need to create single extension file groups and list them above.
1 Like
I might be wrong but, is it not more that your needs are becoming more esoteric, because your basics are already taken care of? So the things you haven't already set up are the things that are (often) on the more complicated end.
The more unique the thing you want to do or streamline, the more likely it is to not be provided by default, and require some button editing, or regular expressions, or even a little jscript code. But I don't think anyone has to do those things to use Opus, and I'd be surprised if anyone thinks Opus has gotten harder to use over the long time you or anyone else has been been using it.
People here will often spend hours helping with those things when it's needed, too.
6 Likes
No, that's an optical illusion. It may look like this because your willingness to follow advice is declining. In reality, Opus' upgrades make it easier to use and reduce the need for coding.
Someone trying to blame the SatNav for taking the wrong turn?
3 Likes