|
Thanks for your help, Nelek!
regards,
George
|
|
|
|
|
Very simple but very good explained, thanks for
Greetings.
--------
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
“The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet.” - Michael A. Jackson
|
|
|
|
|
hi ....
i have developed one win 32 dll application ..in that application
i want to use CString how can i use this ...tell me how to use the MFC data types with in Win 32 Dll Application
i also included #include "afxcoll.h"
how can i use CString datatype in win32 dll
Thanks in advance....
Nothing is Impossible...
|
|
|
|
|
kmani_soft wrote: i want to use CString how can i use this ...tell me how to use the MFC data types with in Win 32 Dll Application
Why?
use std::string instead.
Anyway, have a look at http://msdn2.microsoft.com/en-us/library/5bzxfsea(VS.80).aspx[^]
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.
|
|
|
|
|
CStringT is no longer just part of MFC. Just use the appropriate
header file:
Header Use for
cstringt.h MFC-only string objects
atlstr.h Non-MFC string objects
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
Hello everyone,
I find strange result in the following program.
1. For string array, dereferencing it will result in the string itself, but for int array, dereferencing it will result in the address of the array;
2. When dereferencing it twice (operator **), why the result is always the 1st element in both string array sample and int array sample?
int main()
{
wchar_t me[] = L"Hello World \n";
wchar_t (*me2_ptr)[14] = &me;
wcout << *me2_ptr << endl;
wcout << **me2_ptr << endl;
int values[] = { 10, 20, 30, 40, 55, 60, 70, 80, 90, 100 };
int (*pval)[10] = &values;
wcout << *pval << endl;
wcout << **pval << endl;
return 0;
}
thanks in advance,
George
|
|
|
|
|
Hi,
I'm not exactly sure why you are using wchar_t (*me2_ptr)[14] = &me; and its equivalent for the int.
However, look at things like this:
me2_ptr - is a pointer on a pointer on a wchar_t
*me2_ptr - is a pointer on a wchar_t
**me2_ptr - is a wchar_t
pval - is a pointer on a pointer on a int
*pval - is a pointer on a int
**pval is a int
If you call operator<< on a pointer on a wchar_t it assumes its target is a c-string and delivers the string itself. If you call operator<< on a pointer on a int it just delivers the value of the pointer. This is just the way operator<< is implemented.
|
|
|
|
|
Thanks Doc,
Why *me2_ptr - is a pointer on a pointer on a wchar_t*? I think &me is a pointer to wchar_t, right?
Since in the following code, you can see &me is the same as me,
int main()
{
char buf[] = "Hello World \n";
_ASSERT (buf == &buf);
return 0;
}
regards,
George
|
|
|
|
|
The depicted behavior is not so strange...
George_George wrote: 1. For string array, dereferencing it will result in the string itself, but for int array, dereferencing it will result in the address of the array;
In fact the behavior is quite similar: the name (or the address-of operator & applied on the name, remembering past posts... ) of the int array returns the address of the memory containing the integer values as well the name of the character array returns the address of the memory containing the character values;
you find a noticeable difference in the output only because a (C -like) string is nothing more than the pointer to the memory holding the zero-terminated character sequence, hence whenever wcout finds a (wide) character pointer, it prints the characters belonging to the pointed memory.
George_George wrote: When dereferencing it twice (operator **), why the result is always the 1st element in both string array sample and int array sample?
Again, nothing strange here. Given a int pointer, say int *p , deferencing it means: "take the content of the pointed memory", namely the integer value at address p (that coincide with the first int element of the array). The same point applies to the character array.
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.
|
|
|
|
|
Hi CPallini,
What makes me confused is, in my test program before, the address of a string array should be the same as the string array itself. For example below, buf is the same as &buf.
int main()
{
char buf[] = "Hello World \n";
_ASSERT (buf == &buf);
return 0;
}
I think in the code posted in the question, me2_ptr = &me, and it is the same as me, without dereferencing it, if we simply wcout << me2_ptr, result should be the same as wcount << me? Why we need to dereferencing it by operator * in order to get the same output of wcout << me?
regards,
George
|
|
|
|
|
Because you defined (correctly) it as pointer to an array address (i.e. another pointer), i.e.
*me2_ptr contains the address of me (the same address returned by &me ).
Hence me2_ptr isn't a pointer to w_char s, but instead a pointer to a pointer of w_chars s (added: that turns out to be the same address...).
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.
modified on Tuesday, December 11, 2007 5:41:54 AM
|
|
|
|
|
Hi CPallini,
If you have Visual Studio at hand, you can debug my sample program, and you can find that me is the same as me2_ptr (you can watch it), so me2_ptr is the same as me, I do not know why *me2_ptr is also the same as me?
regards,
George
|
|
|
|
|
You're right. *me2_ptr and me2_ptr both hold the same address (but are different types, this way wcout behaves differently on them), this probably is related to the fact that dereferencing an array name (i.e. *me2_ptr ) should return the same address returned by the array name itself.
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.
|
|
|
|
|
Thanks CPallini,
I think you mean,
1. *me2_ptr is value of array type, and wcout is overloaded to print out the string array;
2. me2_ptr is address of array type, and wcount will print the address of array.
Right?
regards,
George
|
|
|
|
|
Technically the ostream extraction operator << is overloaded, but, poorly speaking the answer is yes.
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.
|
|
|
|
|
Cpallini has already explained at some length (to me too!) how the address of an array has the same value for convenience to printf (and it's relations).
The two bits of code you've shown do the same thing with derefencing. The only difference is that the wcout is clever enough to go "oh, I won't give a number, I'll give a lump of text - aren't I helpful?".
The short answer to question 2
BECAUSE.
Longer answer...
Because it has been defined that way by people cleverer than us.
Is this feature causing you problems?
Iain.
|
|
|
|
|
Thanks Iain,
My question is answered.
regards,
George
|
|
|
|
|
Hi,
I am using WM_CTLCOLOR to make the static text transparent and change the font and colour. Please can you tell me how to do the font-clean-up action if any is required here?
HBRUSH CF4_NewEstimate::OnCtlColor(CDC* pDC, CWnd* pWnd, UINT nCtlColor)
{
HBRUSH hbr = CResizableFormView::OnCtlColor(pDC, pWnd, nCtlColor);
CFont *m_pFont = new CFont;
m_pFont->CreateFont(12,0,0,0,600,0,0,0,0,0,0,ANTIALIASED_QUALITY,0,"MS Sans Serif");
CFont *pOldFont = NULL;
switch (nCtlColor)
{
case CTLCOLOR_STATIC:
pDC->SelectObject(m_pFont);
hbr = (HBRUSH)::GetStockObject (HOLLOW_BRUSH);
pDC->SetBkMode (TRANSPARENT);
pDC->SetTextColor(RGB(255,128,0));
break;
}
return hbr;
}
Thanks.
Fortitudine Vincimus!
|
|
|
|
|
Tara14 ase CTLCOLOR_STATIC: pDC->SelectObject(m_pFont);
This is not the correct way to change the font of a window. You should call the SetFont() function to change the font and this need to be done only once( in OnInitdialog() or OnIntitialUpdate() function etc ).
|
|
|
|
|
I want to add a 16-bit color cursor.
But when I insert a new cursor, there is a default monochrome one, and LoadCursor will use that one by default. How to use 16-bit cursor?
|
|
|
|
|
Just design your cursor in the resource editor, give it a IDC_NAME and use ::LoadCursor and ::SetCursor.
if you load it but not set it active...
Greetings.
--------
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
“The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet.” - Michael A. Jackson
|
|
|
|
|
setted, but the monochrome one using the same ID takes effect
|
|
|
|
|
This is to set the normal white arrow that is always in all MFC-Win32 app by default.
HCURSOR m_hCursor;
;
m_hCursor=AfxGetApp()->LoadStandardCursor(IDC_ARROW);
if (m_hCursor)
::SetCursor (m_hCursor);
And here I set my own drawn cursor
m_hCursor=AfxGetApp()->LoadCursor(IDC_SELPOINT);
if (m_hCursor)
::SetCursor (m_hCursor);
Note that the ID that I use to load my own cursor is the ID that I give to the cursor in my resources editor.
What are you making?
Greetings.
--------
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
“The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet.” - Michael A. Jackson
|
|
|
|
|
That's just what I do.
The problem is that I added a "16-bit color" cursor, not the default monochrome one. But LoadCursor will load the monochrome one instead of the "16-bit color" one. They have the same ID.
|
|
|
|
|
How can one determmine if a given floating point variable is a mathematical integer (1,2,3,4,5...)? I figured I could divide by one and check for zero as a remainder. Doesn't work.
float fNumber = 861;
float one = 1;
fmod(fNumber, one)
modf(fNumber, one)
Both of these return a value of .9998936354755 (or some other decimal very close to 1).
I've tried various combinations of float and double, but get the same results.
Ideas? Thanks.
|
|
|
|
|