|
Assuming that you want to create a string representation of the number (that is 32 => "32" rather than 32 => " " – space being the character with the ASCII code 32), you can use something like this:
CString x;<br />
BYTE b = 123;<br />
x.Format("%u", (unsigned int) b);
or
x.Format("%x", (unsigned int) b); // "7b"
You need to convert it to unsigned int because there doesn't seem to be a way to specify a 1-byte integer in the format string.
Or, if you feel adventurous, you can try stringstream[^] or The Boost Format Library[^].
Florin Crisan
|
|
|
|
|
In your code, bByte is actually a pointer to a BYTE rather than a BYTE. You should have named it better: pbySomethingUseful. p stands for pointer, by stands for byte (b stands for bool, and that one is actually as big as an int). The rest should be a useful name 
So your code should look like:
csValue.Format("%x", (unsigned int) (*pbySomethingUseful)).
Florin Crisan
|
|
|
|
|
You can use CString::Format
csValue.Format( "%x", bByte[1] );
modified on Monday, December 31, 2007 9:36:06 AM
|
|
|
|
|
Hi,
You are attempting to cast a BYTE* into a CHAR. A BYTE* is a pointer to BYTE data....so the casted CHAR will be a CHAR representation of the pointer address of bByte.
CString csValue = (CHAR)bByte[0]; // for individual character
or
CString csValue = (CHAR*)bByte;
If you want to show the hex value of the byte, you can do something like the following:
CString csValue;<br />
csValue.Format(_T("%02X"), bByte[0]);
If you wanted to show the entire contents of the byte array as hex then you will need to wrap the above within a loop and concatenate the result each time to the result string.
<br />
CString csValue, csTemp;<br />
BYTE *pActiveByte = bByte;<br />
while(*pActiveByte)<br />
{<br />
csTemp.Format(_T("%02X"), *pActiveByte++);<br />
csValue.Append(csTemp);<br />
}
I hope that this helps...
Lea Hayes
|
|
|
|
|
I must say that I am little surprised that it works with a BYTE. Weren't %x and %u supposed to take a (four-byte) integer?
Florin Crisan
|
|
|
|
|
Hi all
There is a mfc project and uses my extension mfc dlls. When i look with "Process Explorer" at my mfc exe, the virtual memory of the project is growing. But i am sure there is no memory leak, i tested my projects with Devpartner.
What can be the reason of this growth?
thx.
caner abali
|
|
|
|
|
Maybe there aren't leaks but, neverthless, your application is allocating more and more memory.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
[my articles]
|
|
|
|
|
CPallini thx your reply
yeah i know there are lots memory allocations. i think i have to be much more clear.
When i start my app and it is on idle mode, then it gets some notifications from out of my app, it does its job and again it is on idle mode, but virtual memory size is not as same as first idle mode. and vitrual memory size increases rapidly the third idle mode and followinds idle modes.
i hope i am clear. (sorry for my deficient english 
thx much
caner abali
modified on Monday, December 31, 2007 8:59:10 AM
|
|
|
|
|
canercaner wrote: sorry for my deficient english
Don't worry about, your English (as far as I can recognize, I'm not and English man too) is enough clear.
When your app does it's job servicing another one, does it release all the memory allocated resources?
Post the relevant code, if you think that it may help.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
[my articles]
|
|
|
|
|
yeah in real, it must be a service app, but now it is standard mfc exe.
i think it releases all memory allocated by app because when i exit the app, there is no memory leak. i tested it with Devpartner. And the source code is not small to send in here.
caner abali
|
|
|
|
|
canercaner wrote: i think it releases all memory allocated by app because when i exit the app, there is no memory leak. i tested it with Devpa
Yes, it maybe that final cleanup is correct, but, neverthless, you application holds too much memory while running.
canercaner wrote: And the source code is not small to send in here
Hence, ... Good Luck!
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
[my articles]
|
|
|
|
|
canercaner wrote: But i am sure there is no memory leak
How are you sure?
|
|
|
|
|
i tested my projects with Devpartner.
caner abali
|
|
|
|
|
This may simply be the Process Working Set and therefore would be normal. To see if this is the case, after you notice the increase, minimize your window to the taskbar and see what happens to the virtual memory...if it returns to nearly what it was when you started, then what you are seeing is the working set.
Hope that helps.
Karl - WK5M
PP-ASEL-IA (N43CS)
PGP Key: 0xDB02E193
PGP Key Fingerprint: 8F06 5A2E 2735 892B 821C 871A 0411 94EA DB02 E193
|
|
|
|
|
canercaner wrote: What can be the reason of this growth?
Most likely a memory leak, though you say there isn't one.
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
|
|
|
|
|
Anyone tell me some about the WM_TIMER message handler. How it does works? I was try to a switch for nIDEvent but it does not give a result. I am guessing that no need to use CTime() or SetTimer()
Code:
<br />
void CEfeView::OnTimer(UINT nIDEvent) <br />
{ <br />
if((nIDEvent == ID_RECTANGLE)&&(m_bMouseMoving == TRUE))<br />
SetJoyLockRectangle(1700,700,1710,710); <br />
else<br />
AfxMessageBox(...<br />
KillTimer(1);<br />
modified 13-Mar-13 6:09am.
|
|
|
|
|
The nIDEvent passed to the OnTimer handler, according to documentation [^]:
Specifies the identifier of the timer
i.e. the number of the timer you passed as first argument to the SetTimer method.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
[my articles]
|
|
|
|
|
|
Hakan Bulut wrote: I haven't got a result with it statement.
What do you mean with the above?
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
[my articles]
|
|
|
|
|
Can be more helper about WM_TIMER? They stole my computer.
modified 13-Mar-13 6:08am.
|
|
|
|
|
Can be more helper about WM_TIMER? They stole my computer. I mean that at this statement:
void CEfeView::OnTimer(UINT nIDEvent) <br />
{ <br />
if((nIDEvent == ID_RECTANGLE)&&(m_bMouseMoving == TRUE))<br />
SetJoyLockRectangle(1700,700,1710,710); <br />
else<br />
AfxMessageBox(...<br />
KillTimer(1);
How much at the time comes to an end to the SetJoyLockRectangle's new parameters?
Bitte tun Sie mir nicht antworten, wenn Sie nicht wissen, die Ursache des Problems wirklich oder nur als Antwort. Was ist das? Dies ist das Buch sitzen.
|
|
|
|
|
Hakan Bulut wrote: if((nIDEvent == ID_RECTANGLE)&&(m_bMouseMoving == TRUE))
Well I can't tell if the above is correct, but it looks pretty strange. Is ID_RECTANGLE your (or one of yours) timer identifier? If the answer is no then the code is wrong.
Hakan Bulut wrote: KillTimer(1);
Why are you killing the timer 1?
Hakan Bulut wrote: How much at the time comes to an end to the SetJoyLockRectangle's new parameters?
I cannot even understand the English mean of the above.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
[my articles]
|
|
|
|
|
Oh, it isn't such a difficult topic.
If you need a timer, i.e. a message that OS periodically sends to your window then set a timer (using SetTimer method), specifying:
(1) The timer indentifier, i.e. a number that maybe useful if you app uses two or more timers (though I don't suggest you to use many timers).
(2) The timer elapse, i.e. the time interval separating two timer messages, expressed in ms. Hence, if you need that you timer message handler is called every second, use 1000 as elapse.
(3) an (optional) pointer to a timer callback routine (At the moment,ignore it: use NULL).
Inside OnTimer the message handler:
(1) Check if the timer identifier is the proper one (you may skip this point if you have only a timer in your app, but I don't recommend this behaviour).
(2) Do the timer related operations.
Thats all.
See, there is also an example http://msdn2.microsoft.com/en-us/library/49313fdf(VS.71).aspx[^]
there is also an example.
If you have any doubt, please be detailed about.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
[my articles]
|
|
|
|
|
hi,
When i press {,[ keys in keyboard i get nChar in OnKeyUp() as 219
And when i press },] keys i get 221.
I dont know actually what menas nChar, i see it in MSDN..i get confused...for 1,2,3 keys i get ASCII value of that particular keys coreectly.
But ASCII for { is 123 then why it shows like 219.
Pls clear my confusion.....
Anu
|
|
|
|
|
Well, as stated by the documentation [^], the nChar argument passed to the OnKeyUp() handler, is the virtual key code of the given key, hence it isn't its ASCII code. The fact that the two quantities are the same for numeric (and for letters 'A' to 'Z') keys is a mere (well, not casual, and useful  ) coincidence. Anyway the ultimate reference for virtual key codes is (again documentation states it) the Winuser.h header file
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
[my articles]
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
