(SDK) UIAccessor ... How can DLL related data be found using HWND?

[denisT.MaxDoctor]

Does anyone know or have an idea about how UIAccessor's GetWindowDllDescription and GetWindowDllFileName methods retrieve DLL information using HWND?

[denisT.MaxDoctor]

Well... I can find the process (GetWindowThreadProcessId), find all the modules of the process with their paths (EnumProcessModules, GetModuleFileNameEx)... one of those modules is the DLL I'm looking for, but how do I know which one?

[denisT.MaxDoctor]

As far as I guess, MAX keeps track of its modules and windows and stores the relevant data in certain internal structures. I don't see any other way yet...

[denisT.MaxDoctor · Accepted solution]

О! GetWindowModuleFileName is that simple.

But now I have a method that collects all the process modules, and hence the file names of all the DLLs used with MAX 😜

[klvnk]

isn't that just DllDir ? then from there to all the DllDesc which stores the filename of the plugin.

DllDir& dlldir =  ip->GetDllDir();
for(int i = 0; i < dlldir.Count(); ++i)
{
    DllDesc& dlldesc = dlldir[i]; 
    mprintf(_T("%s\n"), dlldesc.fname);
}
 

should do it.

Ok I misunderstood it's not plugins you're interested in 🙂

[denisT.MaxDoctor]

I'd like to clarify the purpose behind all of this. The reason is that certain built-in and third-party plugins and tools create dialogues and windows and pop them up. When operating in batch mode, these pop-ups can be quite bothersome. To address this, I've implemented a hook that monitors these pop-ups and has the capability to conceal them for specific plugins. Therefore, I aim to ensure a precise association between each window and its corresponding plugin.

Examples:
Biped - Move All Mode

Skin - the Weight Table

VertexPiant -  the Dialog
Unwrap_UVW - the Editor

etc.

[denisT.MaxDoctor]

Maybe there is something I am missing.

My GetWindowModuleFilename method is three times faster than UIAccessor.GetWindowDllFileName. However, my GetWindowDllDescription method is about five times slower than UIAccessor.GetWindowDllDescription.

Perhaps MAX maintains a hash table of DLL descriptions, accessible either by DLL filename or DLL module handler.