C / C++ / MFC

Re: Hi, Philip ,look here...

1-Jan-02 3:50

The backward compatibility is exists in all versions of Windows. If you made a program with VS 6.0, you can run it in XP. Not sure about opening 6.0 projects with .NET, but think it can be done.
The second, if you have a program done on C# and compiled with .NET, you can run it on prior Windows versions only if it has a Components Upgrade installed, like Service Pack.
That is what I read, but never tried. You can just make a test and tell us Smile | :)

Philip Patrick
"Two beer or not two beer?" <shakesbeer>
Web-site: www.saintopatrick.com

Hi, Philip ,look here...

1-Jan-02 5:42

"Opening VS6.0 projects with .NET",Is everything here goes all right,you know,I mean the IL of .NET framework would cause problems while opening VS6.0 projects.Or U mean that there is a transformation occurs.The VS6 CODE would be changed into IL compatible style.

Philip Patrick1-Jan-02 6:02

1-Jan-02 6:02

Yep, I meant transformation, like when you are opening a VC5 project from VC6. But as I said, I'm not sure of this aspect at all. I don't have .NET installed and still don't want to do it Smile | :)

It is too fresh Smile | :)

Philip Patrick
"Two beer or not two beer?" <shakesbeer>
Web-site: www.saintopatrick.com

WM_

The_Server1-Jan-02 2:41

The_Server

1-Jan-02 2:41

Hi, All!!!
=======

I saw this in the MSDN

<code>0       </code>through<code>  WM_USER – 1</code>  Messages reserved for use by the system. 
<code>WM_USER </code>through<code>  0x7FFF</code>    Integer messages for use by private window classes. 
<code>WM_APP  </code>through<code>  0xBFFF</code>    Messages available for use by applications. 
<code>0xC000  </code>through<code>  0xFFFF</code>    String messages for use by applications. 
<code>Greater </code>than<code>     0xFFFF</code>    Reserved by the system for future use.

What is the difference between WM_USER and WM_APP ?
and, Why do I need to RegisterWindowMessage ?

Yours truly. . .

Philip Patrick1-Jan-02 2:55

1-Jan-02 2:55

You should read it all Smile | :)

There is a description of what is that. But I copy-pasted it for you here:

Message numbers in the second range (WM_USER through 0x7FFF) can be defined and used by an application to send messages within a private window class. These values cannot be used to define messages that are meaningful throughout an application, because some predefined window classes already define values in this range. For example, predefined control classes such as BUTTON, EDIT, LISTBOX, and COMBOBOX may use these values. Messages in this range should not be sent to other applications unless the applications have been designed to exchange messages and to attach the same meaning to the message numbers.

Message numbers in the third range (0x8000 through 0xBFFF) (WM_APP+) are available for application to use as private messages. Message in this range do not conflict with system messages.

And RegisterWindowMessage is needed to... register a message on single computer so you will be sure that no one will use the same number on that puter

Philip Patrick
"Two beer or not two beer?" <shakesbeer>
Web-site: www.saintopatrick.com

The_Server1-Jan-02 3:17

The_Server

1-Jan-02 3:17

Why do I need to RegisterWindowMessage ???

Q1: Can't I just use WM_APP + ... Intead of the RegisterWindowMessage thing?

Q2: Do I need to RegisterWindowMessage every time I run the app? or just in the 1st time ?

Thanks

Philip Patrick1-Jan-02 3:41

1-Jan-02 3:41

Well...
A1: Yes, you can just use WM_APP+.. but.. imagine that you defined WM_APP+2 message ID and some other running program defined same message. And doesn't matter that YOU are sending your message to particular HWND, but the other prog. is sending using broadcast, that means you will get 2 messages, yours and not. That's why you need RegisterWindowMessage.
But... You have to use Register... only if you jave TWO applications, that communicating with each other. Within ONE application (when you are sending messages to CHILD and not top-level windows) you can simply define the message id.

A2: Yes you have to register your message everytime the application starts. See a simple example below:

UINT WM_MYCUSTOM_MESSAGE = RegisterWindowMessage(_T("WM_MYCUSTOM_MESSAGE"));

Of course instead of WM_MYCUSTOM_MESSAGE you can use any name you can imagine. Once the message is registered, you can get its value in another application with exactly same string of code.

This is the main idea Smile | :)

Philip Patrick
"Two beer or not two beer?" <shakesbeer>
Web-site: www.saintopatrick.com

1-Jan-02 3:25

Forget it man,try MFC...

Philip Patrick1-Jan-02 3:43

1-Jan-02 3:43

Hmm... there is no connection between MFC and Window Messages. You can still use MFC and send messages between windows...

Philip Patrick
"Two beer or not two beer?" <shakesbeer>
Web-site: www.saintopatrick.com

Jörgen Sigvardsson1-Jan-02 4:07

Jörgen Sigvardsson

1-Jan-02 4:07

Philip Patrick wrote:
Hmm... there is no connection between MFC and Window Messages. You can still use MFC and send messages between windows...

Isn't that an oxymoron? Big Grin | :-D

