-
The example code returns with error, when selecting a file to display: caused by line 69 The following solution works for me: |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
How exactly are you running the I'm not seeing this error after running the example within my clone of Textual. |
Beta Was this translation helpful? Give feedback.
-
Textual DiagnosticsVersions
Python
Operating System
Terminal |
Beta Was this translation helpful? Give feedback.
-
I've checked your most current branch. Your code has not changed. As I've mentioned in my original message, a change from event.path (which returns a path object) to event.path.name (returning a correct string object) was my working solution. Thanks for your efforts, mates. |
Beta Was this translation helpful? Give feedback.
-
Dear Dave,
thanks for your suggestion. I just recently came across your library and installed a version via PIP. So I am just earlier student from your work.
But growing up with a terminal in the late seventies, I am very impressed with what your team has achieved.
Warmly,
Rainer
… On 05/27/2023 11:51 AM EEST Dave Pearson ***@***.***> wrote:
There have been changes to the handling of different types when it comes to setting the application title (#2532), hence my suggestion that it would be worth testing with the latest release of Textual. At a quick glance it's not obvious what the cause of the problem is, but given neither Tom nor I can recreate it with the current release of Textual it's a good idea to ensure we're all looking at the same thing.
—
Reply to this email directly, view it on GitHub (#2664 (reply in thread)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AIUZNI6DX2Q4CCEI6XEUA7DXIG6AFANCNFSM6AAAAAAYRBSM3I).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
I've checked your most current branch. Your code has not changed. As I've mentioned in my original message, a change from event.path (which returns a path object) to event.path.name (returning a correct string object) was my working solution. Thanks for your efforts, mates.