|
Hi
I have a CString containing the hexidecimal handle to a window.
For example 00010AC2.
I want to obtain an actual HWND from it to pass to a function.
Transmit(HWND hWindow, ...other variales ).
So please how do I convert this hexidecimal CString into a HWND type?
Many thanks for your time.
|
|
|
|
|
CAnt you use of Findowindow for get handle?
|
|
|
|
|
CString szMyString = _T("00010AC2");
TCHAR *szStop;
HWND hWnd = (HWND) _tcstol(szMyString, &szStop,16);
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]
|
|
|
|
|
Thank you soo much. Works beautifully!!
|
|
|
|
|
You're welcome.
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]
|
|
|
|
|
Please reffer to 5 or 6 previous message and answer me ... I got your question and replied you
modified on Sunday, September 14, 2008 5:55 AM
|
|
|
|
|
First of all, please have a little patience.
These guys will answer you in their own time - they may be busy or away, and it is a Sunday. They, like all the other members on this site, are answering your questions voluntarily, and they have no obligation to do so, and are not being paid to do so either, so please show a little bit of respect and be thankful for the help they've already given you.
They will answer you in their own time if they have an answer to your questions.
Regards,
--Perspx
Don't trust a computer you can't throw out a window
-- Steve Wozniak
|
|
|
|
|
Thank you.
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]
|
|
|
|
|
No worries
Regards,
--Perspx
Don't trust a computer you can't throw out a window
-- Steve Wozniak
|
|
|
|
|
Thank you from me as well
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
Your welcome
Regards,
--Perspx
Don't trust a computer you can't throw out a window
-- Steve Wozniak
|
|
|
|
|
I don't see any 'please' in your post's title...
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]
|
|
|
|
|
Does it necessary or no?
|
|
|
|
|
It's polite.
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]
|
|
|
|
|
Title of his message is "Mark Salsbery", "cPallini" : PLEASE but I dont know he wants to serach about messages of Mark Salsbery and cPallini or he needs help of them?
|
|
|
|
|
He modified the title. It was originally "Mark Salsbery", "cPallini" : Answer me ...
Regards,
--Perspx
Don't trust a computer you can't throw out a window
-- Steve Wozniak
|
|
|
|
|
I really apologise for what I said and promise It won't happen again ...
I thank all you cool guys for your helps by now ...
|
|
|
|
|
Hello everyone,
I am confused about one simple concept of IUnknown when reading some code,
1. Every coclass component must implement IUnknown, but not a must that every interface (which the coclass component implements) must implement IUnknown;
2. Every interface of every coclass component must implement IUnknown.
Which one is correct?
thanks in advance,
George
|
|
|
|
|
Every interface of every COM component must implement IUnknown since every interface is required to support interface navigation via QueryInterface .
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]
|
|
|
|
|
Thanks CPallini,
Cool! I think your option is you agree with my option 2. Then another question, suppose my component implements interface IX and IY, and both IX and IY will implement IUnknown, so will there be diamond problem?
regards,
George
|
|
|
|
|
George_George wrote: I think your option is you agree with my option 2.
Yes.
George_George wrote: Then another question, suppose my component implements interface IX and IY, and both IX and IY will implement IUnknown, so will there be diamond problem?
Nope (a coclass is not a C++ class).
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]
|
|
|
|
|
Thanks CPallini,
I think for the diamond issue I mentioned, you mean writing some code like this in my sample? The normal solution is providing one common implementation of AddRef/Release/QueryInterface in CFoo, so there is no diamond problem?
CFoo:IX, IY {
IX:IUnknown{}
IY:IUnknown{}
IUnknown{}
regards,
George
|
|
|
|
|
|
Thanks Hamid,
Looks like different from what CPallini said -- CPallini said every interface must implement IUnknown, but the wiki page mentioned every component must implement IUnknown -- "COM objects must minimally implement this interface"? I am confused.
Could you clarify please?
regards,
George
|
|
|
|
|
I think here[^] and here[^] are good articles for you.
|
|
|
|