I set VerifyCopiedFiles in LastRun.ffs_gui to true. When FFS closes it sets it
back to false.
VerifyCopiedFiles Not Sticking
- Posts: 8
- Joined: 15 Jul 2010
-
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
This flag is read-only, i.e. it is not written when a config file is saved,
but reset to its default value. Using it in a file other than LastRun.ffs_gui
will work as expected.
but reset to its default value. Using it in a file other than LastRun.ffs_gui
will work as expected.
- Posts: 8
- Joined: 15 Jul 2010
I can put it in a custom configuration, but then have to remember to load the
configuration. How do I make it the default?
configuration. How do I make it the default?
-
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
With the current implementation it is not possible to use it in combination
with LastRun.ffs_fui. There are two settings that are affected by this
restriction: VerifyCopiedFiles and FileTimeTolerance. The "problem" that this
restriction is supposed to solve is that these values get copied silently
between configuration files as they are not shown on GUI.
with LastRun.ffs_fui. There are two settings that are affected by this
restriction: VerifyCopiedFiles and FileTimeTolerance. The "problem" that this
restriction is supposed to solve is that these values get copied silently
between configuration files as they are not shown on GUI.
- Posts: 8
- Joined: 15 Jul 2010
Can you add something to the GUI in a future release to allow this setting to
be set and saved?
be set and saved?
-
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
In general I try to keep the GUI lean from very advanced or less frequently
used options like in this case. Adding it to the global settings would remedy
the "not saving" issue. But then again having "verify files" global for each
sync-job is probably a bit too much.
used options like in this case. Adding it to the global settings would remedy
the "not saving" issue. But then again having "verify files" global for each
sync-job is probably a bit too much.
- Posts: 8
- Joined: 15 Jul 2010
Putting it in global settings or Default.ffs_gui makes sense. If someone sets
it there they do want verification on all sync jobs. Otherwise if it's in a
custom configuration and they forget to load it, they'll have to re-compare
everything again. And if they load a custom configuration there's a prompt
when closing if you want to save the configuration. Verifying everything is
not too much because if someone doesn't want verification on everything, they
wouldn't change the setting. If they do set it, then it's their intention to
verify everything.
it there they do want verification on all sync jobs. Otherwise if it's in a
custom configuration and they forget to load it, they'll have to re-compare
everything again. And if they load a custom configuration there's a prompt
when closing if you want to save the configuration. Verifying everything is
not too much because if someone doesn't want verification on everything, they
wouldn't change the setting. If they do set it, then it's their intention to
verify everything.
-
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
Having a "hidden setting" is a messy thing in general. Especially when it
operates at sync-config level where it's not transparent for the user when a
setting is copied between innocuous save operations. This is problematc when
such a setting changes the meaning of a sync-job, as for "filetime tolerance".
It's clear that it shouldn't be transferred without notice. Having these
settings at global level solves this particular problem, but at the cost of
granularity. Something has got to give, granularity or (slightly) cleaner and
less implicit design. I'll go for the latter and move these two options
(verify copied files, file time tolerance) into GlobalSettings.xml.
Implemented for v3.9
operates at sync-config level where it's not transparent for the user when a
setting is copied between innocuous save operations. This is problematc when
such a setting changes the meaning of a sync-job, as for "filetime tolerance".
It's clear that it shouldn't be transferred without notice. Having these
settings at global level solves this particular problem, but at the cost of
granularity. Something has got to give, granularity or (slightly) cleaner and
less implicit design. I'll go for the latter and move these two options
(verify copied files, file time tolerance) into GlobalSettings.xml.
Implemented for v3.9
- Posts: 8
- Joined: 15 Jul 2010
Excellent! Thank you!
