I am a bit frustrated with the Events module.  I have spent what I would define as an inordinately large amount of time trying to change one element of the Events module to be skinned correctly.  I have everything else changed to the appropriate color except for the background color of the Selected Day.  To the best of my understanding this should be alterable in the .EventSelectedDay class.  As far as I can tell it is not.  I have looked at the source and I believe that my problem rests in an injected inline style.  The injected style sets the background color to Silver.  I have tried !important to override the inline style it failed, I have tried setting the "Disable Event Month View Inline Styles" and that fixed the problem, but then messed up the alignment of several other controls that I don't have the ability to address correctly to fix because of their inline style settings.  I have tried both the .EventSelectedDay class and the addition of a td to that class because it is in a td tag.  This failed in module.css, portal.css and skin.css.  I have checked about every article I can find on how to override inline styles, none of them have worked.  I have tried to find where this is injected in the core code, and cannot find it in a setting, which means it is probably in a .dll somewhere.  I don't want to have to go through all of the work to find it and maybe have to recompile the code for this simple setting.  This is a ridiculous problem to have, considering there is no need to have an injected inline style.  That is what CSS is for.  Does anybody have any idea of how I can override the default style to change the background color of the selected day in the Events module.  Any help would be appreciated. 

The current events module, not the beta.  No I didn't post to the events forum,  I have tried that in the past and received no respones.  On top of that, I have a feeling this is not directly tied to the Events module, I have a feeling this is tied indirectly to the skinning process itself.  There seems to be something working against the ability to skin this module and it seems to be tied into other css files in the skinning process.  That is a guess but it makes sense at this point.