Re: Bug in CFrameWnd::OnInitMenuPopup (MFC 7.10)
From: Keith MacDonald (nospam_at_parasites.com)
Date: 05/06/04
- Next message: Finn Arildsen: "Re: MFC MDI question"
- Previous message: Das.Peter: "Re: CSocket ERROR ?? (transfer more as 100KB)"
- In reply to: Yan-Hong Huang[MSFT]: "Re: Bug in CFrameWnd::OnInitMenuPopup (MFC 7.10)"
- Next in thread: David Lowndes: "Re: Bug in CFrameWnd::OnInitMenuPopup (MFC 7.10)"
- Reply: David Lowndes: "Re: Bug in CFrameWnd::OnInitMenuPopup (MFC 7.10)"
- Reply: Yan-Hong Huang[MSFT]: "Re: Bug in CFrameWnd::OnInitMenuPopup (MFC 7.10)"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 6 May 2004 10:09:56 +0100
> Writing a KB article is not a easy thing. It contains many steps such as
> tech review, content review...... So it also takes some time unless it is
> quite time critical.
Hello Yanhong,
That's why I am disturbed that you have a bug database for internal use
only. Microsoft have obviously decided that their time is more important
than that of their customers, as the following case will exemplify:
Last year, I spent a long time trying to solve a problem that some of our
customers reported to us, but which we could not reproduce. After a major
effort, I found it was due to a change to CTime::CTime(const FILETIME&),
which our code did not knowingly call. In fact, it called
CFile::GetFilePath(), which calls CFile::GetStatus(), which calls the CTime
constructor.
It turned out that some network file systems and some CD-ROMs were returning
a file access time of zero. The CTime constructor had been changed to throw
in that circumstance, which was not documented in the MFC 7 release notes.
Our code was not catching it, because the parameterless function
CFile::GetFilePath() did not seem a likely candidate for throwing
E_INVALIDARG. The end result was that our application crashed, and our
customers were not happy.
I carefully documented this bug in a posting to this newsgroup, only to be
immediately informed that it was a known problem! Well, it wasn't fixed in
MFC 7.1, still isn't in the Knowledge Base, and my posting has scrolled off
the end of this NG, so anybody else will also have to find it the hard way.
Is that a reasonable way to treat your customers?
Regards,
Keith MacDonald
"Yan-Hong Huang[MSFT]" <yhhuang@online.microsoft.com> wrote in message
news:XMn7aowMEHA.3780@cpmsftngxa10.phx.gbl...
> Hello Keith,
>
> What Al said is right. Firstly, not all the bug reports could be turned to
> a KB article. For an example, bugs that are still under investigation,
bugs
> that will be fixed soon, bugs that is fixed in the next version...... We
> have a internal counter which indicates how many reports are linked to
this
> problem. If there are some people who met this problem or this problem is
> important, our content team will mark it as a KB article candidate and ask
> engineer to write KB for it.
>
> Writing a KB article is not a easy thing. It contains many steps such as
> tech review, content review...... So it also takes some time unless it is
> quite time critical.
>
> Thanks very much for your interest. :)
>
> Best regards,
> Yanhong Huang
> Microsoft Community Support
>
> Get Secure! ¨C www.microsoft.com/security
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
- Next message: Finn Arildsen: "Re: MFC MDI question"
- Previous message: Das.Peter: "Re: CSocket ERROR ?? (transfer more as 100KB)"
- In reply to: Yan-Hong Huang[MSFT]: "Re: Bug in CFrameWnd::OnInitMenuPopup (MFC 7.10)"
- Next in thread: David Lowndes: "Re: Bug in CFrameWnd::OnInitMenuPopup (MFC 7.10)"
- Reply: David Lowndes: "Re: Bug in CFrameWnd::OnInitMenuPopup (MFC 7.10)"
- Reply: Yan-Hong Huang[MSFT]: "Re: Bug in CFrameWnd::OnInitMenuPopup (MFC 7.10)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|