|
Dear Friends,
I have a .li file which works well in Release Mode but it gives error in Debug Mode. I have told to do necessary modification in .lib file to work satisfactorily in Debug mode.
Will you please write to me how to handle this task. Any kind of suggesion will be highly appreciable.
Thanking You in advance..
Billar
|
|
|
|
|
Can you specify what error you get in Debug mode.
|
|
|
|
|
hot to get font file path to font selected to dc?
all i can get is something depending on actual language, not real file path
(arial bold instead of arialb.ttf, 'bold' is act language dependant)
|
|
|
|
|
Can we change wParam in callback keyboardProc function in order to get the character we want , in the destination window(by changing the actual virtual keycode). In my practice, when I changed the wParam inside callback function I didn't get the desired result(no change in the result) . Can any one help me.
Thanking you
arathi
|
|
|
|
|
Hi !
I'd like to know how many lines of code (real code, without comments) my project is made of. Do you know of any tool to do that ?
I'm using Visual Studio .NET 2003.
Thanks !
Jerome
|
|
|
|
|
|
I need to find out which thread send message to my window's message queue.
Is this possible ?
Thanks
rrrado
|
|
|
|
|
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 ) ;
|
|
|
|
|
Thanks, I'll look at it
rrrado
|
|
|
|
|
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!
|
|
|
|
|
>> doesn't respond to the message
What does that mean?
"No matter where you go, there your are." - Buckaroo Banzai
-pete
|
|
|
|
|
I wrote a class CMKCtrl derived form CWnd.
CMKCtrl doesn't Procress the message WM_KEYDOWN and WM_MOUSEWHEEL.
|
|
|
|
|
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
|
|
|
|
|
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.
|
|
|
|
|
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.
Ali
|
|
|
|
|
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.
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.
|
|
|
|
|
Thanks, I'll go take a look.
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
|
|
|
|
|
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?
|
|
|
|
|
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
|
|
|
|
|
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)
|
|
|
|
|
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.)
|
|
|
|
|
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
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)
|
|
|
|
|
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 #define s in limits.h and/or other header files.
|
|
|
|
|
|
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)
|
|
|
|