|
Assuming you have a window handle, you can send the other window a WM_COPY message. Then, in theory, whatever was selected is in the clipboard and you can have a go at it.
The other way to do it, in theory at least, would be to subclass the other app's window, and then use typical CWnd/CEdit functions to get the text (GetSel(), GetWindowText(), that kind of thing).
Sorry to dissapoint you all with my lack of a witty or poignant signature.
|
|
|
|
|
Thank you very much.
I've already send WM_COPY message but it doesn't work. There's nothing in the clipboard.
::SendMessage(m_hWnd, WM_COPY, 0, 0);
I don't know why it doesn't work. Did I forget something? Guide me, please.
|
|
|
|
|
IADsNameTranslate *pNto;
hr = CoCreateInstance
(CLSID_NameTranslate,NULL,CLSCTX_INPROC_SERVER,
IID_IADsNameTranslate,(LPVOID *)&pNto);
if(FAILED(hr))
{
.....
}
CoCreateInstance always fail , HRESULT : 800401f0
any ideas ??
thanx![Rose | [Rose]](https://codeproject.freetls.fastly.net/script/Forums/Images/rose.gif)
|
|
|
|
|
adara wrote:
LPVOID *)&pNto);
Change it to this:
,(LPVOID **)&pNto);
(two pointer)
Mazy
"So,so you think you can tell,
Heaven from Hell,
Blue skies from pain,...
How I wish,how I wish you were here."
Wish You Were Here-Pink Floyd-1975
|
|
|
|
|
Thanx for your reply , but steel no good
"cannot convert parameter 5 from 'void *** ' to 'void ** '"
|
|
|
|
|
Can't you use smart pointer?It is really better that this kind of using COM.
Mazy
"So,so you think you can tell,
Heaven from Hell,
Blue skies from pain,...
How I wish,how I wish you were here."
Wish You Were Here-Pink Floyd-1975
|
|
|
|
|
Call CoInitialize(NULL)
Mustafa Jahangir
BE Computer Systems
NED University
|
|
|
|
|
Hello adara,
HRESULT value of 0x800401F0 means :
"CoInitialize() has not been called."
Make sure that you always call CoInitialize() at the beginning of any
COM application. You can of course call CoInitialize() just before calling
CoCreateInstance().
Note that even after calling CoInitialize() you may still get an error after
the CoCreateInstance() API if there are any other genuine errors.
However, failure to call CoInitialize() will definitely cause other COM APIs
to fail.
Hope the above helps, adara.
Best Regards,
Bio.
|
|
|
|
|
Thank you so much
|
|
|
|
|
Hello adara,
You're most welcome, adara. I hope the info will help you. Another note :
also call CoUninitialize() on shutdown of you COM app.
Look up Microsoft's SDK documentations for more info.
Best Regards,
Bio.
|
|
|
|
|
|
On Windows 2000, you can make windows transparent and codeproject has two articles on it. But how to make menus transparent?
|
|
|
|
|
You may try to emulate menus with windows. I don't believe there'll be other way.
Tomasz Sowinski -- http://www.shooltz.com
|
|
|
|
|
Hello
How can get list of processes on remote NT server?
I know it on VBScript:
for each Process in GetObject("winmgmts:!//serverhost").InstancesOf ("win32_process")
... processing...
next
but i need this on C++
Thanks
Ernst
|
|
|
|
|
Hello Amigo,
You mentioned VBScript, I therefore get the impression that you are using WMI, or something similar to that.
The API GetObject() gives me the impression that "winmgmts:!//serverhost" is a MONIKER of some sort. If so, you need to use the COM Moniker APIs to get a pointer to the underlying COM object associated with "winmgmts:!//serverhost".
Once you get this pointer, call the InstancesOf() method. You should QueryInterface the returned COM pointer for an IDispatch Interface pointer. Using this IDispatch interface pointer, you would use the GetIDsOfNames() and Invoke() methods.
If the above does not work, there are other ways to accomplish your objective of course. One of them is to create a service program and copy it to your remote machine and use the Service APIs to start the service at the remote machine (this can be done). After starting the service, invoke one of the operations of the service. This could be an operation to get hold of a list of processes on that remote machine.
Thereafter, send this list back to your program as a text file or XML file.
Best of luck, Amigo.
Bio.
|
|
|
|
|
Hey all!
I'm using the CMemDC to avoid flicker in my custom control and it works great, but when I resize the window it flickers like mad.
I have both OnEraseBkgnd() return TRUE/FALSE you name it.
I can't figure out why it flickers during resizing but is fine during other flicker causing operations.
Anyone experience this problem before...?
The control drawing occurs in the OnNcPaint and never flickers except when resized. The scrollbars repaint the Non-client area each LINE/PAGE UP/DOWN and while using CMemDC it doesn'r flicker.
Any suggestions...?
Thanx!
"An expert is someone who has made all the mistakes in his or her field" - Niels Bohr
|
|
|
|
|
If your control is placed on a dialog, make sure the dialog has the WS_CLIPCHILDREN style set.
And if words were wisdom, I'd be talking even more. The Offspring, I Choose
|
|
|
|
|
I don't think that style is limited to dialog only is it...?
WS_CLIPCHILDREN as I understand it doesn't remove flicker, but only excludes the area occupied by the control itself so when drawing in the client dc your lines don't overlap your controls. I think this is similar to ExcludeClipRect functions. The flicker occurs because the lack of double buffering.
It seems CMemDC (or when I do the double buffering myself for that matter) won't remove flicker in both OnNcPaint and OnPaint...only one, not both...maybe it has something to do with OnEraseBkgnd...???
Cheers! 
"An expert is someone who has made all the mistakes in his or her field" - Niels Bohr
|
|
|
|
|
What does your handler to OnNCPaint look like? Specifically, how are you creating your DC.
OnEraseBkgnd should not be an issue in this case, because it is not usually called to erase the NC area, on the client area of your window.
My first thought is to make sure that you make use of the clipping region that is sent in with the WPARAM parameter of the WM_NCPAINT message. This will allow windows to clip the old portions of your display that do not need to be repainted. Then if you are resizing you window larger, there should only be a sliver of the window that needs painting. If you are making the window smaller, there should be no part of the window that needs painting.
|
|
|
|
|
CWindowDC dc(this);
I'm having multiple problems actually.
The flicker doesn't occur in both OnNcPaint/OnPaint only in one or the other.
When the window is being resized everything flickers inside the window...even the OnNcPaint flickers despite working fine with any other operation...?
It seems you can't have flicker free drawing in both OnNcPaint and OnPaint...?
Thanx Kilowatt
"An expert is someone who has made all the mistakes in his or her field" - Niels Bohr
|
|
|
|
|
If you initialize your DC like this in NC paint, I believe that you will have more luck.
HDC hdc;
hdc = GetDCEx(hwnd, (HRGN)wParam, DCX_WINDOW|DCX_INTERSECTRGN);
ReleaseDC(hwnd, hdc);
This will ultimately accomplish the same thing, but then your clipping region is used up, and if you subclassed your window, you could have issues in the future:
CWindowDC dc;
dc.SelectClipRgn((HRGN)wParam);
|
|
|
|
|
Thanx Kilo...
"An expert is someone who has made all the mistakes in his or her field" - Niels Bohr
|
|
|
|
|
I also use CMemDC for my custom control.
However when resizing. your rezing should also be done perfectly.
I saw this once in an article @ codeproject, which has absolutely no flicker
static led control
I hope this will help,
Michel
|
|
|
|
|
I have made a app in VC 6.0 and intend to deploy it over a range of platforms ie. Win9x, Win NT, Win2K and XP.
Can anyone give me the list of all runtimes to include along with my executable. ( I am using MFC as a shared dll.)
|
|
|
|
|
Use Dependency Walker on your exe. That will list all required DLLs
Nish
My miniputt high is now 29
I do not think I can improve on that
My temperament won't hold
www.busterboy.org
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
