Hi Dino,
Like I said before, your app is getting to look real smart. I've had a
look under the hood and it's getting tasty in there too!!
)
The variable pixel border on resizing is now dealt with but you'll have to
set a correct minimum size for the form. I've also made the cell borders just
a pixel wide by overlapping the edges.
I've done a lot of work in making it faster and cleaner when you move
forward and backwards between the months.
In the course of doing that I moved a lot of the graphical stuff into the
CalendarCell where it belongs. You're new to UCs and I was only able to
vaguely explain it in the earlier posts, but the UC should do as much for
itself as possible, and the user of the UC (ie. the Form) should have
properties and methods that ask it to do these things.
The idea about a UC is that as far as possible, it doesn't let the user
play with its innards. So rather than letting the Form have access to the
label and textbox so that it can set colours and do painting, etc, the form
tells the Cell to enable or disable, to show the day highlighted, etc. The
cell works out how to actually do that. In other words the Form thinks in
terms of calendar type things, like "this cell is today's so let's highlight
it" and the Cell thinks "I'm highlighted so my label's font and colours ...
etc".
The Cell is now responsible for showing itself when selected. This works
with the Tab key as well as the mouse. There is a wierd thing when tabbin left
from Day 1. It takes 7 left tabs to get to the buttons and I suspect that the
CellHeaders are getting the focus - despite them having TabStop set to False.
I didn't have time, though.
I see a need for classForms and modForms to be merged but again didn't
have time to get involved in that.
I look forward to seeing the next stage. ;-)
Regards,
Fergus