C / C++ / MFC

David Crow9-Jun-03 2:39

David Crow

9-Jun-03 2:39

Something like:

HWND hDesktop = GetDesktopWindow();
EnumChildWindows(hDesktop, EnumProc, 0);

BOOL CALLBACK EnumProc( HWND hWnd, LPARAM lParam )
{
return TRUE; // to continue enumeration
}

I've not ever needed to do something like this before, but I suspect it will return more windows than just the icons. Top-level applications probably have the desktop as their parent window, too.

Jarek G9-Jun-03 3:22

Jarek G

9-Jun-03 3:22

Thank you David!
I tryed that to Smile | :)

and its just like you said it return manny windows, to manny.
But the search goes on I found a VB program that doing this and I am on my way to disassamble the code!

I think I have something to learn here It started as an effort to make a funny program but now its a chalange!

/Jarek

He believed the commercials that said drink beer, get laid
but at closin' time he was alone, he didn't get paid.
Last night his lover was a razorblade..
"Dan Reed song Mix it up"

What do you want to patch today?

David Crow9-Jun-03 5:36

David Crow

9-Jun-03 5:36

Try this:

LPMALLOC pMalloc;
LPSHELLFOLDER pDesktopFolder = NULL;
HRESULT hResult;
LPITEMIDLIST pidlItems = NULL;
LPENUMIDLIST ppenum = NULL;
ULONG celtFetched;
SHFILEINFO fi = {0};

hResult = SHGetMalloc(&pMalloc);
if (NOERROR == hResult)
{
hResult = SHGetDesktopFolder(&pDesktopFolder);
if (NOERROR == hResult)
{
hResult = pDesktopFolder->EnumObjects(NULL, SHCONTF_FOLDERS | SHCONTF_NONFOLDERS, &ppenum);
if (NOERROR == hResult)
{
while (hResult = ppenum->Next(1, &pidlItems, &celtFetched) == S_OK && (celtFetched) == 1)
{
SHGetFileInfo((const char *) pidlItems, 0, &fi, sizeof(fi), SHGFI_PIDL | SHGFI_ICON | SHGFI_DISPLAYNAME);

TRACE2("Icon handle for ]%s[ = %#x\n", fi.szDisplayName, fi.hIcon);

pMalloc->Free(pidlItems);
}

ppenum->Release();
}

pDesktopFolder->Release();
}
}

Is it Possible to export a class from a DLL?

Jarek G10-Jun-03 8:12

Jarek G

10-Jun-03 8:12

Thank you David!
It works I can get the Desktopicons Smile | :)

I saw similar code in Q&A on MSDN Thank you again your code was better.

/Jarek

He believed the commercials that said drink beer, get laid
but at closin' time he was alone, he didn't get paid.
Last night his lover was a razorblade..
"Dan Reed song Mix it up"

What do you want to patch today?

Theopulus6-Jun-03 0:29

Theopulus

6-Jun-03 0:29

I've been reading some messages and articles, but I haven't found any example of using a DLL to store classes and then use them linking it dynamically in an exe.

At present, I'm using Delay Load to create instances of my classes, but I don't want to use .lib and .h files.

Is it possible to do that?

Thanks in advance.

Cedric Moonen6-Jun-03 1:14

Cedric Moonen

6-Jun-03 1:14

Take a look at this article: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dncomg/html/msdn_cpptocom.asp[^]

It explain in detail everything you'll need to start !!
Hope this helps

berndg6-Jun-03 2:29

6-Jun-03 2:29

Cedric,
I think you might be overshooting the target here. COM is one thing, but you might also simply export a C++ coded class with the __declspec(dllexport) statement in MSDEV, and import it with __declspec(dllimport). Of course that technique requires C++ to be used on both sides (unlike COM).

Bernd

Cedric Moonen6-Jun-03 2:49

Cedric Moonen

6-Jun-03 2:49

Yep, that's rigtht, but in this case, you'll have to include the .h and the .cpp files from all your classes in the project then!
If you use a 'kindof' COM model, you'll just have to include the .h file from the interface (just virtual functions), and then use a global function from the dll that returns a pointer to the base class that is in fact 'a pointer to a specific child class'. So, in that way, you don't have to include .h and .cpp files from all your derived classes. The client program doesn't even know the existence of the derived classes: he just call virtual functions from the base class that are redirected to functions from the derived class.

Or, I perhaps misunderstood the question Smile | :)

berndg6-Jun-03 2:58

6-Jun-03 2:58

You didn't misunderstand the question, but the DLL export statement...

You have to include header files in both sides (there is no type library query or so), but the code stays on the server side (DLL). Just look at the whole thing as if it were a good old function library, only with dynamic linking, classes, C++, and so forth.

This is not a "kindof COM", this is a C++ class library. Plain, simple, and useful.

Bernd Smile | :)

geo_m6-Jun-03 3:40

geo_m

6-Jun-03 3:40

But I think, that exporting anything C++ means that the another compiler might not be able to import it (due to different non-standard name mangling) and you must use the same compiler then. But I can be wrong.

berndg6-Jun-03 3:53

6-Jun-03 3:53

Agreed. Exporting a class from a DLL does not allow for multi-language use, or multi-compiler use.
I agree COM is the more powerful tool in places, but it also is an overkill in many others.
Bernd

Theopulus6-Jun-03 6:02

Theopulus

6-Jun-03 6:02

Thanks for all the answers, but I'm not looking for a COM interface. Instead of that, I'd like to use plain DLL's, but as I've just read, I'd have to include .cpp files on both sides and that's what I don't want to do.

All I want is to give a DLL without giving even the header files. I don't want any .h or .lib.

Hope I've explained better this time.

Thanks in advance!!

__________________________
Fernando de Francisco Cano
__________________________

berndg6-Jun-03 6:15

6-Jun-03 6:15

Fernando,
if you want to ship a library, then you must allow clients to connect to that library. One technique is to use static linkage. To do that, you will ship a .lib file and a header file. Another technique is dynamic linkage, for which you will ship a .DLL and a header file. Finally, you could ship COM controls, which come in the physical form of .DLL or .OCX files. You don't need to include header files because COM provides query mechanisms, but essentially in any case you cannot just ship something without letting your user's compiler know what it is.

You seek the impossible unless you don't wish your DLL to be of any use - in which case you could just ship a DLL without a header file Unsure | :~

Bernd

berndg6-Jun-03 6:17

6-Jun-03 6:17

... oh, and in order to get this clarified: you do not ship source code (except header files), unless you wish to. None of the three techniques I listed requires distribution of .cpp files, no whatsoever.
B.