jcwren

Graham, I'm not sure what you mean by "flush out". Creating a new match in EZWS is trivial, so how would deleting all the competitors (if that's what you mean) help much?

I'd have to check, but it think it takes the first letter from each word in the division for the abbreviation. And you can edit those divisions, so perhaps you can add the word 'Pistol' in there to get that effect?

They're also handy for putting over the heads of small children who are crying in Walmart or restaurants.

BTW, for the rain, we either let the scorekeeper stand under the bay cover, and it's shouted out (sub-ideal), or use a 2-gallon zip lock baggie. Assuming you're normal (shout out to all my lefty friends!), hold the NOOK in your left hand, upright, with the ziplock bag over it, and insert right hand up into bag to tap screen. As you may already know, or may have learned the hard way, because of the touch system used on a NOOK, there is NO waterproof cover that will work with it. Basically, that small gap under the bezel around the screen that's a about 1/16" of an inch high is an infrared field. When you use anything between your finger and where you touch, it makes your finger look like it's about 6 times bigger than it is, and it gets confused. And if you use a baggie or something, and some of the plastic droops into the infrared field, it looks like a touch. If the NOOK isn't responding to touches, pressing harder won't help, and, in fact, at some point you can damage the screen. If a NOOK gets flakey on you, put it to sleep, take a paintbrush, and sweep out that gap around the bezel. Usually some dust or a small piece of trash will be lodged in there, and confuses it. If you hold it at the correct angle in sufficiently bright light, you can see under there and look for garbage. After doing the final sync from them at the range, I turn them off, and then sweep them. Every so often I'll use a screen wipe to clean the screens, not because it improves performance, but because knowing those splash marks on the screen are someone's sweat is icky.

Dropbox is being wonky. See if this link works. https://www.dropbox.com/s/6oiuys3spv530q4/Shooting_Order_4_Up.pdf If it doesn't, I'll put it in Google Docs or on my web server.