Philip Patrick1-Jan-02 4:22

1-Jan-02 4:22

I understand your sarcasm Smile | :)

But this is a wrong way to use only ONE library. I'm not saying that MFC is bad. Otherwise, it is really good work done on it, and it is very useful. But you always have to use the best from all you know, to combine libraries, techniks, etc. And your code will be the best.
Show me another QUICK way to tell to another application to do something? Or simple to pass an integer Smile | :)

Yes, yes, I know, there are many. File mappings, shared variables, hard disks.... But this one is the simplest Smile | :)

So never say NO to old technologies (BTW, who said that Win API is an old technology?)
Poke tongue | ;-P

Philip Patrick
"Two beer or not two beer?" <shakesbeer>
Web-site: www.saintopatrick.com

Hi, Philip Look Here...

1-Jan-02 6:11

We will never be in the same step of Micro$oft technology.And one day U would suddenly find that a simplest but most efficiently method provided by M$.They ALWAYS do this with a reasonable pretence,just for M$ own benefit but really for convenience of developers.
U know there are two major team in CHINA:RAD and NON-RAD.They fight for an appellation that "Which is the best".I do think it is fastidium to discuss such an issue.
Different method fits for Different Area.WM_ or MFC or WM_+MFC...... Laugh | :laugh:

Totally agree... :)

Philip Patrick1-Jan-02 6:16

Custom User Interfaces in VC++

1-Jan-02 6:16

Well, you are right Smile | :)

Have nothing to add to your words Smile | :)

Philip Patrick
"Two beer or not two beer?" <shakesbeer>
Web-site: www.saintopatrick.com

31-Dec-01 23:56

I started learning VC++ in 1999 and followed the microsoft curriculum for certifications. At that time I was a good C++ programmer on DOS and then I started using C++ for windows utilizing MFC platform. I didn't waste my time on writing Windows Programs using WinMain approach and I like MFC very much.

I gave the certification papers on VC++ in the year 2000 and since then I've been programming in VC++ regularly.

Now the problem with me is that I don't know the art of creating custom controls and Custom User Interfaces in VC++/MFC. We can see very good source code at codeproject regularly on the concerned topics. So my question to all of you is that "What is the "step-by-step" approach of learning how to create custom userinterfaces in VC++/MFC" ??

Plz help me in this regard. Suggest me good books or resources etc... Confused | :confused:

Jahnn Lee

Re: Custom User Interfaces in VC++

Christian Graus1-Jan-02 0:42

Christian Graus

1-Jan-02 0:42

If you're not sure how MFC does things MFC Internals is a good book, so is 'The MFC Answer Book'. But overall, you've probably already answered the question, this site is full of such custom controls, your best bet is really to look for well written articles that explan how some of those were created, download the source and start changing it to see what happens.

It probably wouldn't hurt to learn some Win32 so you get a better appreciation of what MFC is doing for you, but the MFC Internals book will give you that also.

Christian

After all, there's nothing wrong with an elite as long as I'm allowed to be part of it!! - Mike Burston Oct 23, 2001

Sonork ID 100.10002:MeanManOzI live in Bob's HungOut now

Microsoft Speech API (SAPI) question

31-Dec-01 22:28

Hi,
Does anyone know how to add spanish\french\italian or any other language support to the Microsoft's Speech API engine?
thanks

Re: Microsoft Speech API (SAPI) question

Nnamdi Onyeyiri1-Jan-02 3:09

Nnamdi Onyeyiri

1-Jan-02 3:09

At the sapi website download page, it gives you the opertunity to download language packs.

==================================================
The Eclypse

Re: Microsoft Speech API (SAPI) question

1-Jan-02 3:28

FORGET IT MAN,impossible!!

CImage to HBITMAP

Liorsh31-Dec-01 19:44

Liorsh

31-Dec-01 19:44

Hey,
Anyone knows how to convert a CImage to an HBITMAP ?

Thanks.

Christian Graus1-Jan-02 0:47

Christian Graus

1-Jan-02 0:47

What is a CImage ? If it's a bitmap of some sort, unless it's a DIB, it surely has operator HBITMAP defined ?

Christian

After all, there's nothing wrong with an elite as long as I'm allowed to be part of it!! - Mike Burston Oct 23, 2001

Sonork ID 100.10002:MeanManOzI live in Bob's HungOut now

Liorsh1-Jan-02 0:50

Liorsh

1-Jan-02 0:50

CImage is available when using Microsoft Forms Image 2.0 control.
and it doesn't have HBITMAP operator.
I think it has something to do with IPictureDisp and IPicture.
Hope it helps.

Christian Graus1-Jan-02 1:01

Christian Graus

1-Jan-02 1:01

It's not mentioned in the latest MSDN. If it's a COM object, it may support an IStream, in which case you can get it via a GDI+ Image object. Beyond that I do not know.

Christian

After all, there's nothing wrong with an elite as long as I'm allowed to be part of it!! - Mike Burston Oct 23, 2001

Sonork ID 100.10002:MeanManOzI live in Bob's HungOut now

Philip Patrick1-Jan-02 6:10