C / C++ / MFC

6-Dec-05 12:47

That sounds weird. I know I get the message in my apps, and I don't do anything special.

--
Pictures[^] from my Japan trip.

FindWindow question

skinnyreptile1686-Dec-05 11:50

skinnyreptile168

6-Dec-05 11:50

I use FindWindow function in windows appl_2 to get the handle of windows appl_1. However lpWindowName cannot be use since my windows appl_1 contains version number which will change everytime I recomplie it. I used the class object name inherit "theapp" which does not work. Can anyone please tell me how to get the lpClassName from appl_1 please? Thank you.

Blake Miller6-Dec-05 12:20

Blake Miller

6-Dec-05 12:20

The more relevant questions is WHY do you need to do this?
Because if you need HWND_1 from APPL_2, why not write HWND_1 into a memory mapped file that can be directly read from APPL_2 and then not EVER have to worry about it again. Avoiding the CHEESY FindWindow function altogether. Nuff said Cool | :cool:

I AM going to have to write an article titled FindWindow - JUST SAY NO!

Jörgen Sigvardsson6-Dec-05 12:44

6-Dec-05 12:44

Why not let appl_2 probe for appl_1 with window messages? Use RegisterWindowMessage() to register a unique window message which only your two apps know. A unique message name could be created using Guidgen.exe which comes with visual studio.

// common.h
#define YOUR_MAGIC_COOKIE 0xdeadbeef
#define UNIQUE_NAME "AUniqueName"

// appl_2
#include "common.h"
 
UINT nMessage = RegisterWindowMessage(UNIQUE_NAME);
foreach hWnd in TopLevelWindows {
    if(YOUR_MAGIC_COOKIE == SendMessage(hWnd, nMessage, 0, 0)) {
        // You found your window
       DoSomethingWithYourWindow(hWnd);
    }
}

// appl_1
#include "common.h"
 
UINT nMessage = RegisterWindowMessage(UNIQUE_NAME);
switch(msg.message) {
   ...
   case nMessage:
       return YOUR_MAGIC_COOKIE;
}

Please translate appl_1's message handling into your preferred toolkit's way of handling messages.

--
Pictures[^] from my Japan trip.

-- modified at 18:46 Tuesday 6th December, 2005

skinnyreptile1686-Dec-05 13:00

skinnyreptile168

6-Dec-05 13:00

Either of your methods is better than FindWindow(). Using memory mapped file looks clean but I am not too familiar with it. RegisterWindowMessage() seems easy enough for me to pick up quick.
Thanks a million, guys!

Blake Miller6-Dec-05 15:56

Blake Miller

6-Dec-05 15:56

Bzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzt....

