There are three ways to close bkrpr. There's a button on the window, an option in the file menu and a key combination (C-q). The latter two exit just fine. The first results in the following and crash. It *does* effectively close the app, but obviously this isn't what's intended. I imagine fixing this is a few minutes work, but I haven't looked at all.
vasile@brennan:~/personal/bkrpr$ ./bkrpr.py
Starting GUI. Run bkrpr --help for commandline operation.
New done
Opening /home/vasile/personal/bkrpr/Tears_of_My_Soul
Loaded /home/vasile/personal/bkrpr/Tears_of_My_Soul
Traceback (most recent call last):
File "/home/vasile/personal/bkrpr/GUI/notebook.py", line 408, in _destroy_cb
self.parent.start.update(M)
AttributeError: 'NoneType' object has no attribute 'start'
Traceback (most recent call last):
File "/home/vasile/personal/bkrpr/GUI/notebook.py", line 408, in _destroy_cb
self.parent.start.update(M)
AttributeError: 'NoneType' object has no attribute 'start'
Traceback (most recent call last):
File "/home/vasile/personal/bkrpr/GUI/notebook.py", line 408, in _destroy_cb
self.parent.start.update(M)
AttributeError: 'NoneType' object has no attribute 'start'
Traceback (most recent call last):
File "/home/vasile/personal/bkrpr/GUI/notebook.py", line 408, in _destroy_cb
self.parent.start.update(M)
AttributeError: 'NoneType' object has no attribute 'start'
The exit functions should cancel any existing processing before they shut down the app. Adding that functionality takes this out of the category of quick bugs.