Re: Question about üarent-frame changes

[martin rudalics]

> The biggest problem for me in this area today is that "visibility" on
> GUIs and ttys apparently is not the same thing. For example,
> make-frame-visible seems to do nothing for tty frames. So I guess all
> tty frames are always visible in the sense that frame::visible is
> non-zero.

You mean because 'suspend-tty' acts on top-level frames only?

Another issue we would have to resolve in some way is whether a child
frame should (or could) be given input focus on TTYs: That is, whether a
user may type "into" a child frame, for example, when an application
issues a 'yes-or-no-p' question within a child frame equipped with a
minibuffer window.

> But that would be too easy of course, which is why frame::visible has 2
> bits, and if the second bit is set the frame is "obscured" (happens with
> C-x 5 2), which I'd call sort of invisible because it can't be seen but
> that's of course naive.

Wasn't that second bit used exclusively for redisplay purposes and as
such not available to Lisp code?

martin