Spacehog definition as Include macro in standard scripts

[poutnik]

Hi Jeroen,

why not to define Spacehogs  in standard scripts by !Include PATH! macro ?
They would become much shorter.
Furthermore, all standard and customized scripts can share the common definition.

[jeroen]

Thanks for sharing your idea, I appreciate it. Feel free to do so yourself, but I have found that people find the scripts easier to read and understand without redirections like that. So I have decided some time ago to have the list of spacehogs literally in every script.

[rlg118]

Having spacehogs in a separate routine is the way to go.

The professor who taught me programming years ago would be aghast at the idea of having reusable code repeated in every program instead of using a CALL.

[rlg118]

The syntax of MyDefrag changes with every release and scripts are generally not upwards compatible.

All the more reason for having this reusable code separate. It certainly does not make the scripts any harder to follow.

If you have customized the Spacehog listing, it has to be added to every script (standard and customized) with every new version. That could be a lot of work, especially if you have different procedures for different drives.

It seems that inserting the macro would be a lot easier to do than some of the other enhancements that are suggested in the Requests for New Features forum.

Just my 1/50th of a dollar... I'll go away now.

[MacJudge]

I also prefer some less redundant scripts, which made me write (or mostly copy and paste) the scripts I published in this post that are now finally working with 4.2.5.

But, as Jereon already told, the standard-scripts are restored with every new version, so that you have to copy your modifications to some other place before you upgrade. After this, you have to check for syntax-changes, which make your modifications not working any more.

Thats why I never use the standard-scripts and only look at them with every new version to improve my own scripts. Because my scripts have very little redundancy I finish this job quite fast, because changes have to be done at most time only in one (sub-)script.

[rlg118]

If every script had !include Spacehogs.myd! in it, that part would never have to be touched. Any other mods and you're on your own.

[poutnik]

similarly, I started to use  FastFill(!FFaction!] in my script,  calling it

dfrc.myd -m FFaction=                       for FastFill()  in daily-optimize-like variant, and
dfrc.myd -m FFaction=WithShuffling     for FastFill(WithShuffling) in weekly-optimize-like variant.

similar can be done for Defragment, but I use exclusively chunksize(64) variant.

[poutnik]

Or, similarly, keeping single custom stript with zone definitions, launching it by these commands,
either from shortcuts with parameters, either from CMD file.  ( this time verified )

dfrc.myd -m "Factions="                                   ( just cleaning gaps )        
dfrc.myd -m "Factions=Defragment(fast)"                                     
dfrc.myd -m "Factions=Defragment(fast) FastFill()"                       
dfrc.myd -m "Factions=Defragment(fast) FastFill(Withshuffling)"             
dfrc.myd -m "Factions=SortbyName(Descending)"               

and in the script there will be
Fileselect "zonedefinition" Fileactions !Factions! FileEnd