C / C++ / MFC Discussion Boards

Re: Is it possible to find thread which sent me a message ?

jmkhael1-Jul-04 5:30

1-Jul-04 5:30

You can achieve that by hooking all the SendMessage PostMessage family of API.
To accomplish that several methods are available, and are well discussed on CP. (API Hooking revealed is quite good)
All you have to do is to search for API Hooking in the search box.

Papa

while (TRUE)
Papa.WillLove ( Bebe ) ;

Re: Is it possible to find thread which sent me a message ?

rrrado1-Jul-04 21:38

rrrado

1-Jul-04 21:38

Thanks, I'll look at it

rrrado

&#65309;why the derived class doesn't respond to such message&#65309;

watch_sea1-Jul-04 0:33

watch_sea

1-Jul-04 0:33

I wrote a class CMKCtrl derived form CWnd following Chris Maunder's CGridCtrl
,but my class doesn't respond to the message WM_KEYDOWN and WM_MOUSEWHEEL.
I can't find the reason.
I need help.
Thanks!

Re: &#65309;why the derived class doesn't respond to such message&#65309;

palbano1-Jul-04 4:10

palbano

1-Jul-04 4:10

>> doesn't respond to the message

What does that mean? WTF | :WTF:

"No matter where you go, there your are." - Buckaroo Banzai

-pete

Re: &#65309;why the derived class doesn't respond to such message&#65309;

watch_sea1-Jul-04 15:09

watch_sea

1-Jul-04 15:09

I wrote a class CMKCtrl derived form CWnd.
CMKCtrl doesn't Procress the message WM_KEYDOWN and WM_MOUSEWHEEL.
Confused | :confused:

Automatic Bluetooth device selection

LittleYellowBird1-Jul-04 0:30

LittleYellowBird

1-Jul-04 0:30

Hi,

I am using Bluetooth to communicate with an external device. All I do is talk to COM8, its very simple.

However, when my application runs it asks me to select the device from a drop down list of Bluetooth devices. I want to make the device selection automatic but I have no idea how, can anyone point me in the right direction? Could I get a list of devices from the registry?

Many thanks,

Ali

Re: Automatic Bluetooth device selection

Henry miller1-Jul-04 2:54

Henry miller

1-Jul-04 2:54

Instead of poping up the list, parse it looking for your device.

Most devices have a GUID of some sort that you can lookup.

I don't think the resistry is the right direction. Depending on how your app and device works one of those two might be.

Re: Automatic Bluetooth device selection

LittleYellowBird1-Jul-04 3:10

LittleYellowBird

1-Jul-04 3:10

Thanks for the reply.

Henry miller wrote:
Instead of poping up the list, parse it looking for your device.

I don't have a list of devices, that is what I need and then to be able to select one automatically for the user.

What happens at the moment is that the command 'CreateFile' (which opens the comm port) calls a window/program called 'Bluetooth Console' and I manually select the device from there, then it continues to run my application.

I thought perhaps the registry might contain a list of available devices. I've never done anything with the registry so perhaps I am barking up the wrong tree. Frown | :(

Ali

Re: Automatic Bluetooth device selection

Henry miller1-Jul-04 3:27

Henry miller

1-Jul-04 3:27

go to MSDN and lookup setupapi in particular things like SetupDiGetClassDevs. Once you get close there are a lot of functions to lookup and understand - start reading. Smile | :)

I know our code uses those functions somehow to get a list of devices (CD drives in our case), but it is complex, and under several layers of wrappers that I'm not about to unwind if I don't have to. Good luck figuring it out.

Re: Automatic Bluetooth device selection

LittleYellowBird1-Jul-04 4:30

LittleYellowBird

1-Jul-04 4:30

Thanks, I'll go take a look. Smile | :)

I've been 'Googling' for some help with this but I didn't have a starting point and so my searches have been pretty fruitless.

Henry miller wrote:
Once you get close there are a lot of functions to lookup and understand - start reading.

Its sounds like it will take a while so I better stop typing and get on with it!

Cheers,

Ali

type size

Kamis1-Jul-04 0:02

Kamis

1-Jul-04 0:02

Well,I look into limits.h and see that "short" consists of 2 bytes on my machine and there are 4 bytes for "int" type. So,
1) what does it depend on? (OS, compiler, CPU)
2) Suppose I use such a variable in my prog:
short a;
a=32000;
and than run it on the machine where "short" consists of 1 byte. Will it work correctly?

