code monkeying
i decided to have a look at wxpython today for about the 50 billionth time. this is because i am yet again thinking about a gui for schnolgo. i decided i'd go through it all one step at a time, through a tutorial like a good boy.
the big hitch was that even the simplest scripts were failing inexplicably. after tearing my hair out a bit and having equal frustrations with pygtk, i finally stumbled upon the source of my problems: scite. i couldn't possibly tell you WHY, but scite was fucking with gui programs when they were run using it. the solution: run them in idle. i wish i knew why it was working this way, because it's a bit disconcerting to me that scite might be causing unexpected runtime behavior...
but anyway, the upshot of this is that wxpython is now working correctly and i intend to keep going with it. once uni lets up, this may be one of my major focus areas for a bit. because i have a clear plan of attack with "that hat wilted my lungs" now, things should get rolling with schnolgo a bit more.
i'm finding that schnolgo gets worked on as i put it through its paces. i've used it a couple times for assignments this semester and it's gotten a lot of bug fixes and a few new features as a result. "that hat wilted my lungs" is meant to really put schnolgo to the test, so hopefully this will be good for music and good for code. a round of good for everybody, on the house!
the big hitch was that even the simplest scripts were failing inexplicably. after tearing my hair out a bit and having equal frustrations with pygtk, i finally stumbled upon the source of my problems: scite. i couldn't possibly tell you WHY, but scite was fucking with gui programs when they were run using it. the solution: run them in idle. i wish i knew why it was working this way, because it's a bit disconcerting to me that scite might be causing unexpected runtime behavior...
but anyway, the upshot of this is that wxpython is now working correctly and i intend to keep going with it. once uni lets up, this may be one of my major focus areas for a bit. because i have a clear plan of attack with "that hat wilted my lungs" now, things should get rolling with schnolgo a bit more.
i'm finding that schnolgo gets worked on as i put it through its paces. i've used it a couple times for assignments this semester and it's gotten a lot of bug fixes and a few new features as a result. "that hat wilted my lungs" is meant to really put schnolgo to the test, so hopefully this will be good for music and good for code. a round of good for everybody, on the house!