Commit graph

10 commits

Author SHA1 Message Date
mlncn
02cf152ecb Add crucial destroy() otherwise window stays there, nonresponsive, until script killed
i just hadn't noticed in the standalone script because the script did in fact end, but when called
from pomodoroprompt.py itself, which keeps running, the window hung, froze, freezed, broke, was a
problem.  And i thought it was somehow because it was called from another file or program but really
it was just this missing destroy that is somehow not in many examples.
2021-05-02 15:09:19 -04:00
mlncn
b1c36fd82b Add a functional function to see if we can isolate problem with including
Maybe it's the object?
2021-05-02 12:59:26 -04:00
mlncn
494b454c45 Take prompt and set title if prompt provided 2021-05-02 12:58:52 -04:00
mlncn
9a8be46f8a Bring triggers to actually show window into main function
Well, init function.  Point is our calling program shouldn't have to think
about windows showing all or GTK main anything!

The main trick mentioned last commit wasn't this call to Gtk.main() but rather
the if __name__ == '__main__' bit.
2021-05-02 12:11:53 -04:00
mlncn
596bf7e6a0 Prepare for being a helper script and stop messing with it
The 'main' trick is cool, all that stuff within it only happens if it's called
directly.
2021-05-02 12:04:02 -04:00
mlncn
d4edd49862 Provide a reset button where, if there was text to start out with, in case it was accidentally overwritten 2021-05-02 11:32:18 -04:00
mlncn
67ff99afe1 Demonstration of how to get the value as we don't want actual saving done in this script 2021-05-02 11:19:36 -04:00
mlncn
5792d1e6a5 Add an OK button! 2021-05-01 14:44:20 -04:00
mlncn
0def577866 Here we can actually retrieve what is written on enter 2021-05-01 13:13:12 -04:00
mlncn
d1bc9d62fa Start a file for refactoring prompts to bypass zenipy, use Gtk 2021-05-01 12:48:32 -04:00