Update 3.0.6 has now been released

3.0.6 Release Notes

ADDED – Pain Map Painter – The Eraser tool is back!
ADDED – Pain Map Painter – Drawing path smoothing option. Now enabled by default, this option will reduce the number of points contained within the drawn path while still maintaining the shape of the desired segment. This helps reduce database space and processing time. (Available only on devices running iOS 4.3 and above)
ADDED – Pain Map Painter – Path Overlap Detection. Now enabled by default, this option will scan your pain map to detect any paths that are fully covered by one or more other paths in the drawing. These extraneous paths are then removed to help reduce database space and processing time requirements.
ADDED – JPEG Compression option in Pain Map Painter Tracker. Now enabled by default, the JPEG compression feature greatly reduces the size of the HTML output reports. Up to a 90% reduction in file size has been seen when using the new default setting.
ADDED – Help Confirmation – New users will now get a second pop-up asking if they would like to continue seeing the automatic help screens on each new screen they explore. This has no impact on current users.
FIXED – Comment Tracker – 3.0.5 introduced a bug where a blank comment tracker in an entry would hang the process of generating report data. This is now fixed.
FIXED – Database opening process has been modified to better support schema changes related to software updates
FIXED – Some Diary Entry save bugs

For those of you that want additional commentary on the enhancements, here it is. Enjoy…

  • ADDED – Pain Map Painter – The Eraser tool is back!
    • We had many requests to bring this tool back into the Pain Map Painter, and now we have. The eraser tool enables you to remove any portion of previously painted lines on the pain map model.
  • ADDED – Pain Map Painter – Drawing path smoothing option. Now enabled by default, this option will reduce the number of points contained within the drawn path while still maintaining the shape of the desired segment. This helps reduce database space and processing time. (Available only on devices running iOS 4.3 and above)
    • You probably won’t notice this tool too much as it is designed to reduce the amount of data collected for your painted path, while not affecting the actual shape of the path itself. As an example, a typical painting stroke on the pain map model might consist of 20-30 data points (depending on how many turns and twists you make and how long your finger is left on the screen). The smoothing can often reduce this to 10-15 points which cuts the data in half. This helps both in terms of database storage space and processing time.
    • If you are creating very intricate pain map drawings and notice that the smoothing function is affecting your desired path shapes, you can generally overcome this issue by either using a smaller brush size and/or slowing your finger movement when making curved path segments. Both techniques allow the device to collect more accurate point information that will not be as effected by the smoothing function.
  • ADDED – Pain Map Painter – Path Overlap Detection. Now enabled by default, this option will scan your pain map to detect any paths that are fully covered by one or more other paths in the drawing. These extraneous paths are then removed to help reduce database space and processing time requirements.
    • You will notice this feature when you go to save the Pain Map drawing. You’ll see a progress indicator pop up indicating that the app is Simplifying Path Data. It will do this for both the front and back drawings.
    • Why is this a good thing? We have found that many users were copying their last Pain Map images into a new entry to use as a starting point. Although this is fine in itself, they were often painting over the previous drawing with new paths which added complexity with each time this was done. In some complex pain maps, we saw several hundred paths in a single drawing. This had a major impact on database storage  and processing speed.
    • With the new overlap detection, we are now able to determine if a path is completely covered by other paths. If it is, then it can be removed from the drawing without affecting the final pain map composition. This is a huge optimization when folks are copying their pain maps forward each time. For example, in testing we saw a drawing with more than 700 paths go down to 70 paths after optimization without any impact on the final composition.
  • ADDED – JPEG Compression option in Pain Map Painter Tracker. Now enabled by default, the JPEG compression feature greatly reduces the size of the HTML output reports. Up to a 90% reduction in file size has been seen when using the new default setting.
    • This is another big optimization for our users. Because our reports are very graphics oriented – graphs, pain map compositions, etc, we were seeing HTML file sizes growing very large when some reports were being generated. We have now switched to a JPEG format for the internal graphics which allows for significant compression ratios without much impact on the final images. Because of this, reports that might have become too big to easily email or exchange online have now become quite manageable in size.
  • ADDED – Help Confirmation – New users will now get a second pop-up asking if they would like to continue seeing the automatic help screens on each new screen they explore. This has no impact on current users.
    • When new users begin using Chronic Pain Tracker, we give them the option of seeing a help screen alert describing each new area of the app the venture into. We wanted to make sure this didn’t become too confusing for users, so we give them a second chance to either keep the help screens enabled or disable them so they can explore on their own.
    • We still maintain the option of simply shaking the device whenever you need a help screen to appear.
  • FIXEDComment Tracker Bug – 3.0.5 introduced a bug where a blank comment tracker in an entry would hang the process of generating report data. This is now fixed.
    • This was a bug that slipped by us in the last version. If you selected the Comment Tracker for an entry but then didn’t put any text into the Comment box, and then tried to run a report that included that diary entry, the report process would crash. This is now corrected and we apologize to those of you that had reports crashing because of this.
  • FIXED – Database opening process has been modified to better support schema changes related to software updates
    • As we continue to grow the application, the database schema also needs to change from release to release. This requires the app to update the user’s Diary database to the new schema after they update the software. These enhancements are to help improve the efficiency and stability of that process. It is something you shouldn’t notice as it is all behind the scenes.
  • FIXED – Some Diary Entry save bugs
4 replies
    • ChronicStim says:

      Hi Dbacks.

      Thanks for your question about the availability of a native iPad version of Chronic Pain Tracker. This is an offering/feature that we recognize as highly desired by our users and potential customers, so it is on our priority list.

      We are currently working on what will be a significant new upgrade version (v3.1) that will include:
      * Several new Trackers and associated features
      * Paginated PDF report output option (in addition to the current HTML format)
      * Significant improvements around memory usage and overall app stability

      Once that version has been completed, we will be turning our full attention towards a native iPad version (probably called v3.2). Although we can’t be certain about the timeframe yet, we would like to begin beta testing this version in May with a June/July release date.

      I hope this answers your question. If you have others, please let us know.

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply