Creating new UIWindows, taking over key window -- bad practice?

Question

I'm working on an app which needs to display an overlay an top of everything else. It does this by creating a new UIWindow, and using makeKeyAndVisble to "take over" the screen. When it's done, it gives control back back to the original UIWindow.

Is this a bad thing to do? It feels like it's taking control of the app at a low level, which is generally bad; on the other hand, it's very straightforward to do, so maybe it's perfectly acceptable.

Opinions/experiences?

FLEX uses another UIWindow https://github.com/Flipboard/FLEX — onmyway133, Aug 28 '14 at 09:37

score 4 · Accepted Answer · edited May 23 '17 at 12:06

4

In my experience it is perfectly fine to add another UIWindow on top of the default one.

I also do not think that this is like taking control of the app at a low level. If I consider that the iOS SDK is closely related to the MacOS SDK, I tend to think that multiple window are perfectly supported at a higher level of abstraction: it is only that on iOS they are not so necessary or useful (generally speaking, apart from specific cases).

Digging a bit on the web, I found this interesting discussion on S.O.

Hope it helps.

edited May 23 '17 at 12:06

Community

1
1

answered Jan 28 '13 at 18:36

sergio

68,819
11
102
123

Thanks for the link -- that's exactly what I was trying to ask! :-) – Anna Dickinson Jan 28 '13 at 19:21

Creating new UIWindows, taking over key window -- bad practice?

1 Answers1