|
I am NOT using stdafx...i am bound to rely strictly on a void project/simplest c enviroment - for now at least.
I included:
#include "DShow.h"
#include "WinBase.h"
no redefinition errors showing up with this order;
DShow includes uuids, windows, ole[s] and a lot of 'standard' requested libs...all as <xxx> namespaces 
I am starting to fear having to use all this stuff in a cpp env...or I shall ask my prof for vc2005 
Nonetheless, put sdk paths ahead of others could do some good, thanks!
--edit---
I just found a ICaptureGraphBuilder2 def in an 'axextend.idl' file in sdk\Include! But I cannot use it as it is...
what are idl files?
thanks Mark and excuse me for pseudo-english 
|
|
|
|
|
what about
#ifndef WINVER // Allow use of features specific to Windows 95 and Windows NT 4 or later.
#define WINVER 0x0400 // Change this to the appropriate value to target Windows 98 and Windows 2000 or later.
#endif
#ifndef _WIN32_WINNT // Allow use of features specific to Windows NT 4 or later.
#define _WIN32_WINNT 0x0400 // Change this to the appropriate value to target Windows 98 and Windows 2000 or later.
#endif
#ifndef _WIN32_WINDOWS // Allow use of features specific to Windows 98 or later.
#define _WIN32_WINDOWS 0x0410 // Change this to the appropriate value to target Windows Me or later.
#endif
#ifndef _WIN32_IE // Allow use of features specific to IE 4.0 or later.
#define _WIN32_IE 0x0400 // Change this to the appropriate value to target IE 5.0 or later.
#endif
#include <DShow.h>
(winbase.h is pulled in through dshow.h)
|
|
|
|
|
sorry copy/pasted...you can use it simpler like this...
#define WINVER 0x0400 // Change this to the appropriate value to target Windows 98 and Windows 2000 or later.
#define _WIN32_WINNT 0x0400 // Change this to the appropriate value to target Windows 98 and Windows 2000 or later.
#define _WIN32_WINDOWS 0x0410 // Change this to the appropriate value to target Windows Me or later.
#define _WIN32_IE 0x0400 // Change this to the appropriate value to target IE 5.0 or later.
#include <DShow.h>
|
|
|
|
|
|
Talemin wrote: Well, i'd just found a mini-very-tiny-little line in sdk page so that new (2003->) sdks don't support visual studio 6.0 more. So much for microsoft compatibility
Bummer!!
You'll be happy you upgraded though. I'm still on VC++ .NET 2003, I admit, but it's far better.
Best of luck!
Mark
|
|
|
|
|
OK. VS2005 accepts new classes. I still get the 'funny' errors
(a is not a member of b, but auto-complete func prompts a in &b-> members list...) but they seem only a problem with old vs6 project file conversion.
I hope 
Tip
you all will know this already, but for completeness'sake:
VS2005 provides no more ddraw libraries, which dshow still requires; you must install directx sdk too.
I like this new way of learning TaiChi...
|
|
|
|
|
Hello everyone!
I have this:
CEdit *m_em_errorMsg = (CEdit *) GetDlgItem(IDC_ERROR_MSG);
Is that a correct form of initialization? I don't want to use Create() because I'm using the dialog designer...
That code's giving me some errors, and the debugger's Watch 1 window has a lot of class (CEdit/CWnd) members with "expression cannot be evaluated" errors on them, so that's why I'm assuming the init is the problem... Is it wrong? Thanks! 
Windows Calculator told me I will die at 28. 
|
|
|
|
|
Lord Kixdemp wrote: Is that a correct form of initialization?
Yes, for initializing m_em_errorMsg.
Lord Kixdemp wrote: I don't want to use Create()...
Why would you need to? You should already have a control with an id of IDC_ERROR_MSG.
Lord Kixdemp wrote: That code's giving me some errors...
And those errors would be what?
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
|
You can declare a variable for your editbox and use of it
|
|
|
|
|
That be what I'm doing 
Windows Calculator told me I will die at 28.
|
|
|
|
|
if you declare a variable for your editbox that you have on forum is better than use
<br />
CEdit *m_em_errorMsg = (CEdit *) GetDlgItem(IDC_ERROR_MSG);
|
|
|
|
|
Dong-Jun Kim wrote: Is it normal behavior of modeless dialog boxes?
"Normal" is whatever you make of it.
Dong-Jun Kim wrote: I just want to close the box when I click close, little x button on top right, button.
Then you simply need to call DestroyWindow() in those situations. Be careful that you are not inadvertently calling EndDialog().
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
I have a worker thread that needs to wait a certain amount of miliseconds before resuming..
I would just got the for(i=0; i<10000000000; i++) route, but i'm afaid it will eat up the CPU. I'm trying to stay out of a loop but stay in the worker thread.
I need my main thread to be very alert and time accurate while this worker thread is waiting.
I've looked at all the timer functions.. can't seem to find the one to do the trick..
any ideas.. ?
Workthread()
{
//do some processing
//wait
//do more processing
//return
}
|
|
|
|
|
Sleep[^]
Although why someone is writing multi-threaded code prior to learning the threading API's is... well .... pretty crazy.
led mike
|
|
|
|
|
On Windows, try Sleep(milliseconds)
Eats NO CPU
|
|
|
|
|
HA! Beat you by the click of an eye.
led mike
|
|
|
|
|
|
duh... didn't have the time.h header in... my bad.. thanks guys
|
|
|
|
|
aquawicket wrote: duh... didn't have the time.h header in... my bad.. thanks guys
try more efficient WaitForSingleObject with retrun value WAIT_TIMEOUT
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
Support CRY- Child Relief And You
|
|
|
|
|
Hello.
I have added a picture control to my dialog application resource file.
I dont know how to access it at run time.
I thought you would need a pointer, in the same way you access a Edit control:
CEdit *p = GetDlgItem(IDC_EDT);
p->whatever,
etc.
So I need a pointer to the control I assume in order to send an image to it.
Can anyone help.
Jerry
|
|
|
|
|
Try a pointer to a CStatic object
Mark
|
|
|
|
|
|
That is the type of control placed on the dialog.
You can set a bitmap into it in the designer or at runtime with CStatic::SetBitmap()
|
|
|
|
|
By default, the control has an id of IDC_STATIC. Change that to something else. Then use ClassWizard (Ctrl+W) to associate a CStatic object to that control. Then you can call the SetBitmap() method.
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Rose | [Rose]](https://www.codeproject.com/script/Forums/Images/rose.gif)
Thanks!