|
yes u are right
ok sorry i am new to MFC
|
|
|
|
|
Member 4655685 wrote: ok sorry i am new to MFC
that doesn't prevent you from writing a well written question explaining exactly what you want so we can understand your point and help you this way...
|
|
|
|
|
ok anyway do u know the answer?
|
|
|
|
|
|
Use MoveWindow to set the size of the button once the user has clicked on it and change the text. You need to check width so that the text fits in
m_btn.MoveWindow(10,10,300,40);
Somethings seem HARD to do, until we know how to do them.
_AnShUmAn_
|
|
|
|
|
|
I have a question as to when a preprocessor/macro constant should be used, and when a constant variable should be used.
Or it would be better if i put it in this way,
In a program,
when ONLY a macro constant MUST be used and not a constant variable?
when ONLY a constant variable MUST be used and not any macro constant?
|
|
|
|
|
Usually a constant variable is preferred (because it is typed).
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]
|
|
|
|
|
|
When using macros you should always remember that they're a direct text substitution, not something the compiler does. Imagine that before your source file is passed to the compiler a normal text manipulation program substitutes the macros with their values and this changed text of your source file is sent to the compiler.
One case when macros might be better than constants is when declaring arrays.
#define MAX_PATH 260
char arr[MAX_PATH]; always works, but
const int MAX_PATH=260;
char arr[MAX_PATH]; might give you problems on older compilers.
There is sufficient light for those who desire to see, and there is sufficient darkness for those of a contrary disposition.
Blaise Pascal
|
|
|
|
|
There is no rule when to use constants or when to use preprocessors..
It is always better to use constants because it is typed.
|
|
|
|
|
I am not to able to enter the japanese and other language characters in my editbox control .
Please tell me what is the problem.
Thanx in advance
|
|
|
|
|
are you building in unicode ?
|
|
|
|
|
Initially i was building the project in debug and now in release. But the problem is same in both the modes.
Thanks
|
|
|
|
|
WTF !
I asked about UNICODE, not Debug nor Release mode
|
|
|
|
|
toxcct wrote: I asked about UNICODE, not Debug nor Release mode
Somethings seem HARD to do, until we know how to do them.
_AnShUmAn_
|
|
|
|
|
No Not in unicode but i had tried it also
|
|
|
|
|
|
Dhiraj kumar Saini wrote: No not in UNICODE
then it should !
|
|
|
|
|
can u tell me how to convert it in unicode. I mean how should i change the settings to UNICODE
|
|
|
|
|
Dhiraj kumar Saini wrote: can u tell me how to convert it in unicode. I mean how should i change the settings to UNICODE
Easy as p**s, simply reverse the operation you used when you changed it from Unicode to non-unicode build.
Dhiraj kumar Saini wrote: No Not in unicode but i had tried it also
Here, the change you speak of here.
FFS! Look it up, it's hardly rocket-science.
|
|
|
|
|
Actually I am new to this project. Somebody else changed it from unicode to non unicode. SO i dont know hoe to reverse it.
|
|
|
|
|
oh! So you didn't already try it then?
Which part of what you write is actual fact?
|
|
|
|
|
actually there were certain modifications for which the project was changed from unicode to nonunicode by the pther person. But he left the job and now the modifications are being done by me. But the chat module is not working. which i havent changed.
|
|
|
|
|
Then you are not doing a Unicode build. What is defined under the preprocessor definitions: _MBCS or _UNICODE ?
Many are stubborn in pursuit of the path they have chosen, few in pursuit of the goal - Friedrich Nietzsche
.·´¯`·->Rajesh<-·´¯`·.
[Microsoft MVP - Visual C++]
|
|
|
|