FileSet features I'd like to see

FinalBuilder Feature Requests
1

These are both minor issues, easy to work around, but would be nice polish:

  1. FileSet to Variable should have Include path and Include relative path checkboxes like File/Fileset Iterator does. For my use I only wanted the filenames.
  2. FileSet Copy/Move has an Overwrite existing files checkbox, but if you do a move rather than a copy the action still fails with a “File already exists” error.
2

These are both good ideas, we’ll look at implementing them this week.

3
  1. implemented
  2. I could only reproduce this when the setting to overwrite read only files was enabled - fixed.

https://downloads.finalbuilder.com/downloads/finalbuilder/860/FB860_3672.exe

4

Thanks, Vincent :slightly_smiling_face:

One small quirk: In File/FileSet Iterator the Include relative path when setting variable checkbox results in strings like .\filename.txt while the FileSet to Variable’s new behavior for Include Relative Path returns strings without the leading period so it’s \filename.txt. Personally I’d have preferred that both cases omit the leading .\ entirely so you’d just get filename.txt or dir\filename.txt without a path component, though obviously changing that could break someone else’s script, but it feels like they should be consistent with each other.

5

Ah, the iterator is using a different method to get the relative path.

Yes, backwards compatibility is extremely important - what seem like simple changes can break things elsewhere - it’s impossible to know how users are using actions which call the internal ExtractRelativePath function. There are unfortunately lots of little inconsistencies scattered through the various actions (25 years and many devs later) - which I would love to fix - but I know many of them would break peoples projects.

https://downloads.finalbuilder.com/downloads/finalbuilder/860/FB860_3673.exe

6

Was that new build supposed to change something? Stripping the leading \ or .\ was trivial in the script I had, so it’s fine either way, but I’m still seeing the same mismatch between the relative paths returned by the two actions.

1 FileSet Define
1 FileSet Define560×554 13.6 KB

2 FileSet Define 2
2 FileSet Define 2560×554 8 KB

3 FileSet to Variable
3 FileSet to Variable560×554 10.6 KB

4 FileSet Iterator
4 FileSet Iterator560×554 13.3 KB

5 FileSet Results
5 FileSet Results596×319 11.3 KB

6 FinalBuilder Version
6 FinalBuilder Version474×209 2.09 KB

7

Well it would have, if I had commited all of the changes - for some reason I only committed half the files changed. My apologies.

https://downloads.finalbuilder.com/downloads/finalbuilder/860/FB860_3674.exe

8

Not a problem at all, thank you. I’ve certainly had my fair share of “simple, easy to implement” feature requests that turned into bigger time sinks than you’d think.