Re: type size [edited]

bneacetp1-Jul-04 0:17

bneacetp

1-Jul-04 0:17

1) From my understanding, the size of the variable depends on the compiler and/or OS (whether 16bit-, 32bit-, or 64bit-based I think).
2) If you ever ran into a situation where a short took only a byte, you wouldn't be able to get a to 32000. The highest number you could get to would be 255. Look below at the binary math:

1111 1111

1 + 2 + 4 + 8 + 16 + 32 + 64 + 128 = 255

I doubt though that you will ever run into a situation where a short will only take a byte of memory. I hope that this helps.

Happy Programming and God Bless!

"Your coding practices might be buggy, but your code is always right."

Internet::WWW::CodeProject::bneacetp

Re: type size

Antony M Kancidrowski1-Jul-04 0:29

Antony M Kancidrowski

1-Jul-04 0:29

NO! The maximum number you can get in 8 bits is 255

1 + 2 + 4 + 8 + 16 + 32 + 64 + 128 !!!

Ant.

I'm hard, yet soft.
I'm coloured, yet clear.
I'm fuity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Williams (Little Britain)

No - Int is signed

normanS1-Jul-04 2:38

normanS

1-Jul-04 2:38

Being pedantic, INT is a signed value.

For an 8-bit value, the range is 0000 0000 to 1111 1111.

BUT . . . 0000 0001 to 0111 1111 are positive, while for 1000 0000 to 1111 1111, the sign bit (MSb) is 1, so these are negative numbers.

The range is thus -128 to +127 for a 1-byte INT.

10 or 15 years ago, I did some development on Windows 3.11 using Turbo C++ 3.1 (16-bit Integers.) I carefully used only ANSI C commands, for portability, but I also used INTs, instead of SHORT & LONG. This really caused problems when I ported the code to a MicroVax running VMS (32-bit INT, as I recall.)

Re: No - Int is signed

Antony M Kancidrowski1-Jul-04 5:15

Antony M Kancidrowski

1-Jul-04 5:15

NormanS wrote:
Being pedantic, INT is a signed value.

Quite, though I was pointing out the mistake in binary mathematics. Still my statement stands as I do not metion type Wink | ;)

Ant.

I'm hard, yet soft.
I'm coloured, yet clear.
I'm fuity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Williams (Little Britain)

Re: type size

Graham Bradshaw1-Jul-04 0:43

Graham Bradshaw

1-Jul-04 0:43

Kamis wrote:
what does it depend on

The ANSI standards do not impose any restrictions on the size of short, int or long data types, and for portable code, you should make no assumptions. Famously, some (many) years ago, the Microsoft C++ compiler changed the size of an int from 2 bytes to 4 bytes, and broke all sorts of code (including a lot of internal MS stuff), that had hard-coded the assumption that sizeof(int) was 2.

In the Windows world, if you need a guaranteed size, you can use BYTE, WORD and DWORD data types.

If you need code to be portable, you have to make use of sizeof() and all of the #defines in limits.h and/or other header files.

Re: type size

Kamis1-Jul-04 1:25

Kamis

1-Jul-04 1:25

Thanks for the help!

Re: type size

Henry miller1-Jul-04 3:04

Henry miller

1-Jul-04 3:04

Once upon a time, in a land not so very far from here there was a machine. This machine seems just like any other computer at first glance, but when you look closer you discover the size of short, int, and long are all 36 bits!

Don't make any assumptions lest you one day be called upon to port you code to that machine.

You can of course decide how far to go. If your program is using MFC you can be confident that porting to non-windows won't happen, so you only need to consider windows. Microsoft is unlikely to make short less than 16 bits, but it might be bigger.

In general it is safe to assume that short is 16 bits because any machine where that is not the case will either have more bits, or other serious limitations that you have to take into account from the start of design. (they still make 4 bit CPUs, but the code that runs on them is all written in house)

