Script linearity

[jeroen]

The only difference is, first colors these files red, second green.

The colors are NOT the only difference. As I said before, ExcludeFiles will totally prevent files from being moved. Your little FileSelect trick is nice, but the files can still be moved when MyDefrag is processing a zone before your trick zone.

All defragmenting and filling commands and AddGap are already inside FileSelect.

No, they are in the FileActions.

I can run AnalyzeOnly script, see how bad does the disk look and decide whether I will use monthly, weekly, or daily optimization script. I think the script should be able to do that without need for the user to decide.

I can only repeat: already possible.

[Kasuha]

The colors are NOT the only difference. As I said before, ExcludeFiles will totally prevent files from being moved. Your little FileSelect trick is nice, but the files can still be moved when MyDefrag is processing a zone before your trick zone.

They are both executed at the place where they lie in the script. If I place my "zone" closer to ExcludeFiles (i.e. before all other zones) they do exactly the same. And if I can allow some files to be moved before I fix them to position, I consider it a feature.

But okay, there's no problem with it. As I said I don't think it's logical but now I accept that there is some logic behind it.

No, they are in the FileActions.

Okay... Sorry for not expressing it in a way you can understand. What I really meant was, AddGap should be part of FileSelect...FileActions...FileEnd structure instead of separate command. Something like
FileSelect
  <FileBoolean>
AddGap
  <Expression>
FileActions
  <Commands>
FileEnd.

I can run AnalyzeOnly script, see how bad does the disk look and decide whether I will use monthly, weekly, or daily optimization script. I think the script should be able to do that without need for the user to decide.

I can only repeat: already possible.

I can only repeat: not possible with single script. Did I say it should be in single script? Oh, I didn't. Okay, I do it now. I meant it should be possible to do in a single script, without user intervention. The script should be able to decide whether the disk deserves monthly, weekly, or daily optimization.

[jeroen]

What I really meant was, AddGap should be part of FileSelect...FileActions...FileEnd structure instead of separate command.

Ah yes, I see what you mean now.

I meant it should be possible to do in a single script, without user intervention. The script should be able to decide whether the disk deserves monthly, weekly, or daily optimization.

Copy the contents of the daily, weekly, and monthly scripts into a new script, so they are 3 blocks right after another. Then change the volumeboolean of the first block so it will only select disks that you think should only be processed by that block. For an example see FragmentedFiles. Do the same for the second block. The third block does not need any change because it will automatically be executed for any disks that were not processed by the first or the second block.

[poutnik]

There are several reasons why the whole list of files must be kept in memory and changing the scripting will not make it possible to use less memory. One of the most important reasons (there are more) is that MyDefrag must be able to find the (name of the) file that uses a particular cluster on disk. This information is not available from Windows. When you know the name of a file you can ask Windows which clusters it occupies, but that is exactly the other way around. 

In case of low RAMsize / FileNumber ratio, one need to choose
between Scylla of keeping limited info and reading what is needed
and Charybda of keeping all and swapping what is not needed. ( Odyssea )

[poutnik]

I meant it should be possible to do in a single script, without user intervention. The script should be able to decide whether the disk deserves monthly, weekly, or daily optimization.

Copy the contents of the daily, weekly, and monthly scripts into a new script, so they are 3 blocks right after another. Then change the volumeboolean of the first block so it will only select disks that you think should only be processed by that block. For an example see FragmentedFiles. Do the same for the second block. The third block does not need any change because it will automatically be executed for any disks that were not processed by the first or the second block.

I think Kasuha had in mind script runtime decisions, not user decisions at time of script design. I cannot but second that.

[poutnik]

ExcludeFiles lying outside VolumeSelect is beyond my logic, it should be one of VolumeActions. .........................................

........................................
By having ExcludeFiles outside the VolumeSelect it has become possible to globally define unmovable files, on all disks.

Why not have them both, like global and volume local settings ?