I see, thanks. This is basically a rounding error that results from integer values being used instead of floats. I intend to fix this, but you can also work around this issue pretty easily by explicitly using float coordinates, i.e. <code>center.x - 64.0</code> instead of <code>center.x - 64</code> etc. Just add a <code>.0</code> to your coordinates for now and it should work.
Yes, edit the link, remove your suggestion, then I got no problem;-)
Wow,read (a lot ) of yor workflow, what a bloody beginner I am, seeing your examples of using Pythonista in so many different ways!!
Result: I at least need a lot of explanations, e.g. the Application stuff possible in Pythonista and a lot more. @kingtut, willtry to dowload some of your examples on a PC, did not try downloading on my Ipad (imposible I think)
On the iPad, you can tap the [+] button at the top while you're editing to get a popover with these things (images, sound effects, colors...). On the iPhone, there is an "Insert..." item in the copy/paste menu (when you don't have text selected) that does the same thing.
I plan to overhaul the canvas module to work better with others (mostly PIL and scene). Basically, I want canvas to work more like PIL, i.e. allow multiple canvasses that can be drawn to and saved as images etc. I can't say yet when I'll get to that, I'm pretty busy with some other things at the moment, but it's on my radar.
I encountered the same problem. After struggling to get either datetime.strptime or time.strptime to work consistently without error I gave up and downloaded dateutil.
The dateutil module also has the benefit that you shouldn't need to work out the format string. Assuming that dateutil supports your date format your example code could be written as:
from dateutil import parser
obstimedt = parser.parse(obstime)
If you're interested in using dateutil then you can download it using this script: https://gist.github.com/4026516 (note that this script creates a 'temp' and a 'dateutil' directory alongside your Pythonista scripts - although the 'temp' directory gets deleted after download).
Another little thing would be if gravity() used Core Motion so that it also included data from the gyroscope and compass. This could potentially be pretty powerful a way of playing with the built in sensors.
Maybe allow users to specify return types in docstrings and parse those? Like this:
Gives the current position of the ball.
That way, the difficulty of parsing a dynamically typed language is lessened, and users can still benefit from the added code completion feature. If they dont specify the @returns thing, then there will just be no code completion for it.