Unity Window Handle

Hi,

This may not the correct forum to post this type of request. I have searched lot but no result.

In unity, when I use "Process.GetCurrentProcess().MainWindowHandle" returns 0 only,
which is not returning the exact Unity Window Handle. Can anyone help me on how to get the unity window handle.

Thanks in advance.

 

you can't get the unity window handle to my knowledge. Unity manages the whole thing

 

I am developing the game which will run like as gadget. So, If I have the unity window handle, it may help me to use the handly with native API atleast.

 

why do you use an engine that you know will run in an own self managed windows when you want to run something as a gadget? makes completely no sense.

but depending on what you want to do: embedd the offline webplayer in its IE activex form into a standalone app

 

Thnaks for update,

it is kind of data driven game which shows status information with custom 3d objects [includes translation, rotation].

No other way other than IE activex for standalone system?

 

well you can always use the application name -> find process on Win32 level -> get handle

but it requires that you are on pro to call out to native code

 

Well, Thanks Dreamora

 

I know this post is old, but since this comes up in searches, I thought I'd post the answer. This will get Unity's Window handle (on Windows of course), and it doesn't require Pro to work. Tested on Unity 4.5, works in editor and build.

Code (csharp):

1. [System.Runtime.InteropServices.DllImport("user32.dll")]
2. private static extern System.IntPtr GetActiveWindow();
3.  
4. public static System.IntPtr GetWindowHandle() {
5.   return GetActiveWindow();
6. }

Edit: Note that this will not work if the Unity Window is not the active Window. In the editor it will return the currently focused editor window.

 

Yes. Natives (like Windows 32/64 API) DLLs always worked on ALL Unity version (Pro or Not). The contrary informations are an Urban Legend.


Sorry for the resurrection.

 

Only if they're in the project's root path or system path. In 3-4.x, Unity didn't allow you to access to native DLLs in the assets folder and would throw an error telling you needed pro. Most people just got around this by moving the DLLs into the project root (outside assets) including many asset store products (baffling enough they were allowed). Unity 5 did away with this restriction since there is now only one version of Unity. That's why I felt it necessary to make it known you didn't need pro.

 

Of course...

 

Is there a more robust solution by now? (~Unity 2018.3). I intend to use the window handle to set the window position for non-fullscreen runs. I have multiple Unity builds running at the same time, and having them all appear at the same position is annoying. And to my knowledge, the '-screen-position <x> <y>' commandline argument is still not available.

 

Hi has anyone still managed to find the right answer for this? I am also stuck in the same situation.

 

This is exactly what I posted above in message #8.

 

Some Magic Here is !!!

 

Once more I'm giving this issue a resurrection.
We have a bug with this solution already, because there is a chance, that Active or Foreground window has changed right before you try to access it. And we move other windows via Win32 API occasionally.

 

This issue has been fixed now, in Unity 2021.2: https://issuetracker.unity3d.com/is...t-mainwindowhandle-always-returns-0-on-builds