KPerry
I was thinking maybe CupCake.

I like it. Plays on the "baker"/"cakewalk" element very well. Alternatives might be things like "LayerCake", etc, emphasing the deeper, "layered" look the utility gives you, but CupCake is perfect. Friendly, small, etc.
Other avenue would be the "Sonar" element - for example "Periscope" - but the other utility recently developed has the "Projectscope" moniker already.
Anyway - many thanks for your hard work and generosity in sharing this with the Sonar community. Great little utility.

Do you mind if I host it on my Onedrive? This is the last version I have 2.1.5632.19736  Is this correct?
I am putting together a storage space with public access for all the utilities created by Sonar Members

Thanks Kevin.
There are about 7 different utilities developed by current members here. I'm going to host them all in my Onedrive if the other developers agree and put a link to that in my signature along with a thread so people are made aware. After a while it's usually the case that some remember while most never knew about it. I'd like to give more people the benefit of the hard work that these people do.

Well with scooks recent SonarToolsEditor utility it is possible to add these programs to Sonar's Utility menu and launch them from there.

Are you using the latest version?

Follow the link in my signature to Cupcake 2.5-1

It's compiled for x64 only - I'm only able to practically test on Windows 7 and Server 2007 (at some stage I'll go to 10...when I have time!).

I can confirm its not working for windows 10  X64.
Looking forward to an update when your ready!

Cool does it add itself to the tools menu?

@Mudgel - could you add a note about incompatibility with Windows 10 alongside your download link, please?

KPerry
Reg file will save everything, including fields that aren't user-editable; it's perfect for a backup.  But if you want to edit "safe" fields such as names or transfer settings to another computer (or user), the XML is probably safer.

You may have address this later in the thread (perhaps page 2 or 3), and if I missed that I apologize.
 
I would think that if you had a process that ran as a user-triggered rebuild/recompile/data-update-function, then you could read an external file that contained your internal tables, or however your data is set up for the execution of the code.
 
So, rather than build up whatever internal data you are working with, that slows your current process down - doing it every time someone runs it, you have a separate process or some menu option when the utility starts, or done outside of Sonar altogether, do that process ONCE, and save everything that way, so it doesn't have to rebuild the same thing from the same data, every time.
 
Them, whenever an updated set of data needs to be absorbed by the utility, the user could run/trigger the functionality to rebuild the internal data and save the data in a single update run.  This way, the MAJORITY of the time, the utility would run super quickly, and only once in a while require the updating of the internals.
 
I guess you could also just compile up a new version of the utility whenever its internal data needs change, and just release it, and replace the obsolete one.
 
Just some thoughts on it :)
 
Bob Bone