Textual v6.0.0 broke pong #6095
TomJGooding
started this conversation in
General
Replies: 2 comments 5 replies
-
Not at my desk to try, but I think the only change that may be required is to explicitly set the Style on your segments. Ie self.rich_style if you want to pull the style from CSS. This change negates the need to do an expensive second processing of the segments. |
Beta Was this translation helpful? Give feedback.
4 replies
-
For what it's worth, in case you hadn't noticed yet, not only does your court get a little wonky, the whole display does. Try quitting with ctrl+c for example. ![]() |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Today I was just curious if my silly pong game built with Textual still actually worked. Apparently it does... until the latest Textual v6.0.0.
The CHANGELOG does warn of a breaking change:
But I'm struggling to understand how this would cause all the weird glitches and how to fix them! Perhaps there's something obvious I'm missing in #6057, but this does include quite a lot of changes.
Obviously this is just my silly experimental game, which is why I posted this as a discussion rather than creating an issue. But I wonder if the changes in the line API might have broken other application widgets too?
Beta Was this translation helpful? Give feedback.
All reactions