Pallet Window Resize Bug

[gaxolotl]

Have you checked closed issues? Yes!

Have you checked against the most recent version of Textual? Yes!

How to replicate this bug:

python -m textual
*resize terminal window*
^p (Control+p)

[github-actions]

Thank you for your issue. Give us a little time to review it.

PS. You might want to check the FAQ if you haven't done so already.

This is an automated reply, generated by FAQtory

[TomJGooding]

It will be helpful if you run the following command and paste the results:

textual diagnose

If you don't have the textual command on your path, you may have forgotten to install the textual-dev package.

[gaxolotl]

It will be helpful if you run the following command and paste the results:

textual diagnose

If you don't have the textual command on your path, you may have forgotten to install the textual-dev package.

Textual Diagnostics

Versions

Name	Value
Textual	1.0.0
Rich	13.9.4

Python

Name	Value
Version	3.12.8
Implementation	CPython
Compiler	MSC v.1942 64 bit (AMD64)
Executable	C:\Users\acer\AppData\Local\Programs\Python\Python312\python.exe

Operating System

Name	Value
System	Windows
Release	11
Version	10.0.22631

Terminal

Name	Value
Terminal Application	Unknown
TERM	Not set
COLORTERM	Not set
FORCE_COLOR	Not set
NO_COLOR	Not set

Rich Console options

Name	Value
size	width=120, height=30
legacy_windows	False
min_width	1
max_width	120
is_terminal	True
encoding	utf-8
max_height	30
justify	None
overflow	None
no_wrap	False
highlight	None
markup	None
height	None

[TomJGooding]

Very strange, I can't reproduce this. What version of Windows Terminal are you using? Does Ctrl+p do anything in your terminal when not running Textual?

[gaxolotl]

Very strange, I can't reproduce this. What version of Windows Terminal are you using? Does Ctrl+p do anything in your terminal when not running Textual?

No Ctrl+p doesnt do anything when textural is closed. My Windows terminal version is 1.21.3231.0. It seems to have been fixed after restarting Windows.

[TomJGooding]

Glad restarting seems to have fixed it. I wonder if your Windows Terminal was updated and this might have been some bug in an earlier version...!