| Author |
 Topic  |
|
|
BigHands
Senior Member
28 Posts |
|
|
feline
Whole Tomato Software
United Kingdom
18939 Posts |
 Posted - May 06 2008 : 10:24:52 AM
|
I see the problem, the screen shot is very clear, thank you for that.
Assume I know nothing about Direct3D, what header file do I need to include?
What class do I need an instance of?
Am I going to need to install a DirectX SDK to get access to the header file to test this? |
zen is the art of being at one with the two'ness |
 |
|
|
BigHands
Senior Member
28 Posts |
Posted - May 06 2008 : 1:55:41 PM
|
quote:
Originally posted by feline
Assume I know nothing about Direct3D, what header file do I need to include?
What class do I need an instance of?
Am I going to need to install a DirectX SDK to get access to the header file to test this?
You need to include d3d9.h. Here's a bit of code to replicate the parsing issue:
#include <d3d9.h>
int main()
{
IDirect3DDevice9* pDevice;
// And then try typing out any one of the following
// and you'll see the problem tooltip:
pDevice->Clear(
pDevice->CreateVertexBuffer(
pDevice->CreateVertexShader(
// etc.
return 0;
}
I can send you the latest DirectX9 header files if you need them (otherwise, I think the entire SDK is ~450MB). |
Edited by - BigHands on May 06 2008 1:56:00 PM |
|
|
|
feline
Whole Tomato Software
United Kingdom
18939 Posts |
Posted - May 06 2008 : 2:27:09 PM
|
I have the DirectX SDK somewhere, but if you could just send me the single header file I need for the test that would be most useful, thank you. It saves me installing the SDK somewhere just to find the single file I need.
Please send me the files via the form:
http://www.wholetomato.com/support/contact.asp
including this thread ID or URL in the description, so we can match it up. |
zen is the art of being at one with the two'ness |
|
|
|
feline
Whole Tomato Software
United Kingdom
18939 Posts |
Posted - May 06 2008 : 3:39:42 PM
|
I have the files, thank you for these. The problem is happening because parameter highlighting is getting confused with the STDMETHOD macro:
case=3727 |
zen is the art of being at one with the two'ness |
|
|
|
BigHands
Senior Member
28 Posts |
Posted - May 06 2008 : 4:35:33 PM
|
quote:
Originally posted by feline
I have the files, thank you for these. The problem is happening because parameter highlighting is getting confused with the STDMETHOD macro:
case=3727
Yikes! That's a pretty old case number. :( Are there any workarounds you can think of? Is this an issue that will be tough to fix?
|
|
|
|
feline
Whole Tomato Software
United Kingdom
18939 Posts |
Posted - May 06 2008 : 5:09:48 PM
|
I have increased the priority on this bug report for you, hopefully that will help.
I don't know of any work arounds, but you could try editing VA's "StdAfx.h" file as explained in this FAQ entry:
http://docs.wholetomato.com?W302
and add the entry:
#define STDMETHOD(x) x
at the bottom. This file is used to help VA's parser with difficult code, and can be used to work around odd effects. After modifying this file you need to rebuild the VA symbol database for the changes to take effect:
VA Options -> Performance -> General -> Rebuild symbol databases
I honestly do not know if this will help or not, but it might. |
zen is the art of being at one with the two'ness |
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Sep 13 2008 : 01:11:50 AM
|
| case=3727 is fixed in build 1649 |
|
|
| |
Topic |
|
Direct3D Parsing
