KnitCounter 4.2.3

One more fix for a problem I see in the logs a lot:

4.2.3 + fix for where you’ve linked your counters into a loop.  This now better detects and won’t increment a counter again after incrementing previously.

– tink will still cause it to crash if you’ve got a circular reference.  Please avoid this.

And a request, if you are having issues with the app, please contact me.  It is so disheartening to read comments on the Market that the app is buggy, doesn’t do this or that, etc.  Also, if you have the option when the app crashs to send the report to the developer, please do so.  Without those and direct contact, I won’t have the ability to make things better.  The last couple of releases are a result of the error reports from crashes.  I was able to tell from them what happened and could address.

Thank you.

This entry was posted in Knit Counter. Bookmark the permalink.

One Response to KnitCounter 4.2.3

  1. Jill says:

    I purchased your app a few days ago, and so far so good. However, I wonder if there’s a manual somewhere to explain how to do a few things that I haven’t figured out. I’ve managed to set repeats that are linked to row numbers, but can’t seem to “get” how to obtain the number of stitches I should have after a given number of increases. As an example, I’m currently knitting a scarf that has 2 increases in one row and 4 in the next, repeated 33 times. Is there a way to show the number of stitches I should have at any given point in the work? Thank you!

Leave a Reply

Your email address will not be published. Required fields are marked *


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>