jcwren

No thanks. If you can't be bothered to document it, I can't be bothered wasting time looking at it.

It does come with the Root'n-Score-It kit, but it's disabled. If you rooted with a very old kit, or the original one that RASI is based on, it's enabled by default. One of the things RASI does on the second reboot is run through and set tweaks that make it better for scoring. Disabling Button Savior is one, another is locking the desktop, and a few other things like that.

Personally, I feel that if someone didn't check their scores, and they're incorrect, that's too bad, and the awards stand. I'm of the opinion that the incorrect scores are what should be uploaded to USPSA (and PractiScore), but for the purposes of submitting an activity report, they should be corrected. Just because someone had the wrong score in the system (but it's correct on paper) doesn't mean they should be penalized if it affects the classification percentage.

It's not a memory pressure issue, it's a failure to properly initialize some application crash reporting code. Re-entering the application while on certain screens seems to have something to do with it.

1.2.28 is beta, and not ready for prime-time. 1.2.27 is safe enough, IF you stay in the PractiScore app (e.g., don't go and use your camera or other programs while you're actively scoring. If you must, exit PractiScore cleanly first). There is a change log available. On the main screen, tap the build number. Some people report it takes a little fumbling around to get it to come up, but I've not encountered that.

The first problem is using EZWS 4.05. That version is deprecated. Update to 4.13. Importing the registration is done by going to Setup->Registration->Registration Import (far right tab, #6 of 6), then clicking the 'Import Registration' button. This will open a file selection dialog, where you can then select the 'reg.txt' file.

1.2.26, actually. http://rootnscoreit.com/

Ran a match on 8.3 this weekend, without any issues. The 8.3 upgrade doesn't *appear* to have any real impact on applications, like the change from 7.x to 8.x did. And WiFi stability seems to be slightly improved. Maybe PS support for the Apple Watch? We put Bluetooth tags on all the target stands, and as you stand next to the target, it brings up that target for scoring Although I still wish you could point the iPad or iPhone at the target, and have it score automatically. You'd have a recorded image of the target for arbitrations, plus a digital overlay, zoom and enhance...

I'm building a comprehensive list of match signup services. I'm hoping to have a features and pros/cons list when I'm done. These are the one I can remember so far this morning: squadsignup.com matchsignup.org shootnscoreit.com clubs.practiscore.com uspsa.com Any others?

Nice review, BJinPass. Looks promising, I think I'll buy one to play with. The only cost downside I see is the probable necessity of adding a case of some kind. Cases are the razor blade of the Schick business model. I have a couple NOOKs that have clearly been dropped, but not broken. Atlanta 3-Gun, who uses iPad Mini's, had someone drop one and it landed face down on a rock, and shattered the screen. The case was a LifeProof nud', which doesn't have the screen protector. I'm curious if that would have saved it or not. And these should work as well as any other capacitive touch system in the rain. Not having that raised bezel for the IR field that the NOOK has, there's no place for dust to collect, which is a definite plus. I'm not sure about the overheating issues, as we haven't run into that here in the GA summers (that I'm aware of). I do know that in direct sunlight, the touch system can get wonky because of the IR component in sunlight. Simply shading the screen with your body has been enough to solve that particular problem. The IR touch system is also why it doesn't work in a ziplock bag, or any case that puts something between your finger and the screen. Your finger looks like something the size of a quarter to the touch system, and can't cope with that. Generally it looks like you're touching random areas of the screen.

Next to trivial? Do tell, please. And you can import directly from EZWS? How does that work?

That would seem to indicate that people are exporting the match multiple times out of EzWinScore, posting to PractiScore after each export. I can't envision a valid use case for doing that.

I've updated the ezws2ps (EzWinScore to PractiScore) converter to version 1.0.4. Changes: Fixed an issue with multi-string times in scores not being correctly copied to the PractiScore .psc file when 'Include Scores' is checked. Added knowledge of classifier stages so when a classifier is present, the hits per target is known instead of inferred. This issue affected classifiers CM99-02, CM99-09 and CM99-63 not having the number of hits on each target defined correctly. Added support for target type. If target type is defined as Classic in EzWinScore, then 'Classic Targets (No B Zone)' is checked in PractiScore. Added support to force target NPMs to number of hits per target when scoring is fixed time (PractiScore iOS already did this internally, not sure about Android, but it's the "correct" way to define the stage). The page at http://www.tinymicros.com/wiki/ezws2ps has been updated. The updated version is available via the download link on that page, or directly from https://dl.dropbox.com/u/12548441/ezws2ps.zip The zip file has both the previous version and the current version. The previous version is named 'ezws2ps_103.exe' while the current version is named 'ezws2ps.exe'. If you find any issues, please let me know at jcwren@jcwren.com. You could post in this thread, but I'm not a big fan of using forums as a support system. Edited 2014-11-27 11:58 -- Changed 'defined as IPSC' to 'defined as Classic'. Thanks to Roger M. for catching this documentation error.

Yes. And Root'n-Score-It makes it trivially easy to do.

Eugene is right. I mentioned iPads above, that should actually be iPad Minis. Currently, even the oldest iPad Mini will run iOS 8.1, so PractiScore should be supported for a good while. But there will come a point when Apple stops supporting the older devices, and PractiScore may reach a point where it needs a more recent version of iOS to support new features (although right now, PS is supported on iOS versions as far back as 4.0, I believe).