copyto w/o the stats

[MBaas]

I have a script that copies files using copyto. After the copy it usually shows the stats:

23-04-2025_13-22-52.png (20.45 KiB) Viewed 290 times

If I understood the doc correctly, [pop_stats] should help to suppree that dialog, so I was hoping

Code: Select all

copyto $tp , $f , 9:=0; 

would do it _ but I still get those stats.

I think my counting is correct

Code: Select all

copyto [location], [source], [rootpath], [flags], [autorichop], [on_collision], [preserve_dates], [create_log], [pop_stats], [skip_junctions], [verify], [show_progress]
                 1               2            3              4            5                   6                       7                        8                   9                  10                 11                                                                       

so I don't understand why it still shows it...

Any ideas, anyone?

[highend]

Counting args starts with 0, not 1...

[MBaas]

Ouch! Thanks!

So I changed to

Code: Select all

copyto $tp , $f , 8:=0;

- but it still shows the stats! ???

[highend]

Not here...

[MBaas]

Hmm, but that line of code was directly taken from the .xys, no edits. Maybe it's a side-effect of other things I'm doing in that script?

But the only candidate for that could be

Code: Select all

setting "BackgroundFileOps", 0;

, I think (the other stuff that script is doing is bit of filename processing with gettoken and old files are deleted with delete.

[jupe]

Are you by chance using the tB version?, because I think this is a known issue in it that hasn't been resolved yet.

[MBaas]

Thanks - that's it! I am mainly running TB since it already is so good, so I forgot the possibility it might due to that

[admin]

Are you by chance using the tB version?, because I think this is a known issue in it that hasn't been resolved yet.

The issue is that any non-default settings are not honored by the background copy process?

[MBaas]

Well, to be exact, the issue is that the specific setting is provided in the call's arguments is not considered. And the default for custom copy is also set to not show the summary report.

24-04-2025_14-13-29.png (102.5 KiB) Viewed 194 times

[admin]

So only scripted operations are affected?

[MBaas]

yes, I think so.

[jupe]

The issue is that any non-default settings are not honored by the background copy process?

I haven't investigated myself, but based on user feedback, copyto\moveto\backupto\sync all seem to keep the custom copy dialog open after file operation, and it doesn't seem to matter if its BJ or not, and it doesn't seem limited just to scripting. A couple examples,

viewtopic.php?p=228325#p228325
viewtopic.php?p=228095#p228095

[jupe]

It looks like this issue should now be fixed in XY tB .0307 if you wanted to test.

[MBaas]

Yes, it is!