C / C++ / MFC

session description protocol

6-Dec-12 22:11

See this article[^].

One of these days I'm going to think of a really clever signature.

mani2516195-Dec-12 18:33

mani251619

5-Dec-12 18:33

I am working on customization of multimedia communication using SDP. Plz could you provide me with SDP code

Re: session description protocol

Richard MacCutchan5-Dec-12 21:26

Re: session description protocol

5-Dec-12 21:26

mani251619 wrote:
Plz could you provide me with SDP code

Sorry this site does not provide code to order.

One of these days I'm going to think of a really clever signature.

David Crow6-Dec-12 2:50

David Crow

6-Dec-12 2:50

mani251619 wrote:
Plz could you provide me with SDP code

Did you see #2 here?

"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

"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous

Re: session description protocol

jeron16-Dec-12 4:03

jeron1

6-Dec-12 4:03

Perhaps here[^] or here[^].

error C1083: Cannot open type library file "libid:00.......

ForNow5-Dec-12 12:01

ForNow

5-Dec-12 12:01

Hi,

I am getting a compiler error on #import statment defining the library type for excel 2003

I am using Visual C++ 6.0 The library type is in excel.exe

Which in my case resides in C:\Program Files\Microsoft office\office11

Where would I specify this directory in Visual C++ 6.0

Re: error C1083: Cannot open type library file "libid:00.......

Richard MacCutchan5-Dec-12 12:15

Re: error C1083: Cannot open type library file "libid:00.......

5-Dec-12 12:15

You already posted this question in the COM forum; please do not crosspost.

One of these days I'm going to think of a really clever signature.

ForNow5-Dec-12 12:23

ForNow

5-Dec-12 12:23

Thought nobody visited the other forum sorry

Re: error C1083: Cannot open type library file "libid:00.......

ThatsAlok6-Dec-12 3:33

ThatsAlok

6-Dec-12 3:33

ForNow wrote:
Where would I specify this directory in Visual C++ 6.0

Are you working in MFC, if yes then you can use the class wizard to generate the class based from OCX,TLB or DLL

"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
Never mind - my own stupidity is the source of every "problem" - Mixture

cheers,
Alok Gupta
VC Forum Q&A :- I/IV
Support CRY- Child Relief and You

Re: error C1083: Cannot open type library file "libid:00.......

David Crow6-Dec-12 5:10

David Crow

6-Dec-12 5:10

ForNow wrote:

I am getting a compiler error...

Which is what?

System message processing in MFC - basic question.

Vaclav_5-Dec-12 5:23

Re: System message processing in MFC - basic question.

5-Dec-12 5:23

<pre lang="text">
What is the basic difference in processing system messages in MFC?
Should I use message map or WindowProc?
In my included sample the WindowProc get executed first ( as expected ) , but I really do not do any message processing in this case. So my secondary question would be - what is considered by OS as processed message?
</pre>

BEGIN_MESSAGE_MAP(C_Setup, CDialog)
//{{AFX_MSG_MAP(C_Setup)
ON_MESSAGE(WM_DEVICECHANGE, OnMyDeviceChange)
//}}AFX_MSG_MAP
END_MESSAGE_MAP()
LRESULT C_Setup::WindowProc(UINT message, WPARAM wParam, LPARAM lParam)
{
//AfxMessageBox("LRESULT C_Setup::WindowProc(UINT message, WPARAM wParam, LPARAM lParam)");

if(message == WM_DEVICECHANGE)
{
AfxMessageBox("message == WM_DEVICECHANGE");
} // TODO: Add your specialized code here and/or call the base class

return CDialog::WindowProc(message, wParam, lParam);
}

Appreciate your input.
Thanks
Vaclav

Richard MacCutchan5-Dec-12 5:33

Re: System message processing in MFC - basic question.

5-Dec-12 5:33

Why are you using a MFC message map and a Win32 message procedure? You should only be using message maps in MFC programs.

One of these days I'm going to think of a really clever signature.

Vaclav_5-Dec-12 7:37

Re: System message processing in MFC - basic question.

5-Dec-12 7:37

OK, so let me rephrase it - when would one use WindowProc in MFC?

Chris Meech5-Dec-12 9:11

Chris Meech

5-Dec-12 9:11

Less than rarely, closer to never. Even with all the knocks on MFC message maps, once you are developing with MFC, I can not think of a reason for not using the maps. Smile | :)

Chris Meech
I am Canadian. [heard in a local bar]

In theory there is no difference between theory and practice. In practice there is. [Yogi Berra]

posting about Crystal Reports here is like discussing gay marriage on a catholic church’s website.[Nishant Sivakumar]

Re: System message processing in MFC - basic question.

