|
Here is remarks of VK_DECIMAL :
A virtual key code for the numeric keypad DECIMAL POINT (.) key.
but what is happen if the user hit point (.) not from numeric keyboard ? Or when decimal separator is comma (,), not point ?
|
|
|
|
|
Flaviu 2 wrote: but what is happen if the user hit point (.) not from numeric keyboard ?
You are right on this, it wouldn't be detected.
Flaviu 2 wrote: Or when decimal separator is comma (,), not point ?
You are wrong here, the key on numerical keypad alway corrensponds to the decimal separator.
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.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
I learn something here , that the point key from numerical keyboard corespond to decimal separator , whatever it would be , thank you for that ... but still , I didn't know how to get keyboard code of global decimal separator ... 
|
|
|
|
|
Flaviu 2 wrote: but what is happen if the user hit point (.) not from numeric keyboard ?
You may find the scan code for such a key this way (at least it works on my system):
TCHAR a[2];
int nResult = ::GetLocaleInfo(LOCALE_USER_DEFAULT,LOCALE_SDECIMAL,a,2);
SHORT vkCode = VkKeyScan(a[0]);
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.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
Didn't working , because
SHORT nDecimal = VkKeyScan(m_chDecimalSymbol);
return 190 , which is not 46 (.) ....
|
|
|
|
|
It's correct: 190 is VK_OEM_PERIOD, that is the scan code of (the lef hand) key for the '.'.
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.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
Flaviu 2 wrote:
sTemp.ReleaseBuffer();
if(nResult)m_chDecimalSymbol = sTemp[0];
As an aside, you should swap these two lines. Doesn't make sense to read sTemp after releasing its buffer... 
|
|
|
|
|
|
My foulish !
UINT nDecimal = (UINT)m_chDecimalSymbol;
Thank you all , from your patient , plus , I learn something here , it's alway a pleasure to talk with you !
|
|
|
|
|
Regarding my statement about ReleaseBuffer(), it turned out I was wrong. In your example it probably doesn't make a difference, but, generally speaking, it was correct to call it when you did.
Just wanted to let you know, as you may not aware of new posts that are not in response to you, personally. See David Crow's response to my previous posting in this thread for more info.
|
|
|
|
|
Stefan63 wrote: Doesn't make sense to read sTemp after releasing its buffer...
Sure it does. As a matter of fact, you shouldn't do anything with sTemp until you have released it's internal buffer.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Some people are making such thorough preparation for rainy days that they aren't enjoying today's sunshine." - William Feather
|
|
|
|
|
Thank you for reminding me why I hate working with MSDN classes. The term 'ReleaseBuffer' appears to be pretty clear on what it does, but like so many times, MS has its very own and unique understanding. 
My error was to only check on GetBufferSetLength(): GetBufferSetLength at MSDN.
Unfortunately the explanation of true meaning of the effect of ReleaseBuffer after GetBufferSetLength() is ambiguous, although, based on the function name I didn't realize that. In fact, when I checked ReleaseBuffer just now, I found that it also isn't clear - that is, it isn't until you look at the code example. Or, more to the point, the comments added in there. Without that example I might in fact still question your assertion.
I'm still unsure whether it is required to call ReleaseBuffer() before accessing the CString variable; according to the documentation all it does is resize the buffer to the required size and, optionally, insert a terminating 0 character. The latter isn't required since GetLocaleInfo() already does it. The former isn't needed either, as the buffer was allocated with the correct size.
If there is any other hidden functionality of ReleaseBuffer(), I am not aware of it.
|
|
|
|
|
the code is print one time correct and one time junk.i didnt anderstand why he print junk
the program in c
main file
#include<stdio.h>
#include<malloc.h>
#include"tal.h"
void main()
{
Node *pol1=create();
printf("%d\n",push(pol1,2,3));
printf("%d\n",pol1->size);
}
h file
typedefstruct node
{
int mekadem;
int hezka;
int size;
struct node *next;
} Node;
Node *create();
int push(Node *pol1,int a,int b);
ex.c file
#include<stdio.h>
#include<malloc.h>
#include<stdlib.h>
#include"tal.h"
Node *create()
{
Node *q = (Node*)malloc(sizeof(Node));
q->hezka=0;
q->mekadem=0;
q->next=NULL;
q->size=0;
return q;
}
int push(Node *pol1,int hez,int mek)
{
Node *temp=pol1;
Node *followtemp=pol1;
Node *node=(Node*)malloc(sizeof(Node));
node->hezka=hez;
node->mekadem=mek;
node->size=0;
node->next=NULL;
if(pol1->size==0)
{
free(pol1);
pol1=node;
}
return ++(pol1->size);
}
|
|
|
|
|
In create() you are creating a new node, setting size to zero. In push() you check if size is zero, and then free the node. Your pointer poll will no longer be valid.
|
|
|
|
|
but after i free the POL1 i did
pol1=nod
and then ++(pol1->size)
so size is supposed to be 1
|
|
|
|
|
Member 7809860 wrote: but after i free the POL1 i did
pol1=nod
Yes, but that only changes the local reference to your node.
If you want the callers value to be updated you will need something like:
int push(Node **pol1,int hez,int mek)
{
Node *temp = *pol1;
Node *followtemp = *pol1;
Node *node = (Node*)malloc(sizeof(Node));
node->hezka = hez;
node->mekadem = mek;
node->size = 0;
node->next = NULL;
if ((*pol1)->size == 0)
{
free(*pol1);
*pol1 = node;
}
return ++(*pol1->size);
}
and call it like
void main()
{
Node *pol1 = create();
printf("%d\n", push(&pol1, 2, 3));
printf("%d\n", pol1->size);
}
|
|
|
|
|
The problem is that
int push(Node *poll, int hez, int mek) passes the pointer poll by value, not by reference. The assignment poll=node; is valid within push(), but the change will not be passed to the caller. As a result, after calling push() the pointer poll in main will still point to the memory location of your first node, but this node was already freed. The newly created node will be lost, as you failed to pass the pointer back to main. Your print statement accesses poll->size which is now undefined and can have any arbitrary value.
|
|
|
|
|
you are right.i solved the problem with *pol1=*node .
thanks
|
|
|
|
|
i have address a function of a process
example :73D7469D
i don't know how to read this function of that process and interact with this function
plz help me
thanks so much..sorry if my english isn't good
|
|
|
|
|
so0_lanhlung2 wrote: i don't know how to read this function of that process and interact with this function
Short answer: you can't do that.
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.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
i open spy++ and i right click\propeties.i see winproc:001....(address) of a window
may i redefine this winproc of this window to send WM_KEYDOWN.
because this window had security...i can't sendmessage,postmessage,defwinproc
can you help me .
thanks so much
|
|
|
|
|
That's more or less the primary purpose of having security there. Without it, the opportunities for hackers and writers of viruses would be truly endless. Access to the victim's e-mails, social networks, and bank accounts would be just a few WM_KEYDOWN messages away!
|
|
|
|
|
i have 2 class CControl and CMainFrame ( MFC), in CControl i have a function
void CControl::OnButtonRun()
{
// TODO: Add your control notification handler code here
CBaocaoDoc *pDoc = GetDocument();
if(pDoc->dc_status)
{
if((pDoc->nc_status) && (pDoc->phoi_status))
{
m_feetrate.SetRange(0,1000,TRUE);
UpdateData(TRUE);
m_fr=temp_mfr; // lay toc do
m_feetrate.SetPos(temp_mfr); // set toc do
SetTimer(2,1000,NULL);
UpdateData(FALSE);
}
else MessageBox("Chua chon chi tiet hoac file","Thong bao",MB_OK);
}
else MessageBox("Chua xuat file chua duong dung cu","Thong bao",MB_OK);
}
now i want call OnButtonRun() from CMainFrame, if i call function like
void CMainFrame::OnImportfile()
{
// TODO: Add your command handler code here
CControl abc;
abc.OnButtonRun();
}
MFC have error C2248: 'OnButtonRun' : cannot access protected member declared in class 'CControl'
please, help me, thanks .
|
|
|
|
|
I'm assuming the OnButtonRun function is an event handler.
I'm further assuming that this function is called on a button click.
You can send the BN_CLICKED message to the button to simulate the button click which will then call the OnButtonRun function -
abc.SendMessage(WM_COMMAND, (BN_CLICKED << 16) | BUTTON_ID, abc.GetDlgItem(BUTTON_ID));
Having said this, you may need to access the already existing instance of CControl instead of creating a new instance of it.
|
|
|
|
|
there's a couple of ways to do it, one is using SendMessage() or PostMessage() to message the event handler (as someone has already suggested, this is the proper way)... here's another resource for how to do it:
Scroll to the bottom of the page for solutions:
http://www.experts-exchange.com/Programming/System/Windows__Programming/MFC/Q_21374701.html[^]
if you've defined CControl yourself, then you can take a shortcut and just make the method public (by doing this you're ignoring the framework)
I noticed that you're also creating CControl when you call it, that doesn't really make sense if the control is also associated with something in the GUI since you're creating this on the stack that means it'll be gone after the execution of OnImportfile()
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