More important these days is to note that sizeof(int) is no longer == sizeof(VOID *). This is breaking a lot of code, 64 bit CPUs are here today some people even have them on their desktop without knowing it. (though windows doesn't use all 64 bits yet, that will come)

Re: Searching for Font (GDI+)

Mike Dimmick1-Jul-04 0:13

Mike Dimmick

1-Jul-04 0:13

You can use GDI and GDI+ in the same application. You can continue to use the GetFontUnicodeRanges API. You can call Graphics::GetHDC to get a GDI HDC from a GDI+ Graphics object. Call Graphics::ReleaseHDC to unlock it when you're finished.

Stability. What an interesting concept. -- Chris Maunder

Re: Searching for Font (GDI+)

Slava20001-Jul-04 0:45

Slava2000

1-Jul-04 0:45

Thank you very match, but i want to avoid a duplucate Windows object HFONT (once as member of GDI+ Font class, and secong HFONT, that i need to select (SelectObject) into HDC for forwarding HDC to GetFontUnicodeRanges):

<br />
Status st=Ok;<br />
INT nFound=0;<br />
InstalledFontCollection InstalledFonts;<br />
INT nCount=InstalledFonts.GetFamilyCount();<br />
FontFamily *pInstalledFamilyes=new FontFamily[nCount];<br />
st=InstalledFonts.GetFamilies(nCount,pInstalledFamilyes,&nFound);<br />
ATLASSERT(st==Ok);<br />
<br />
//Create a font and test it...<br />
for(INT i=0;i<nFound;i++)<br />
{<br />
	BOOL bFontFound=FALSE;<br />
	Font FoundFont(&pInstalledFamilyesi],fontSize,FontStyleRegular,UnitPixel);//First creation<br />
	if(FoundFont.GetLastStatus()!=Ok)<br />
		continue;<br />
	//Create a GDI object HFONT for using WINAPI functions for serching font<br />
	LOGFONTW lf;<br />
	FoundFont.GetLogFontW(pGr,&lf);<br />
	HFONT hFont=::CreateFontIndirect(&lf);//Second creation<br />
	ATLASSERT(hFont);<br />
<br />
	WTL::CDC dc;//One more HDC<br />
	dc.CreateCompatibleDC(pGr->GetHDC());<br />
	<br />
<br />
	HFONT hOldFont=(HFONT)::SelectObject(dc,hFont);<br />
<br />
	//Get the glyphsets array for a font<br />
	GLYPHSET *pGlSet=NULL;<br />
	DWORD nSize=::GetFontUnicodeRanges(dc,pGlSet);//Retrieve a size of an array<br />
	if(nSize==0)<br />
		continue;<br />
	pGlSet=new GLYPHSET[nSize];<br />
	::GetFontUnicodeRanges(dc,pGlSet);//Fill the array<br />
<br />
	pGr->ReleaseHDC(dc);<br />
//........................................ etc.<br />

So can i to avoid duplicate creation of the tested font.

Thanks.

displaying the mem address of chars + char arrays

Member 121044230-Jun-04 23:34

Member 1210442

30-Jun-04 23:34

I can do the following with 'int' with ease:
1: get the address of the pointer
2: get the contents of the pointer (the address it points too)
3: get the value of the variable pointed too.

int *a;
int b = 'B';

cout <<"address of b (the var) = " <<&b <

Re: displaying the mem address of chars + char arrays

Yogesh Kshatriya1-Jul-04 0:25

Yogesh Kshatriya

1-Jul-04 0:25

Modify the code as follows.
It should serv your purpose.

void main(){

char *a;
char b = 'B';

a = &b;

cout <<"address of a = " <<&a <

Re: displaying the mem address of chars + char arrays

Member 12104421-Jul-04 1:37

Member 1210442

1-Jul-04 1:37

Can you please explain this to me:

(unsigned long)(*(&a))

thanks D'Oh! | :doh:

Re: displaying the mem address of chars + char arrays

Yogesh Kshatriya1-Jul-04 3:02

Yogesh Kshatriya

1-Jul-04 3:02

a contains address of b. But if you say cout << a, it won't print the contents of a ( i.e address of b).
But you know it is address i.e. unsigned long type, so force it to print conent of a as an address.

Actually referencing & derefrerncing in the statment is not required.

i.e (unsigned long)(*(&a)) is same as (unsigned long)(a)

Re: displaying the mem address of chars + char arrays

Member 12104422-Jul-04 0:31

Member 1210442

2-Jul-04 0:31

hmmm, yes that makes much more sense, thanks! Smile | :)

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.