MFC timer IDs used to handle docking capabilites are in very normal usage range - by Marc_75

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


2
0
Sign in
to vote
ID 641100 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 2/3/2011 2:21:27 AM
Access Restriction Public

Description

The following timer IDs exist in afxdockablepane.h

// auto hide timer events
static const UINT AFX_AUTO_HIDE_SLIDE_IN_EVENT     = 1;
static const UINT AFX_AUTO_HIDE_SLIDE_OUT_EVENT    = 2;
static const UINT AFX_ID_CHECK_AUTO_HIDE_CONDITION = 3;

These IDs can simply conflict with existing timer IDs.

I would have expect MFC timer to be in a sort of preserved ID range as is the case for almost any MFC specific IDs.

Of course the workaround is simple: just use other timer IDs to avoid any conflict, but these issues or precautions are not listed anywhere in the MFC documentation
Sign in to post a comment.
Posted by Microsoft on 2/8/2011 at 10:01 AM
Hello,

Thanks for the report. This issue has been fixed in MFC for the next major release of Visual Studio.

Pat Brenner
Visual C++ Libraries Development
Posted by Microsoft on 2/3/2011 at 2:58 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)