Re: Q: child frames on ttys

["Gerd Möllmann" <gerd.moellmann@gmail.com>]

Robert Pluim <rpluim@gmail.com> writes:

>>>>>> On Wed, 21 Aug 2024 10:03:33 +0200, Gerd Möllmann <gerd.moellmann@gmail.com> said:
>     >> 
>     >>> 6. Update: Build frame matrices for all windows visible on a terminal.
>     >>> Copy visible parts of child fraem desired glyphs to root frame
>     >>> desired glyphs. Then write to the screen.
>     >>> 
>     >>> 7. After writing to the screen, copy visble parts of root frame
>     >>> current glyphs to current glyphs of children.
>     >> 
>     >> What does the current glyph matrix of the root frame contain now?  The
>     >> overwritten parts or the original ones?  Or are the original parts
>     >> stashed away so they can be easily reused when the child frame is made
>     >> invisible?
>
>     Gerd> The curren matrix of the root frame must always reflect what is on the
>     Gerd> screen, so that we can decide what to output to the terminal to make the
>     Gerd> terminal display what the desired matrix says. IOW, the parts of the
>     Gerd> root frame's current matrix that were overwritten don't really
>     Gerd> interest anymore.
>
> Donʼt tty menus already do this? Perhaps we could reuse them.

I think the tty menus work a bit different from what I'm thinking of. I
must admit that I haven't looked very closely, and I'm just assuming
that it works like what I've talked about with Eli a long time ago.

If that's the case, menus panes temporarily save away some part of the
matrix, and restore it when done with the eseentially modal interaction
with the menu. Soemthing like that. I think it's a pretty different use
case.

The mechanism could in principle be used to pop something up on ttys of
course, but that wouldn't help much with existing packages that use
child frames already, like Corfu or Posframe.