Richard MacCutchan5-Dec-12 9:22

Re: System message processing in MFC - basic question.

5-Dec-12 9:22

Never. MFC has an inbuilt message pump and MessageProc() handler which distributes the messages according to your MESSAGE_MAP entries. If you add your own MessageProc() then you break the connection between those entries and your message handlers.

One of these days I'm going to think of a really clever signature.

Albert Holguin5-Dec-12 10:26

Albert Holguin

5-Dec-12 10:26

I would agree with NEVER... use message maps in MFC. If you find it doesn't do something specific that you needs, that's when you go around the framework, other than that... it's best to try to use the framework that's there.

Re: System message processing in MFC - basic question.

Albert Holguin5-Dec-12 10:29

Albert Holguin

5-Dec-12 10:29

Messages use WindowProcs, but MFC handles that for you. There's really very few cases where you'd have to go around what MFC already does. Only reason to code your own WindowProcs would really be if you're doing native Win32 coding.

Dbt.h - symbol not defined?

Vaclav_5-Dec-12 5:07

Re: Dbt.h - symbol not defined?

5-Dec-12 5:07

These lines are OK

if ( DBT_DEVICEARRIVAL == wParam || DBT_DEVICEREMOVECOMPLETE == wParam ) {
PDEV_BROADCAST_HDR pHdr = (PDEV_BROADCAST_HDR)lParam;

But here the compiler complains about undefined symbol.

PDEV_BROADCAST_DEVICEINTERFACE pDevInf;

All of these are defined in Dbt.h and suppose to work in XP.

<b>So, what else did I missed?</b>
Any help will be appreciated.
Cheers
Vaclav

Richard MacCutchan5-Dec-12 5:30

Re: Dbt.h - symbol not defined?

5-Dec-12 5:30

1. Please put your code inside <pre> tags.
2. Show the exact code and the compiler error that you get.

One of these days I'm going to think of a really clever signature.

Jochen Arndt5-Dec-12 6:06

Jochen Arndt

5-Dec-12 6:06

If you open Dbt.h and lookup the definition, you will see that it is enclosed by this condition:

#if(WINVER >= 0x040A)

So check your WINVER definition (usually in stdafx.h). For XP and later it should be 0x0501.

SOLVED Dbt.h - symbol not defined?

Vaclav_5-Dec-12 7:33

5-Dec-12 7:33

Thanks,
my Windows OS is XP SP3 ( 5.1) and my VC 6.0 has references only to WINVER 4.0!
I hope I can fix that without screwing things up too much.
Thanks again.

I see that WINVER is set in Windows.h by default - by checking if it is not defined -independent of OS version. I guess my expectations from OS and compiler are little to high.

-- modified 5-Dec-12 15:11pm.

Jochen Arndt5-Dec-12 21:46

Jochen Arndt

5-Dec-12 21:46

Because WINVER is used in Windows.h and many other header files, it is set to the smallest supported value in Windows.h if not already defined.

It is a definition that decides which API functions and structures can be used. Which compiler is used does not care. But to use features introduced with newer Windows versions, you must use newer include files from a newer Windows SDK.

Vaclav_6-Dec-12 3:28

6-Dec-12 3:28

Jochen,
thanks again for your input.
I was just puzzled that the WINVER is defined in Windows.h only if it is not already defined elsewhere. But there is nothing wrong with that and it was a good learning experience for me. I think the main "problem" is that I get involved with coding and assume that the supporting headers are there or are OK.
With all the new IDE's I wish the people who post code here would point out which OS / SP / SDK is required for the code to even compile.
But than one would not learn anything from "mistakes", tough call.
Vaclav

Jochen Arndt6-Dec-12 3:50

Jochen Arndt

6-Dec-12 3:50

You are always welcome.

The problem is that you are using an ancient development environment. I have not used VC 6 since many years. At work I'm still using the also outdated Visual Studio 2003 because we need to support Win98 and 2K for some machine control systems.

In 2012 there is no more support for Windows 9x, NT4, and 2000. So there is no need to use old dev software and most here assume that you are using a newer version (VS 2008 or later). In fact you should use a newer version when writing programs for actual Windows versions. Especially VC 6 is too old. With VS 2003 and updated SDKs, I'm at least able to write code for Windows 7.

It is common practice that the actually oldest supported Windows versions is the min. requirement. With your VC 6 version that was Windows 95. For Microsoft and the people here it is actually Windows XP. When reading articles here, just have a look at the publishing date to guess what is supported. Many articles also have a note about the requirements.

I know now that you are using VC 6. For future questions, it may be helpful to add a note that you are using VC 6 so that others are prepared.

Vaclav_7-Dec-12 7:26