DateTimePicker using Themes

  • Thread starter Thread starter Berndt Johansson
  • Start date Start date
B

Berndt Johansson

Hi

If I enable the theme support on my .NET 1.1 WinForm application that uses a
number of DateTimePicker controls the checked property of the DateTimePicker
will not work properly. I have seen some posts in groups about this problem
and our quick solution has been to remove the manifest file from the
shipment and our application currently use the W2k appearance, however the
users aren't very happy about it.

Has anyone been able to find a workaround for this problem? In other words I
would like to use the XP themes AND still use the DateTimePicker control. I
have been thinking about drawing my own checkbox control and override the
Checked property, but doing that could be potentially bug-prone.

/Berndt
 
Hi Berndt,

There are several issues might occur when you use DateTimePicker control
with XP visual style enabled, from your description I'm not sure what issue
you referred to, but have you read this article on CodeProject?

http://www.codeproject.com/cs/miscctrl/DateTimeSlicker.asp

It provides some workaround and enhancements to DateTimePicker control,
does it resolve your problem?
If it does not provide workaround to your problem, could you give me some
detail information about the problem you met?

Thanks!
Best regards,

Ying-Shen Yu [MSFT]
Microsoft Community Support
Get Secure! - www.microsoft.com/security

This posting is provided "AS IS" with no warranties and confers no rights.
This mail should not be replied directly, please remove the word "online"
before sending mail.
 
Hi

Yes it solves my problem with the Checked property not returning the correct
true or false value of the checkbox control in the datetimepicker control.
I'll make some further tests on the enhanced control, but it looks very
promising.

When will MS fix these issues on the control? Any updates to VS.NET 2003 or
will it be in VS.NET 2005?

/Berndt
 
Hi Berndt,

Actually this issue is a problem in comctl v6, so the fix is not licked to
be included in VisualStudio. Currently, windows prodout group is planning
to fix it in next release of Windows, the fix maybe included in service
pack in the future but I'm not clear about it.

Best regards,

Ying-Shen Yu [MSFT]
Microsoft Community Support
Get Secure! - www.microsoft.com/security

This posting is provided "AS IS" with no warranties and confers no rights.
This mail should not be replied directly, please remove the word "online"
before sending mail.
 
Back
Top