foreach hWnd in TopLevelWindows {    <br />
  if(YOUR_MAGIC_COOKIE == SendMessage(hWnd, nMessage, 0, 0)) {

This will hang your application if the top-level window you sent a message to is not responding.

Better use the other technique, or else at LEAST use SendMessageTimeout.

Jörgen Sigvardsson7-Dec-05 7:06

7-Dec-05 7:06

You're right!

--
Pictures[^] from my Japan trip.

Jörgen Sigvardsson7-Dec-05 7:09

7-Dec-05 7:09

Another solution is to use HWND_BROADCAST and register another response message. Then collect the result in a/the message loop.

--
Pictures[^] from my Japan trip.

Re: CImageList question ...

ThatsAlok6-Dec-05 19:05

ThatsAlok

6-Dec-05 19:05

vitowong wrote:
Either of your methods is better than FindWindow(). Using memory mapped file looks clean but I am not too familiar with it.

Have a look at this thread before using FindWindow api!-
PROS AND CONS of FINDWINDOW[^]

"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

CImageList question ...

Maximilien6-Dec-05 10:32

Maximilien

6-Dec-05 10:32

( must be a dumb day for me ... )

I have a CImageList that I use in a Tree Control; the bitmap contains non-mask images all bundled in one big bitmap; I create the imagelist like :

/// il is a class member.
il.Create( IDB_TREE_IMAGES, 16, 0, RGB(0,128,128) );  // the RGB is the color that I mark as tranparent in the bitmap.
il.SetBkColor( GetSysColor(COLOR_WINDOW) );
//...
SetImageList( &il, TVSIL_NORMAL ); // for the tree control.

This works well, all images are drawn transparently.

I want to split the big bitmap into individual smaller bitmaps, why ? because it's easier to add and remove images from the image list by adding and removing individual images instead of having to remove and resize the big image.

so, I do this :

m_ImageList.Create( 16, 14,ILC_COLOR4,30, 10 );//  RGB(0,128,128) );
CBitmap bm;
bm.LoadBitmap(ITB_TREE_COORDINATE);
COORDINATE_IMAGE_INDEX = m_ImageList.Add( &bm, RGB(0,128,128) );
bm.DeleteObject();
...
/// I do an Add for each individual bitmap.
m_ImageList.SetBkColor( GetSysColor(COLOR_WINDOW) );
//...
SetImageList( &m_ImageList, TVSIL_NORMAL );

but in this second case, the images are not drawn transparently; the bitmaps are 256 colors palettized bitmaps.

Any ideas ?

in my example that works, there is not specification for the type of images ( ILC_COLOR, ... ) and for my second example, I need to specify one, is there a default type I can/should use ?

Thanks.

Max.

Maximilien Lincourt
Your Head A Splode - Strong Bad

Jörgen Sigvardsson6-Dec-05 10:47

How do I capture "Enter" Key in an Edit Control?

6-Dec-05 10:47

You're supposed to use ILC_MASK in the Create() call together with your color format (e.g. ILC_COLOR8).

--

Jethro636-Dec-05 7:57

Re: How do I capture &amp;amp;lt;RETURN&amp;amp;gt; in an Edit Control?

6-Dec-05 7:57

Hi:

I am trying to do what I thought would be a simple thing. I have a dialog which contains a variety of controls. One of my controls is an edit box. When a user is entering data through this control, I would like the user to be able to press the "ENTER" key to accept what has been entered.

I understand that dialogs will execute their DEFAULT button when "ENTER" is pressed but I THOUGHT that if I derived a new CMyEdit from CEdit and found the right function to override, I would be able to intercept the "ENTER" key and have it process the input instead. I must find a way to do this because I have users that feel that pressing enter after making an entry into a control like this is a natural thing to do and it is natural to expect that the input should be processed at that point. Frankly, I somewhat agree...

Is it my imagination or is this impossible? I have overridden every CEdit virtual function that I can find and NONE of them are called when I press "ENTER". Some of them are called if I press other keys, but not "ENTER".

What gives? What am I doing wrong?

Thanks in advance for your help!
Mark

-- modified at 14:33 Tuesday 6th December, 2005

David Crow6-Dec-05 8:18

David Crow

6-Dec-05 8:18

Use the ES_WANTRETURN style.

"Take only what you need and leave the land as you found it." - Native American Proverb

Re: How do I capture "Enter" key in an Edit Control?

Jethro636-Dec-05 8:33

Re: How do I capture &quot;Enter&quot; key in an Edit Control?

6-Dec-05 8:33

Hi David. Thanks for your response.

I did try this already. It made no difference. As it turns out, the VS help item that discusses "Want Return" says:

"This style has no effect on a single-line edit-box control."

I am using a single line edit box so I guess that explains it. I really don't want to use a multiline box so I am still stuck with this problem.

Thanks,
Mark

David Crow6-Dec-05 8:38

David Crow

6-Dec-05 8:38

In the context of a single-line edit control, the enter key makes no sense. It should do the default behavior, which is to dismiss the dialog.

"Take only what you need and leave the land as you found it." - Native American Proverb

Jethro636-Dec-05 8:47

6-Dec-05 8:47

Well, I guess there is an "old school" that feels that pressing ENTER means "Take this input and process it". Some feel that it should then move the focus to the next item in the TAB order. It makes some sense to me although I would like nothing more at this point then to tell my users that this is the "new school" and "get over it". Unfortunately, I don't think they are going to drop this issue. I wish I could find a way...

Thanks again,
Mark

Nish Nishant6-Dec-05 9:02

Nish Nishant

6-Dec-05 9:02

Looks like you'll have to handle it in the dialog that contains the edit control. PreTranslateMessage is probably a good place to do this. Check for WM_KEYDOWN, use GetFocus to see if focus is on your edit control, check for VK_RETURN and do your stuff.

Jethro636-Dec-05 9:06

6-Dec-05 9:06

Hi Nishant:

I'll give that a try.

Thanks for your suggestion.
Mark

Jörgen Sigvardsson6-Dec-05 13:07