Took another look at the offsets today. Decoded most of it now (location given as decimal byte offset with start of the window data section as byte 1, order of bytes as written):
Data Locations:
Code:
PackLocation: 5 (BYTE)
Horizontal Position: 9+8+7+6 (DWORD)
Vertical Position: 13+12+11+10 (DWORD)
Width: 14+15 (WORD)
Height: 18+19 (WORD)
Visible: 22 (BYTE)
Then there are 6 DWORDs pretty much at the end of window data
which are for the opacity sliders.
They are followed by a couple of bytes that I do not understand yet.
Values for PackLocation (IMPORTANT: this is also the
Offset for the calculation of Location!):
Code:
0: left, top
1: center, top
2: right, top
3: right, center
4: right, bottom
5: center, bottom
6: left, bottom
7: left, center
8: center, center
9: left, top
10: left, center
11: center, center
12-FF: right, bottom
As you can see 9-12/FF appear redundant - I may have overlooked
special functionality associated with those (or not)
Values for Visible:
That's probably enough for you Landiin to change your UIsettingsSpy into a full blown UIsettings Editor. Btw I could not use the edit function of your tool, it would not write the correct values into the file (also in adjacent bytes not edited), I ended up doing all the above in my hex editor, was faster anyway.