The thing with UIWindows is that you really should never make your own, and your app should really never need to make a new window. The UIKit is designed so that you should be able to do 99.9% of what you need using view controllers and views. The reason we are using a window in this case is to keep a nice separation between then Unity views and the hacked overlay views. This way if Unity is doing something funky with their views and their window we wont break it.

However, remember that windows are actually view subclasses. and views dont necessarily clip their subviews, so changing the size of the window will not effect the size of the subviews (at least not the way we are doing it in the code here) so: make sure that all your views are resized to smaller frame rects, make sure that your window is clipping to it’s bounds and has a clear background and is not opaque.

Then, (as I said before) add the webview into your window, but make sure it’s rectangle is also smaller.

Good luck!
Cheers!
-B

Thanks for the great tutorial! I’m not versed in ObjC… but this helped alot. I am currently trying to integrate a webview in my Unity project. With this I have the webview coming up on top of Unity, but I’m trying to limit the view to a small portion of the screen. I thought that changing the overlayWindow rect might have an effect, but no luck.

overlayWindow = [[UIWindow alloc] initWithFrame:CGRectMake(0, 431.0, 320, 49.0)];

Any suggestions?

Thanks,
Matt

That should be all fixed now, thanks for pointing that out!

Cheers!
-B