Using pick.pick within curses.wrapper() breaks input about pick HOT 7 CLOSED

I don't know if this relates to / is same as #83

from pick.

For completeness, I also tested on my raspberry pi and it was reproducible:

$ pip list | grep pick
pick        2.1.0
$ python -V
Python 3.10.7
$ uname -a
Linux possum 5.15.61-v7l+ #1579 SMP Fri Aug 26 11:13:03 BST 2022 armv7l GNU/Linux
$ cat /etc/debian_version
11.5

from pick.

Thanks for your report, I believe the problem is you're creating nested curses screens: pick itself is also running inside a curses.wrapper call.

from pick.

Perhaps pick can accept an optional screen parameter, if provided, use it instead of creating a new curses screen.

from pick.

That would make sense as it'd mean pick had done all the teardown type operations.

(and I've seen similar with a different menu module too)

I'd be happy to create a fork and give that a try (and make a PR if it works) if you'd like

from pick.

Sure! Go ahead

from pick.

That seems to fix it, at least in my limited use case (and shouldn't break your existing code path)

from pick.