[Feature Request]: Recursive updating of custom palette XML files

[PWagner1]

As per discussion Krypton-Suite/Standard-Toolkit#1552 (comment)

[giduac]

There are some themes in there that carry a version number in the file name.
How would that be handled if, let's say, the version for all files should be set to N while some files have a different number in their file name.

Updating all xml files in a directory structure with a certain number can be done.

[PWagner1]

There are some themes in there that carry a version number in the file name. How would that be handled if, let's say, the version for all files should be set to N while some files have a different number in their file name.

Updating all xml files in a directory structure with a certain number can be done.

Hi @giduac

Need to strip all (or delete) files of _vX so that there is a 'base' version of the file, then within the code logic create a directory named vX, then place all the 'upgraded' files within that directory.

Hope this makes sense :)

[giduac]

Can you please write that out more explicit and complete including the various conditions so we have a clear description of what should happen under which circumstances?

[PWagner1]

Can you please write that out more explicit and complete including the various conditions so we have a clear description of what should happen under which circumstances?

Hi @giduac

Yes sure

1. Remove or rename any files that have _v# in them, to create a 'base' version of the palette
2. Create or update the existing 'Palette Upgrade Tool' UI to accept folders as a input/output (possibly use list boxes, so that the user can see the contents of the directory)
3. Update the existing 'Upgrade' button code to utilise the KryptonCustomPaletteBase upgrade features (possibly use a foreach loop here?)
4. For the output directory use the default name as the current palette version. This is already defined in the TKs GlobalStaticValues, so use this as it'll make it easier to support in the future
5. Possibly allow the folder to launch the new folder in explorer once 'upgrading' is complete

[giduac]

Some more questions please.

• Be more specific per item.
• To come to a full functional description which completely takes out the guess work.

[PWagner1]

Some more questions please.

• Be more specific per item.
• To come to a full functional description which completely takes out the guess work.

Hi @giduac

I think I've got it... let me know if you want to see the full code...

// Validate output path to check if it exists
            ValidateOutputPath(ktxtOutputDirectory.Text);

            // Loop through the file array
            foreach (var paletteFile in GetPaletteFiles(ktxtInputDirectory.Text))
            {
                // Upgrade the file and store it into the newly created directory
                kcpbUpgrader.ImportWithUpgrade(File.OpenRead(Path.GetFullPath(paletteFile)));

                // Export the file
                kcpbUpgrader.Export(File.OpenWrite($"{ktxtOutputDirectory}\\{paletteFile}.xml"), false);
            }

cc. @Smurf-IV

[giduac]

Yeah sure, push the branch...

[PWagner1]

Yeah sure, push the branch...

Ok, so its under https://github.com/Krypton-Suite/Theme-Palettes/blob/alpha-paletteupgradetoolredesign/Applications/Source/Palette%20Upgrade%20Tool/Palette%20Upgrade%20Tool/UI/PaletteUpgradeTool.cs

[PWagner1]

@giduac It's still very much alpha software

[PWagner1]

So, the logic works, but we hit a snag here...

Any ideas @Smurf-IV?