How does FastFill() handle fragmented files

[ScorpionGTfx]

So, as I was writing before (and in other threads too), if FastFill will consider Wrap-around fragmentation, then the problem you just described shouldn't be anymore . So I continue to not understand what are these cases where FastFill (with wrap around) might make things worse...

[poutnik]

So, as I was writing before (and in other threads too), if FastFill will consider Wrap-around fragmentation, then the problem you just described shouldn't be anymore . So I continue to not understand what are these cases where FastFill (with wrap around) might make things worse...

IMHO
1) Wrapping flag should be global and Fileactions should respect the setting in both evaluation and writing.
2) Wrapping ( and "dewrapping" ) decision should be based 
       on how wrapping would be (is) done      ( what affects performance )
       and not on what would be (is) wrapped  ( what does not affect performance )

[BloodySword]

No. Wraping should be a individual setting for each command.

[poutnik]

Then they could fight over to be wrapped or not to be wrapped, if set not to be in harmony.
Another option could be that a command setting would overrule a global setting. ( not needed to be global, volume wide would be enough )

[BloodySword]

Last point is acceptable. You always have to think about other opinions not only of your own in a community. It's not easy but neccessary for good features.

[poutnik]

Last point is acceptable. You always have to think about other opinions not only of your own in a community. It's not easy but neccessary for good features.

Then remember your own words...