Re: COleDateTime::GetCurrentTime() problem
- From: David Lowndes <DavidL@xxxxxxxxxxxxxxx>
- Date: Mon, 30 Oct 2006 09:51:47 +0000
You are right, it has to do with altering floating point processor settings.
Using the flag D3DCREATE_FPU_PRESERVE when creating the Direct3D device
solves the problem.
Searching the newsgroups it appears that others have also suffered
from this problem :(
If you've not done so, I think it'd be worthwhile submitting a bug
report on it (and the solution) to ensure MS are aware of the problem
- and so they can come up with some solution in the future, even if
that's only documenting the fact that something as innocuous as
COleDateTime::GetCurrentTime() can fail because of the floating point
settings.
In the absence of an obvious bug report by the OP on the connect site,
I've created this one:
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=233345
Anyone who's interested can vote/validate it.
Dave
.
- References:
- COleDateTime::GetCurrentTime() problem
- From: Alexander Mair
- Re: COleDateTime::GetCurrentTime() problem
- From: David Lowndes
- Re: COleDateTime::GetCurrentTime() problem
- From: Alexander Mair
- Re: COleDateTime::GetCurrentTime() problem
- From: David Lowndes
- Re: COleDateTime::GetCurrentTime() problem
- From: Alexander Mair
- Re: COleDateTime::GetCurrentTime() problem
- From: Alexander Mair
- Re: COleDateTime::GetCurrentTime() problem
- From: David Lowndes
- Re: COleDateTime::GetCurrentTime() problem
- From: Alexander Mair
- Re: COleDateTime::GetCurrentTime() problem
- From: David Lowndes
- COleDateTime::GetCurrentTime() problem
- Prev by Date: Re: SetUnhandledExceptionFilter
- Next by Date: Re: SetUnhandledExceptionFilter
- Previous by thread: Re: COleDateTime::GetCurrentTime() problem
- Next by thread: How to read the string from RichEditCtrl? But in the RichEditCtrl, may be have Emoticons...
- Index(es):
Relevant Pages
|