Add a recursive setting - fix #219

[Huluti]

TODO:

• update POT file
• to be tested

[ARAKHN1D]

I tested this on my system and found a couple issues:

• Using either recursive or non-recursive compression on a folder throws a FileNotFoundError. I looked into it and found out that in both of the get_image_files_from_folder functions, appending the image_file URI using get_uri() instead of image_file itself fixes the error.
• When using non-recursive compression on a folder with nested folders inside of it, the nested folders don't get searched for files. I'm not sure if this is intentional or not.

Besides those two things, I can confirm that this does fix #219. Nested folders don't get shown as unsupported formats anymore. I do have a question, though—is there a difference between recursive and non-recursive compression? Do they have certain pros and cons that mean both are viable options for different situations, or is one better than the other in all areas? Just curious.

[Huluti]

Thanks for testing this and finding this error (I wrote the code in the car and hadn't tried it yet 😅).

• When using non-recursive compression on a folder with nested folders inside of it, the nested folders don't get searched for files. I'm not sure if this is intentional or not.

That's the point of this "Recursive Compression" setting. Recursive mean that Curtail will go through all nested subdirectories to find images if enabled. If not, only images from the parent folder will be compressed.

I've set the parameter to true by default, leaving the option to deactivate it if you don't want it.

Is that clearer?

[ARAKHN1D]

Ah, my mistake. That's clearer, thank you.