> 1. parser should recognize html comments in theme.xml.
That's on the todo list.
> 2. theme path should probably be pointing to _the_ xml file, not
directory.
> then directory would be assumed one level up the xml file path.
Nope, that's correct, as Isaac pointed out.
> 3. <textcontrol> should have means of specifying font used
That's not very easy to do. Consider that themes are cross platform -- how
do you specify the fonts for all platforms? What if the font is not
available on that machine?
> 4. should be able to omit controls from theme.xml - currently if
> some control is not specified, .ui traps.
That's a bug. I'm planning to allow the xml file to specify more than one
window, so the user can switch from a normal window to something like a
window shade window. A window shade window will obviously have fewer
controls in it...
> 5. theme window is not get masked properly on my system, any ideas why?
I just fixed some bugs in that. Check it out again after the next theme
check-in.
> 6. need 'minimize' button type
That's on the todo list. The number of controls is far from complete.
> 7. i am creating a theme, based on the liquified visions skin from
rainplay
> (ui/rainplay/skins/visions), for some reason minimize/exit 'buttons'
initially
> do not get drawn - when I move mouse over them, they get draw just fine...
> a bug?
Sounds like it... But, its too early to go hunting for that bug. I'm still
making quite a few changes as I go.
> 8. when one moves mouse really fast out of window, control does not
realize
> that it has lost it's 'mouse over' if it had one - need some
garbaga-collector
> thingie on, say, separate thread, checking if mouse is completely out of
> player window...
I've seen that. I'll put it on my list.
> 9. should be able to supply tooltips for buttons (well, anything).
I'm not planning on doing that initially. The planned freeamp skin will
display some text explaining the function of a button in a status field in
the player when the mouse is moved over that button. Once things stablize a
bit more, feel free to implement the tooltips.
> 11. should be able to specify multiple 'quit' buttons (other buttons too)
> (now that's flexibility ;)
Eeek.
> Yeah, and the coordinates for "rect="'s are somewhat wacky, i find.
> I think x2 and y2 are being handled as 'non-inclusive' coordinate, or
> something to that effect. I'll investigate.
That has been fixed as well.
> and, i think buttons.bmp still is not good in CVS. true?
Yup. I dunno why that one barfed. I'lll clean it up with the next check-in.
--ruaok Freezerburn! All else is only icing. -- Soul Coughing
Robert Kaye -- [EMAIL PROTECTED] http://moon.eorbit.net/~robert
