Select Same?

Help & Support
1

No matter what I do I can't get Dopus to select by the same as the current selection.
Rating, file type, nothing. It just won't do it. How come I can do a select a rating=3 and it works fine? (Selects all items that match that pattern), or select by a date or file type, or anything at all, but it draws a line at whatever is currently selected. Why is this so difficult?

Just take the data of the item that's selected and select everything else in the folder that's the same. If I have a file selected with a rating of 3 and I push my select same rating button it should select all items in the folder with a rating of 3. This is pretty basic but Dopus just refuses to do it.

2

Select the same where and how?

In a button?

In a script?

Via the Filter Bar or FAYT or something else?

3

For buttons on my filter array. Command, script, I've tried both.

This doesn't work, for example:
Select filterdef rating match {file:rating}

I can select by all kinds of things, just not same. Here's the date created buttons.

Dates
Dates191Ă—159 4.96 KB

When a script has logging it says odd things like "rating undefined" or "this is not a file".
For same size, there might be a problem with Everything rounding the byte numbers before sending it to Dopus, so the button can't get an exact match and fails to match, but I'm not sure.

4

DId AI tell you {file:rating} was a thing? Because it's not a thing.

5

Is my desire possible?

6

You could probably do it with a script.

7

Yes, with this same script :
A newer version:
LogicRun.opusscriptinstall v0.99.6.opusscriptinstall (7.4 KB)

And the button:

LogicRun FILES $all$ GETPROPS {allfilepath$} 
[[
FILTERDEF
=return $(rating, OR ,rating==)$
]]
[[
COMMANDS
Select FROMSCRIPT DESELECTNOMATCH
]]
  1. It probably can't select nested items in expanded folders.
  2. Check the issue with archives.
1 Like
8

I remember this now. I stopped using that script because of the select same size issue we couldn’t figure out. That’s about when I started asking the clankers for help.

This ratings variation is working good, thanks a bunch. Here’s some cookies 4 u :cookie::cookie::cookie:
No cookies for these unhelpful devs.

Could I put a quiet argument somewhere in that button to make it work without the progress pop up? I assume that I can replace rating in the brackets with other metadata?

For the archives issue have you come across File Association Manager before?

I’ve heard good things, that it can register unsupported metadata file types with the windows properties table. I haven’t tried it yet though.

9

If you want the devs to be helpful you should ask them constructive questions, not come in ranting and raging because the AI nonsense you've been trying doesn't work :wink:

4 Likes
10

And this is why asking on this forum is my last resort.

11

The problem with sizes is that, unless you want the exact number of bytes, the results are a bit confusing. In fact I have a post about it with no replies so far; I didn't try anything after that.

I'll consider some option for that.
The main issue with that approach is that there'd be no way to know what the command is doing, or to stop it. This is more noticeable when it's used with lots of files. A better option might be adding a delay before showing the dialog, so it won't pop up if the operation finishes quickly.
Actually, this script was actually a bit forgotten; I'll update and polish it when I have more time.
(One drawback for that with this and my other scripts is the lack of feedback, probably because they're not used much or something like that. That also kind of puts me off releasing new versions or other scripts.)

1 Like
12

For a simple execution like same rating, I think hidden process is better. It happens so fast that what I see is just a blip of a window, which is not ideal. I think maybe runmode:hide is the command for that, but I dunno. If I could just put a modifier in the button itself instead of you having to modify the script then you could keep the script as is but have variations like “hide progress” on some of the buttons that don’t need it.

I see your post about the size issues. Ya that’s puzzling. I wonder if the find tool is drawing its data from somewhere other than where the columns are, or where a button would. Or if all things are drawing from the same index but are interpreting it differently. I’m just speculating. I would just fix up all these problems myself if I could.