|
Well, you mostly only repeated what you sent in your first post so that doesn't bring us any further...anyways, i supose you access members thorough that dCreateAgent->dFollowAgent pointer, which points at some random memoy location or NULL if you initialized it, until you do dCreateAgent->dFollowAgent= new FollowAgent(...); , from which point it will point at a valid object and you can use it. Does this help?
> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> Sometimes you just have to hate coding to do it well. <
|
|
|
|
|
I'm installing that product on my vista SP1 with VS2008 SP1.
There is Missing Pre-requisite window appear.
Miscrosoft Platform SDK not found
Microsoft Platform SDK build 1830 or higher is required
to install Intel(R) C++ compiler for applications
running on IA-32, version 11.0.061.
Select one of the following options.
- Do no install Intel(R) C++ Compiler
- Continue installing and use Microsoft Platform SDK folder entered below
c:\program files\Microsoft SDKs\Windows\v6.0\
What does it mean?
Why platform SDK is needed for Intel Compiler?
Intel Compiler will be installed into different directory than SDK?
Чесноков
|
|
|
|
|
I would install a more recent (isn't yours the one that came with Visual Studio 6.0 ?) Windows SDK (it is available for free from Microsoft ) before installing the compiler.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
The platform SDK contains the runtimes required to link object code on Windows systems into executables. Intel obviously designed their compiler to be compatible with the Windows libraries rather than try to write their own. You can get the latest SDK from Microsoft; see here[^] for more information.
It's time for a new signature.
|
|
|
|
|
Currenty Windows SDK is for 7 and .NET Framework 3.5.
I read they will ship a newer SDK after Visual Studio 2010, to support .NET 4.0 with Windows 7.
|
|
|
|
|
Sorry, but what has this to do with the my last message?
It's time for a new signature.
|
|
|
|
|
Please provide me step by step how to create a number of dialogs in a Console application
I also need to respond to the events in the dialogs as in MFC.
|
|
|
|
|
I don't get it. If you need dialogs, why don't you create a win32 application instead ?
|
|
|
|
|
I already have a console application in which I want to create my dialog. If I tried to create a dialog resource and then add a class to the dialog through class wizard as in MFC it gives me errors
due to #define "StdAfx.H" which is included in the new dialog class created through wizard. And also its not able to recogonize the MFC classes.
|
|
|
|
|
I believe he wants to mimic the logic of old DOS GUI.
|
|
|
|
|
Just as you normally would. What's the specific problem?
Steve
|
|
|
|
|
If I tried to create a dialog resource and then add a class to the dialog through class wizard as in MFC it gives me errors due to #define "StdAfx.H" which is included in the new dialog class created through wizard. And also its not able to recogonize the MFC classes and gives errors.
|
|
|
|
|
|
Which is the opposite of what the OP wanted, yes?
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Man who follows car will be exhausted." - Confucius
|
|
|
|
|
|
|
I don't think Visual Studio is set up to do this. If you want to use MFC then you should either create an MFC Windows app that contains the dialogs, or an MFC dialog app with tabs or some similar mechanism. If you want to add dialogs to a console app then you will need to do it manually, by adding all the required Win32/MFC framework components.
It's time for a new signature.
|
|
|
|
|
In a console based application, we cant include the dialog which is created by MFC or SDK. If u still need to use the dialog in console application, convert the your console application to win32 application and try to use MFC dialogs.
---Parthi
|
|
|
|
|
Parthiban wrote: In a console based application, we cant include the dialog which is created by MFC or SDK.
Wrong. You could have a console based application support MFC by including the right header files.
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
Sounds like you didn't create the console application with the MFC app wizard, so the pre-compiled header settings are not set correctly. You also technically need to initialize MFC in main, though this isn't actually required for some parts of MFC (which I used to worry about in the days of very limited memory, but haven't for years.)
|
|
|
|
|
How can i get the column count of list view ......i m doing this in win 32
|
|
|
|
|
It would be a question for the list header :
{
long lCols = 0;
if (hwndList) {
HWND hwndHeader = ListView_GetHeader(hwndList);
if (hwndHeader) {
long lRes = SendMessage(hwndHeader, HDM_GETITEMCOUNT, 0, 0);
if (-1 != lRes) {
lCols = lRes;
}
}
}
}
virtual void BeHappy() = 0;
|
|
|
|
|
thanks Eugen
i m using this macro's
hHeader = ListView_GetHeader(hListview);
g_ncColumns = Header_GetItemCount(hHeader);
|
|
|
|
|
Not quite sure where I should ask this...I mean, this site really needs a Windows programming section, doesn't it?
Anyways, here goes. I have this DLL trying to call mciSendString (command passed as a parameter). The call works fine in an EXE, but it refuses to do anything on a DLL (I'm testing with "set cdaudio door open"). The function gets called but it hangs. Forever.
Stack, if it helps:
ntkrnlpa.exe!ExAllocatePoolWithTag+0x8ab
ntkrnlpa.exe!MmIsDriverVerifying+0xa08
ntkrnlpa.exe!MmIsDriverVerifying+0x12ea
ntkrnlpa.exe!PoShutdownBugCheck+0x32ce
ntkrnlpa.exe!KeSynchronizeExecution+0x10c
ntdll.dll!KiFastSystemCallRet
!WaitForSingleObject+0x12
!waveOutWrite+0x50c
!mci32Message+0x526
!mciSendCommandW+0x10b
!mciSendCommandW+0x48e
!mciSendStringW+0x31
!mciSendStringA+0x87
Thanks!
|
|
|
|
|
It seems to be a "deadlock"...
(for example, a recursion on the code block,
what is protected by a critical section...
...like: mciSendCommand(..)->mciSendString(..)->mciSendCommand(..))
virtual void BeHappy() = 0;
|
|
|
|