Yes, I figured out that I was getting the right constructor.
I just got it working. I assume it is some problem or feature
with memory management on the C++ side. I changed my python code
to retain no references to the wxCalendarDateAttr's, creating each
instance dynamically as a parameter when I need it, and everything
works ok.
Is that a general rule, that I should not hold on to a parameter
that is shown as a pointer in the wxPython docs?
I also notice 2 things:
1. It looks like it is pointer semantics on the C++ side. Changing
the attribute for 1 day can cause the calendar display to change for
other days if the days are sharing the same wxCalendarDateAttr.
2. Changing the month doesn't clear the attributes and give you a
clean month to start with.
(1) + (2) + not holding any references implies that the first
thing to do when the month changes is usually going to be to give
each day its own clean attribute before changing any attributes.
It seems to be working OK for me now. I'll holler if it erupts
again, but for now, everything looks pretty good when I follow the
above.
Al