I want to create a simple user button that does the following:
Goes to my specified folder and then filters for a specific extension (*.flv) for example and then returns the result in the current lister WITHOUT opening a separate result collection. The results should remain in the current lister so I can still see the other lister on the other pane.
Currently this is my command
When I run this...it goes to the folder but only brings up the filter dialog and doesn't run the command. I have to run it manually and the result of this is the filters are collected in a separate lister that takes up the entire screen.
I want the button to run the command and the result to remain in the current lister without expanding into a separate lister hiding my current Command Lister viewer setting. Is there a way of running the user command to do this? Thanks.
Do you want it to filter the view to show *.flv, or to search the folder and subfolders and display the results in the current window?
If you want the filtering option, do you only want to see *.flv in the current directory, or in it and all subdirectories?
[quote="nudel"]Do you want it to filter the view to show *.flv, or to search the folder and subfolders and display the results in the current window?
If you want the filtering option, do you only want to see *.flv in the current directory, or in it and all subdirectories?[/quote]
I want it to filder the view to show *.flv in the current directory window only.
Try changing your button commands from this:
Set SHOWFILTERFILENAME *.FLV
Thanks. This worked perfectly. Now...how come the user manual doesn't give this example, hmm? I couldn't find it. It's a godsend to have this discussion forum.
One last tweak...how do I get the results sorted by last date modified? What command will do that? Thanks in advance.
Oh I'll bet it's in the manual somewhere.
To answer your question though, add one more line to your button commands:
Set SORTBY=modified SORTREVERSE=On
If you don't want it reverse sorted, just remove the last part of that line.
If the manual had every example of every command (or combination of commands in this case) that Opus could do then it would still be being written.
Of course, more examples would not be a bad thing but there's always going to be something someone needs that doesn't have an explicit example. Sometimes you have to ask in the forum or read the Raw Commands section of the manual and work out how to do things from what's on offer. Don't worry, it gets easier as you use things more and you usually get a quick response from the forum if you get stuck or don't know where to begin.