The program parses cinf resources now. SHHHHHHHHHHHH! (These are Kaleidoscope proprietary resources.) I won't release the code for this until we at least go to some reasonable effort to get permission from the Kaleidoscope guy if we can find him.

So the converter uses the cinf resource to parse out the cicn images for controls. For example, sliders, tabs, buttons, etc. The image part of it is working already, but there won't be a one-size-fits-all layo resource like there was for window frames, so that has yet to be developed. The layo resource tells themes where to put images and gives them clickable / visible characteristics. So I will have to convert info from the cinf into the layo for each control.

Scroll bar buttons will be a whole separate header and source file I think, I'll put that off. There are other things I can do that affect a whole range or parts in the theme.

Concerning the "wnd#" resources, those are tricky because of stretch and collapse regions. I'm not exactly sure how to translate those into a layo. layos use centering coordinates and collapse items individually, which is more versatile. It seems that this should be possible with some clever hacking. But once again, wnd# is Kaleidoscope-proprietary.