Yes, drag'n'drop squad re-ordering has been on the request list for a while. If you carry the device from stage to stage (which is something I don't advocate and none of the clubs in the area do), it would work well. But if you had to re-order at every stage, then it gets to be sort of pointless. What you can do is use something like this: https://www.dropbox.com/s/yna2bd5pbq3o15o/Shooting_Order_4_Up.pdf You fill it out once, and carry it from stage to stage. Edit: Also, how would it know who's a new shooter? There's no way it would be able to figure that out.

I did a little digging into the NOOK Android sources. To set the time, the NOOK is trying to hit an NTP server at 'time.barnesandnoble.com' or 'pool.ntp.org'. I can think of several ways it could be tricked, but they're probably a little convoluted for (as Bill likes to say) 'non-propeller heads'. If you're running a smart enough stand-alone router at your range (like something running RouterOS or OpenWRT), you could add a DNS server that would hijack those two addresses and point them back to the router, where an NTP server would be running. However, most routers don't have real-time clocks, so if you set the router's clock then cycle the power, the clock is going to be incorrect. If *all* the devices being used have the wrong time, there's not much of an issue. But if you're using a phone or tablet with cellular service, and the NTP server isn't set to the correct time, the phone/tablet and the NOOKs will be too far apart and won't sync (Practiscore doesn't permit the time to be more than 10 minutes apart between the syncer and syncee). Plus you don't really want to jack around the time on some devices, as it may cause any software with an expiration date to expire, along with security certificates. Probably the easiest way to handle this to install an Android program that actually allows the time to be set manually. This is near impossible on a non-root device, because setting the time is considered a VERY important operation, and mere users can cause many problems by jacking around the time. For rooted devices, like the NOOKs, this is much less of a problem. I'll poke around and see what I can find, and update the Root'n-Score-It rooting system with a utility that would allow manual time setting.

They'll try to get the time from whatever network they're connected to. If you watch the networking screen when you connect to an AP, it probes to see if it can find "the internet". If it does, and it can find a time server, it will set the time. If not, it won't. The ability to set or not set the time has no bearing on the NOOKs finding each other in Practiscore. It's only when two Practiscore devices are syncing that the time is actually an issue.

Supposedly the later versions of PS are a little more intelligent, and start looking at their IP - 32, then work up. It shouldn't really matter where the IP address is, as long as NOOK #1 doesn't get x.y.z.32 and NOOK #2 gets x.y.z.240. I prefer to configure our routers so that devices get the same address based on their MAC address. I put my iPad at 192.168.17.128, so if I enter the sync code manually, it's at 1180 (17 in hex is 11, 128 in hex is 80). This means I'm not getting a sync code like 1A7B, where I have to shift back and forth between the numbers and letters when entering it. I put the NOOKs at fixed addresses because sometimes when they're being difficult about syncing by tapping from the device list, I can enter the sync code. I know that NOOK #1 is at 1101, NOOK #2 at 1102, etc.

Create the stage with 1 paper target, 1 hit, with 1 non-penalty mike, then make sure no-shoots are enabled for the stage. It does mean you'll have to score that paper, so it's not quite as easy as an all-steel stage. But really, since there's no differentiation made in PS about no-shoots vs mikes vs penalties, I'd probably just treat it as a penalty.

Screw that! Anyone that needs an old version to MAKE A MATCH RUN SUCCESSFULLY, I'll provide a link to whatever build they want. For USPSA matches, we've had good luck with 1.2.15. Some people still prefer 1.2.12. But if you want a complete list, check here. I generally recommend never updating in the week before the match. And after an update, set up a 3 shooter/3 stage match for testing, and make sure you can create a match, add shooters and stages, add/edit scores, and sync. I also suggest keeping the latest and previous .apk files on hand at a match, in case you do need to reinstall. Note that if you uninstall PractiScore, you will lose ALL your match databases and shooter history. If you're just reinstalling, that's not an issue. We had that happen at Area 6, where we couldn't delete the match (screen flickered black, then returned to the main menu). We ended up having to uninstall and reinstall the same version of PS on all the NOOKs, which fixed it. Afterwards, I couldn't recreate the problem, and since it wasn't the bleeding edge version, I figured no one would be interested in the problem anyway.

Any how the hell exactly is this a "problem of your own backyard"? When you release a version, it's BETA. Because you, self admittedly, only test "things that interest you". So we find a problem, and your solution is "Here, replace your version that you know has a certain problem set with a version that's completely untested, and may or may not fix your problem, and may or may not introduce additional problems that you'll only discover in the middle of a match"? I don't know where you learned about development, testing and release methodologies, BUT THAT'S UNACCEPTABLE. You're releasing software that people are counting on to work, and to provide some modicum of support when something goes wrong. Saying in the middle of a 400 shooter x 12 stage match "Oh, that? Well, you're running one release level down, so I'm not interested in any problems you have. Upgrade to the latest version, and see if it still does that." just does NOT CUT IT. Hey, I have an idea. Let's find the manufacturer of your car, and have them apply the same philosophy. Maybe after you smack a phone pole at 100kph because the engine shutdown in a curve because some developer at Toyota|Ford|GM|Subaru just didn't feel like handling a corner case when the accelerometer values are exactly 0.125 G's, and said "Screw it, just reboot the ECM." So here's the short-form version: No one trusts your releases because of your (lack of) testing philosophy, releasing three versions in 24 hours, and the expectation that there WILL be problems in things that used to work. PractiScore users have the expectation the software will work. Oh, it's free, you say? SO WHAT? I can point to thousands of free programs that are solid, quality software. The expectation is that it will be *reasonably* stable. Will they find odd use cases? Sure. Should they basic functionality like syncing to crash? No. So what do people do? They run versions where the problems are (mostly) known, and save the bleeding edge versions for when they can risk a match going to hell because of some failure or another. With the wide-spread and ever-increasing adoption of PractiScore, you need to realize that you're representing a company that has expectations of USPSA and other shooting disciplines adopting it as the primary scoring method, and that ultimately, this is an income source for said company. Every time you release a version that breaks things that used to work, don't even bother with superficial testing, decide that a 5 word change log is acceptable, and don't indicate potential issues in that release, you're damaging that company's credibility. When that credibility gets low enough, people will abandon PractiScore for other systems (think Wirtex, or maybe an open-source solution). So before you go shooting off with "Not the current version, not interested.", 5 word change logs, a release-of-the-day, and whine about no one is helping you test, I suggest you keep in mind what I wrote above.

Download the .apk file from http://practiscore.com/android.php?version=latest, put it on an SD card, install the SD card in the NOOK, use the file browser that should be present in your rooting kit to navigate to the SD card, click on the .apk file. You may need to uninstall the old one first. There was some revision level where it wouldn't install over it, and it had to be manually removed. You can manually remove it by pressing and holding on the Practiscore icon on the desktop and select 'Uninstall' from the little menu that pops up.

Normally it takes me about 10-15 minutes per, but you can pipeline them, which makes it go pretty quick.

10, maybe 15, seconds. What's the screen showing?

You're tapping on the words on the screen, instead of pressing the ridges on the side. The latest version of RASI indicates that on the screen, I believe.

Sure, XAMPP is fine if you want a 125MB+ of full-blown Apache web server with PHP and all the trimmings. But for just serving a few files, nginix (at 784K for the installer) is pretty darn small.

Well, that's the thing. You don't actually open it from >within< Practiscore, you try to open in email, Dropbox, the browser, whatever. Applications, like Practiscore, register themselves as delegates for that type of file. So the browser, email client, Dropbox go "I dunno what to do with this, but I've got a delegate that does. Would you like to open it in Practiscore?" You say "Yes. Yes, I *would* like to open it in Practiscore, dammit!", and it hands the data to the delegate. I'm not sure, since I'm not an iOS developer, but I think it's because from a user standpoint, named storage as we know it (C:\FOO, /home/users/me, or "My SD card") doesn't exist in iOS.

Yes, although it's not *quite* as straight-forward. You can: 1) Send yourself an email with the .psc file attached, and open it from the email program 2) Put the .psc file on a web server, browse to it (in Safari, Chrome doesn't know what to open it with), and open it 3) Use iTunes (MAJOR PITA, don't suggest this at all) 4) Use an Android device, then sync the iDevice against the Android device. At a match, I have the free, lightweight nginix web server installed on a laptop. The laptop and the iDevice are on a hot spot, or the range LAN. I copy the .psc file to the html folder of nginix, and then browse to the laptop with the iDevice. Option 1 requires internet access.

Except some of the instructions can be a bit cryptic. http://www.rootnscoreit.com/tourist.html Hey, I can't help it if I have the attention span of a ferret on meth! I keep *meaning* to finish it. I just get distracted by shiny... HEY LOOK! A SQUIRREL!

2014/04/10 - PractiScore 1.2.15 released 2014/04/11 - Area 6 starts I'm sure any issues could have been patched before our "big match", and 12 primary, along with 12 back-up NOOKs could have all been updated. At a range with no internet access, and extremely limited cellular coverage. That would have been an excellent plan. *I* don't go into major matches with beta software. I don't even do that at local matches, unless I have a full fleet of backup devices with a version I know the characteristics of.

Bill may be able to confirm this with an ODBC connection to the database, but I'm guessing that the error indicates the field for the time overflowed the width of the field type in the match database. Not sure if EZWS stores times as actual floats or integers * 100, but that would definitely overflow any 32-bit integer field.

The version is on the main menu screen, under the 'Change Match' button. When registering competitors for the match, under the 'Added Shooter #' button, there are two other buttons, labeled 'Edit Divisions' and 'Edit Classes'. I would suspect that someone was mucking around in there at some point, and inadvertently disabled 'Production' in divisions, and 'A' in classes. Tactical, for some Dog unknown reason, is an option in divisions, and is always available, even though it's not a recognized USPSA pistol division (this is also true in EZWinScore, it's not a PractiScore bug).

You can put a PIN on a match the first time it's uploaded. Subsequent uploads require the same PIN be used. At least, that's the theory. I've never actually tried it. Also, while possible, there's little value in doing that. The *real* results are the one in the original device, and the results that are uploaded to USPSA. Results on PractiScore.com are for entertainment purposes only.

*crickets*