Ya, well it's definitely a rant. But it's one of those uncomfortable but necessary talks.
I don't agree with "fit my personal needs". I don't buy that, never have.
If it's useful for me then it's useful for everyone. I'm not curing cancer over here, I'm just managing files, just like any other John Doe.
The thing about consumer data is the majority is silent. The real reasons they don't use something isn't always the one reasons we think it is. (The whole reason for all this orwellian data collection is so the decision makers know what real reasons for human behavior is). If a program like Dopus has lots more abilities than another program, how come there isn't more people utilizing these things? Because a fraction of possible users will spend as much time as I have learning computers and implementing these abilities. It's just that simple.
If someone can't figure out why Canva, being the worst picture editing software ever made, yet is the most popular, then I can't help them (It's easy to use!) Until they realize that if you build it they will only come *if they can. If you build a big beautiful house but no one has transportation to get to your house, then you're going to be pretty lonely in that house all by yourself.
It's like when telling people to read the manual, make sure you have a good manual first. And that relevant data isn't hard to find.
And if you don't want too much forum activity (complaints, issues etc.) then don't drop the ball in the first place, where they are forced to end up on your forum asking for help. In both cases the original offender is the seller, not the buyer, every time.
My success here is everyone's success. The next guy who has my same problem will be served by the the record (forum) of the issues that I got solved and will be on his way. Therefore the company saved effort solving a hundred futures issues because they (you guys) had already solved my one.
Note that I posted a new version with improvements to GETPROPS, and you can now use the same vars as in FILESâfor example, GETPROPS $visible_dirs$ to refer only to selected folders, etc.
Nerdy deep dive on sizes and folders
Keep in mind you canât get certain props from folders, like size, unless those items come from a Tab object directly. So if you specify filenames, properties like size will always be 0. But you can use all the other vars to easily reference those items.
Alright, I updated to the latest LogicRun version.
This modified button isn't working for me. Ctrl and Shift doesn't change, no modifier selects all. I ran some tests on the vanilla standard buttons and the "folders only" kind isn't working for me either. Depending on how I set it up it either selects all folders or it throws an error.
I checked my Everything index and it's set up correctly, including sizes. I also have the Windows index (But it doesn't tell you what it means by "properties", cause reasons). I tried the $visible_dirs$ with or without quotes. Tried adding the GETPROPS before it.
Tried getting rid of the USEEVERYTHING. I duplicated files and folders and renamed them so that I'm for sure using same sized items. I'm all out of ideas.
Post the exact instruction you're using.
Also set log level to debug in script config.
Then open the script log pane and use your button. You can see there what's the actual command line you're passing to the command. You can post that info as well.
Log, from clicking on the button without any modifiers held down.
Making sure a file was selected that has other files in that folder which are the same size.
30-Apr-25 07:38:PM LogicRun: INFO => === COMMAND BEGIN ===
30-Apr-25 07:38:PM LogicRun: DEBUG => cmdline : LogicRun FILES $visible$ IN C:\Users\me\Downloads\Hardstyle\ GETPROPS
30-Apr-25 07:38:PM LogicRun: DEBUG => COMMANDS : true
30-Apr-25 07:38:PM LogicRun: DEBUG => USEEVERYTHING : size:$(sizeautoEV)$
30-Apr-25 07:38:PM LogicRun: DEBUG => FILTER : false
30-Apr-25 07:38:PM LogicRun: DEBUG => FILTERDEF : false
30-Apr-25 07:38:PM LogicRun: DEBUG => GET PROPS : 0
30-Apr-25 07:38:PM LogicRun: INFO => Validating 1 entries...
30-Apr-25 07:38:PM LogicRun: INFO => Expanding filter...
30-Apr-25 07:38:PM LogicRun: INFO => Getting values for "sizeautoEV"...
30-Apr-25 07:38:PM LogicRun: DEBUG => QUERY : size:66bytes
30-Apr-25 07:38:PM LogicRun: INFO => Getting files using Everything...
30-Apr-25 07:38:PM LogicRun: DEBUG => ==> EV is running:true; autorun:false
30-Apr-25 07:38:PM LogicRun: DEBUG => ==> Waiting for EV database to be loaded: 1
30-Apr-25 07:38:PM LogicRun: DEBUG => QUERY : < <C:\Users\me\Downloads\Hardstyle\>> size:66bytes !path:"$Recycle.Bin"
30-Apr-25 07:38:PM LogicRun: DEBUG => ==> Query finished, results: 0
30-Apr-25 07:38:PM LogicRun: INFO => ITEMS : 1
30-Apr-25 07:38:PM LogicRun: INFO => RESULTS : 1
30-Apr-25 07:38:PM LogicRun: INFO => Running command(s) in 1 file(s)...
30-Apr-25 07:38:PM LogicRun: DEBUG => => Select FROMSCRIPT DESELECTNOMATCH
30-Apr-25 07:38:PM LogicRun: INFO => ==> Command "Select FROMSCRIPT DESELECTNOMATCH" succesfully executed
30-Apr-25 07:38:PM LogicRun: INFO => === COMMAND END ===
Paste this into Everything : < <C:\Users\me\Downloads\Hardstyle\>> size:66bytes
Does it give you more than one result?
I just realized that when using Everything, the command ignores the files you specify via FILES, since youâre asking a list of files to act upon. Sorry for the earlier bad advice. It might be worth adding an option to only use the defined files when Everything is in use.
I'm getting no results in my Everything search results.
Trying to make sure my typing is exact. Dunno, it's not showing the files in the list.
Windows Search is garbage. And so is having a permanent file collection because you wanted to temporarily find something. So I'm forced to use the Windows index.
Hold up. I had an idea. I moved the files to another location and as I suspected it's because the downloads folder is a virtual folder (as far as I can tell). I got both items show up in another folder.
Are you sure about that? Because the logs show youâre getting at least one result. Also, keep in mind this command is meant for Everything 1.5 or later.
Not sure about the rest either. FWIW this command doesnât create a collection unless you explicitly ask it toâit just gives you the files resulting from a filter (EV or Opus filtering), so you can run whatever commands you want.
And what do you mean by âpermanentâ? That you canât delete it later or something? You can always make a button to delete collections in one go, so theyâre not permanent at all.
Ya I had one result. The item that was selected remained selected so nothing changed.
The point is to select everything that is the same size so since there is two items it should have resulted with two things.
See my moving of the two files and changing the path I got the result.
So I checked your original code and yes it does work but not in the downloads folder.
I should have done that side test first, sorry.
I'm not talking about this script creating a file collection. Using the Dopus Find tool creates a permanent find collections, so I use Find Here RECURSE to drill into folders, so I'm forced to maintain a Windows index for that.
(Using your new, most recent button)
Ok, selecting same size on files is working. But still, the folders are not.
With Ctrl held down (or nothing held down) it should select the other same folder but doesn't.
But at least we discovered that the Downloads folder is an issue, so we can be aware of that.
That doesnât sound normal at all. Maybe thereâs something in your Everything config worth checkingâlike if youâve somehow excluded that folder or something similar.
I canât fully wrap my head around why a file collection would be seen as a âdiseaseâ to be avoided at all costs! Theyâre a super useful toolâI bet Microsoft wishes theyâd thought of that feature. And you can delete them when you donât need them anymore; theyâre not permanent!
Please post the script log again while holding down the Ctrl key.
You're right, I'm sorry. I had the downloads in the exclusions. My fault.
File collections are not a problem. As long as I have control of when I want to keep them or not.
Using the Windows search then saving the ones I want to keep is how I'm doing it. So that the default is discard then the exception to that rule is keep.
Just like Microsoft having the I attribute as 'Not Content Indexed'. ... what? You mean to tell me that applied is the default for all objects and removing it is the exception to the rule? Instead of just calling it 'Indexed'? Doesn't having another attribute cost more memory? Times that by billions and billions of files over millions of computers. Why not have all new files not have this added attribute, and then the indexer adding it when it indexes them? It's absolutely backwards and confusing. (Maybe for security reasons) but it's as backwards as the Dopus requiring me to make the exception to the rule the rule and forcing me to manually make the rule the exception. I wouldn't say a word about it if I could just disable the auto-permanent nature of the collections, but nope.
I also reminded Jon that moving search result collections into subfolders to have a proper folder tree structure in your file collections breaks its ability to refresh the same searches, but nope they don't care. While their tag system and date tracking is stuck in the commodore 64 era but hey the guy that says so is somehow in violation even though I'm right on the bullseye with these things.
...
Folder is selected. Another folder with the same size does exist in the folder.
Holding Ctrl while clicking on your button (most recent button).
Log:
30-Apr-25 09:53:PM LogicRun: INFO => === COMMAND BEGIN ===
30-Apr-25 09:53:PM LogicRun: DEBUG => cmdline : LogicRun FILES $visible_dirs$ IN "C:\Users\isme\Pictures\ismyPics\Forums\" GETPROPS
30-Apr-25 09:53:PM LogicRun: DEBUG => COMMANDS : true
30-Apr-25 09:53:PM LogicRun: DEBUG => USEEVERYTHING : size:$(sizeautoEV)$
30-Apr-25 09:53:PM LogicRun: DEBUG => FILTER : false
30-Apr-25 09:53:PM LogicRun: DEBUG => FILTERDEF : false
30-Apr-25 09:53:PM LogicRun: DEBUG => GET PROPS : 0
30-Apr-25 09:53:PM LogicRun: INFO => Validating 1 entries...
30-Apr-25 09:53:PM LogicRun: INFO => Expanding filter...
30-Apr-25 09:53:PM LogicRun: INFO => Getting values for "sizeautoEV"...
30-Apr-25 09:53:PM LogicRun: DEBUG => QUERY : size:1.16MB
30-Apr-25 09:53:PM LogicRun: INFO => Getting files using Everything...
30-Apr-25 09:53:PM LogicRun: DEBUG => ==> EV is running:true; autorun:false
30-Apr-25 09:53:PM LogicRun: DEBUG => ==> Waiting for EV database to be loaded: 1
30-Apr-25 09:53:PM LogicRun: DEBUG => QUERY : < <C:\Users\isme\Pictures\ismyPics\Forums\>> size:1.16MB !path:"$Recycle.Bin"
30-Apr-25 09:53:PM LogicRun: DEBUG => ==> Query finished, results: 0
30-Apr-25 09:53:PM LogicRun: INFO => ITEMS : 1
30-Apr-25 09:53:PM LogicRun: INFO => RESULTS : 1
30-Apr-25 09:53:PM LogicRun: INFO => Running command(s) in 1 file(s)...
30-Apr-25 09:53:PM LogicRun: DEBUG => => Select FROMSCRIPT DESELECTNOMATCH
30-Apr-25 09:53:PM LogicRun: INFO => ==> Command "Select FROMSCRIPT DESELECTNOMATCH" succesfully executed
30-Apr-25 09:53:PM LogicRun: INFO => === COMMAND END ===
If you're sure you can see more than one 1.16MB file listed, first check if you can get the results from the Everything window. Or you can try using Opus alone. (A starter template for the button is in my first posts in this thread).
Everything does give the correct folder results. My 'Folders index' area was empty but that's because folders are already included in the NTFS index area. I tried adding my pictures folder and it warned me that it's already indexed. I did it anyway and got duplicate results. Removed it and it's back to normal.
The button wasn't working for folders that are 66 bytes each. I added a bunch of files into them and it started working when the sizes were in the kilobytes. And worked at about 1.2 megabytes. Then stopped working again at 2.66 megabytes.