Observed Effects of the LGS Suite

Filenames

In Using Macro Files and Human Readable Profile Files there is mention of having to shut down LGS, then apply changes. The reason for this, through pure observation only, is that when LGS launches, it reads in all the profiles, and keeps them in memory. I've also noticed that at LGS launch, these XML files are all rewritten, ground up. So the file is first read in, processed, then written back out. If at any time the profile is changed within LGS, the changes are both written to memory and the the profiles XML file. So if you apply changes to a profile via your text editor, LGS does not read these changes in while it is running. If you apply a new change to a profile while in LGS, changes made outside of LGS are lost. So it is important to follow the order of operations.

• Close LGS
• Apply changes to your configuration
• Optionally close your text editor, with understanding that what LGS does will overrule your contents.
• Relaunch LGS

GUIDs in general

It seems that Logitech decided to generate GUIDs (Globally Unique IDentifiers) for every type of action and identifier that needs to be linked with another identifier or action. To the LGS suite, it seems that it doesn't matter what this ID value actually is, just so long it is properly linked. It also seems to be case insensitive, or, converts to uppercase.

The LGS suite seems to be generating version 4 of GUIDs, but whether or not the software actually acts on those values beyond the fact that they're a string, with my testing, I've not seen any issues crop up assigning a human readable string to individual values.