[05:17] <patrickb> Re How things are generally working (assuming implied context of using T-W). Good I'd say. I've been mostly improving the debugserver the last months. Now that it seems to be working reliably, I'm now back at filling in the remaining missing bits of the UI.

[05:19] <patrickb> There's the missing bits here and there in T-W, but the UI itself is working reliably within it's limits.

[05:20] <patrickb> Sometimes error message could be more telling. Two incidents come to mind.

[05:23] <patrickb> When changing the layout, sometimes it says that an element breaches it's min/max constraints. It's non obvious which element is breaching, nor why it's limited to that size. For me it's mostly been trial and error on the most recent changes. Once fixed it's most of the time understandable, what the issue was.

[05:29] <patrickb> When changing the contents of a RichText Widget, one needs to call update-scroll-maxes. When not doing so, the error messages of set-x/y-scroll, set-cursor-pos and ensure-y-span-visible are not helpful to find the root cause.

[19:54] <japhb> Ah, those are good points.  Definitely file issues for those.  :-)

[19:54] <japhb> Though I will say the bad handling of layout errors (the first incident you mention) has been on my radar.

[19:57] <japhb> I was trying out someone else's TUI tool (not Raku-based; I forget the implementation language), and when resized too small it would replace the laid out UI with a simple message that said "This UI requires a minimum size of X*Y.  The current size is W*Z."  I really liked that way of handling it.

[19:57] <japhb> I've got a rough idea how to accomplish that in T-W's model, so maybe that's one worth tackling the next time I get some hacking hours.

[19:59] <japhb> The other thing you've mentioned wanting that has been on my mind is pop-ups/hover windows.  Proper layered painting should be working at this point, but there's no (simple) way to create what we'd call a tooltip or a modal box.