SetFileColor

[Dezeer]

The newest mydefrag 4.0 doesn't recognize the SetFileColor command for some reason.

[kandro]

Works fine for me.

See Formal script grammar for positioning:

<VolumeAction>
::= 'ReclaimNtfsReservedAreas' '(' <Settings> ')'
  | 'FileSelect' <FileBooleans> 'FileActions' <FileActions> 'FileEnd'
  | 'MakeGap' '(' <MakeGapOptions> ')'
  | 'DismountVolume' '(' ')'
  | 'DeleteJournal' '(' ')'
  | <Setting>
  | 'SetFileColor' '(' <FileBooleans> ',' <FileColorBooleans> ',' <Number> ',' <Number> ',' <Number> ')'

[jeroen]

The newest mydefrag 4.0 doesn't recognize the SetFileColor command for some reason.

SetFileColor is not allowed as a FileAction (because the FileBoolean would interfere). You have to use it outside a FileSelect-FileActions-FileEnd structure.

[Harald]

The newest mydefrag 4.0 doesn't recognize the SetFileColor command for some reason.

SetFileColor is not allowed as a FileAction (because the FileBoolean would interfere). You have to use it outside a FileSelect-FileActions-FileEnd structure.

It seems then that the FILESTATE "selected" becomes meaningless since no files are selected outside FILESELECTS.
(quoting from the manual: "Files go through the following stages as they are being placed in zones: from "not(Selected) and not(Processed)", to "Selected and not(Processed)", to "Selected and Processed", to "not(Selected) and Processed".")

[jeroen]

It seems then that the FILESTATE "selected" becomes meaningless since no files are selected outside FILESELECTS.

Files have 16 different states (all the possible combinations of Fragmented, Movable, Selected, and Processed), and each state has it's own color. SetFileColor is used to setup all these colors. Usually you will setup the same colorset for all files, but it is possible (with the FileBoolean) to setup a different colorset for different sets of files.

Setting colors inside the FileAction is not possible because the actions will change the state of the files. For example files that become unfragmented while the Defragment action is being executed. Colors therefore have to be setup earlier, before the fileactions.

[Dezeer]

The newest mydefrag 4.0 doesn't recognize the SetFileColor command for some reason.

SetFileColor is not allowed as a FileAction (because the FileBoolean would interfere). You have to use it outside a FileSelect-FileActions-FileEnd structure.

Ok, then it can't be put in the settings file?

[Harald]

Setting colors inside the FileAction is not possible because the actions will change the state of the files. For example files that become unfragmented while the Defragment action is being executed. Colors therefore have to be setup earlier, before the fileactions.

OK, that makes sense. Thanks for clearing up my misunderstanding.

[jeroen]

Ok, then it can't be put in the settings file?

Ah! Now I get it. It should be possible to use SetFileColor in the settings file, yes, but I see that I forgot to add it there. At the moment you can only use it inside a VolumeSelect. Will be fixed in the next version.

[rstarkov]

Ah! Now I get it. It should be possible to use SetFileColor in the settings file, yes, but I see that I forgot to add it there. At the moment you can only use it inside a VolumeSelect. Will be fixed in the next version.

It would be really cool to place SetFileColor with FileBooleans inside the Settings file - doesn't seem to be possible in 4.3.1.