Scripting: rich operations

[jacky]

- I'd still like a scrollto command very much.

- But one thing I would really love right now, is the ability to start a rich operation from scripting. Of course there are requirements in the source items for this to work (they all need to share a same parent), but if the items-list as source doesn't match the command could simply fail I guess. But I'd really love an extra param <path> for copyto/moveto, with <path> being the equivalent of the search location when used in XY.

For example, I have a script currently that I use when working on different projects, and right now the script does a goto to the destination (since there's no scrollto, so it's quite slower since it's a network location) and then run a search on the source location (inc. subfolders). But then I need to manually locate & select all items that have been created/modified since last time and that needs to be copied, then I drag&drop them to do the rich copy.

My script can (and very soon will) take care for me of determining which items have been created/modifed, and so needs to be copied. But the thing is, I can't simply do a copyto with that list of items because obviously there's a structure to be preserved and I need to do a rich copy.

I guess I could sort the list, select items in root folder and copyto there, select items in a subfolder and do a copyto there, and so on for all different folders, but that sounds very much like a PITA, really. If I could just add an extra param <path> (source "root" folder) to copyto to get a rich operation going, that would really be awesome!

[admin]

Possible, though not before 7.80. And I'd need a better term for the extra argument, not just "path". No idea currently...

Would be an extremely powerful feature for those who understand it. I think Rich Copy generally is one of the most underestimated killer features here. And it's almost 9 years in the app now!

[jacky]

Possible, though not before 7.80. And I'd need a better term for the extra argument, not just "path". No idea currently...

Would be an extremely powerful feature for those who understand it. I think Rich Copy generally is one of the most underestimated killer features here. And it's almost 9 years in the app now!

hmm... <root> or <richroot> ? Since it's just that, the root for the rich operation...

Rich operations are great features for sure, and I can't wait for 7.80 now

[admin]

Possible, though not before 7.80. And I'd need a better term for the extra argument, not just "path". No idea currently...

Would be an extremely powerful feature for those who understand it. I think Rich Copy generally is one of the most underestimated killer features here. And it's almost 9 years in the app now!

hmm... <root> or <richroot> ? Since it's just that, the root for the rich operation...

Rich operations are great features for sure, and I can't wait for 7.80 now

I added it because it's just to cool to wait any longer!

I'm just having a blackout, because I cannot make up any good reason for this age-old restriction:

Code: Select all

Note that Rich Operations only works with files, not with folders.

Can you? Otherwise I would remove it... works well apparently. Sure you have to take care that your source list does not have items that contain each other, else you get lots of "overwrite?" prompts -- but that's your responsibility and not really dangerous.

[jacky]

I added it because it's just to cool to wait any longer!

/me is dancing now!

I'm just having a blackout, because I cannot make up any good reason for this age-old restriction:

Code: Select all

Note that Rich Operations only works with files, not with folders.

Can you? Otherwise I would remove it... works well apparently. Sure you have to take care that your source list does not have items that contain each other, else you get lots of "overwrite?" prompts -- but that's your responsibility and not really dangerous.

I think the idea was just that, to avoid "unnecessary" overwriting prompts. And also you probably thought it made sense mostly/only for files, because I guess usually you don't want to keep empty folders around in rich op. cases, only preserve the structure of a group of files...

But I don't think it would be a problem to get ride of that limitations, no.

[jacky]

Yep, this is very cool. Now I got my script done, and I don't have to do any work : XY determines which files must be dealt with, and rich copy them on its own... I just sit back & wait, very zen

Thanks again for this great addition!

[admin]

Yep, this is very cool. Now I got my script done, and I don't have to do any work : XY determines which files must be dealt with, and rich copy them on its own... I just sit back & wait, very zen

Thanks again for this great addition!

I wish I had the time to write great scripts for myself. Maybe some day when XY is finished (HA HA HA)...