AirPrint of Scorecard in 3.0

[FTMSupport]

With v3.0 on iOS, we added the AirPrint option to Scorecards viewed from the Game Info screen. Anyone had a chance to try that out?

[CoachJoe]

FTM,
Works great! I didn't know it was there. Thanks for the info.

[randkos3]

Haven't tried it . . . what does it do?

[OhioTex]

AirPrint is a feature apple added to their iOS operating system in iOS 4.x to enable remote printing direcly from iOS devices to airprint enabled printers by simply taping the "square with arrow out icon" that appears on menu bar in some applications (like safari). This sounds more useful than has been for me in practice, because very few printers and traditional home network setups are nt AirPrint enabled due to the protocols apple choose to implement.

(perhaps coachjoe or others, can elaborate here on how to make AirPrint more useable, what kind of set up works b/c my tcp/ip networked printer, nor USB connected printers seem to show up in AirPrint, and I did not want to run my desktop all the time to print through it with a third party app)

As to iscore, FTM added/enabled the AirPrint function in v 3.0 of iScore for iOS. We now get the "arrow out" icon in the upper right corner of the screen when viewing scorecard from game info screen. If you have AirPrint enabled printers, you can easily print your scorecard without emailing first. (I applaud FTM for starting down this path, but I have not seen the AirPrint icon on any other screens in score. that said, given the limited airprint and apples limited support for older printers/traditional home network set ups, I am not in a rush to see more iScore screens enabled to AirPrint. IMHO

[FTMSupport]

Did this for scorecard in the hopes that for leagues that require a paper scorecard with an umpire signature, this gives the option to print one at the field if there is a portable AirPrint compatible printer.

[CoachJoe]

For anyone who wishes, the following programs allow you to access you PC Printers with your iOS 4 devices with AirPrint

AirPrint Installer for Windows 7/Vista/XP (32-bit/64-bit)
http://jaxov.com/2010/11/download-airpr ... -xp-vista/" onclick="window.open(this.href);return false;

AirPrint iOS 4.2.1 Hack for Windows users
*** These sites are in German (Use Google to Translate)
Program description: http://www.macerkopf.de/airprint-ios-4- ... 02481.html" onclick="window.open(this.href);return false;
Link to Downloads: http://iblueray.de/viewtopic.php?f=22&t ... fceffcc05c" onclick="window.open(this.href);return false;

You will need a little computer knowledge to install and run. Make sure you read the install instruction!
I have not come across any problems or virus in these sites and they have both worked for me, but as with any software downloads please have an active AV program.

[FTMSupport]

Thanks CoachJoe.

[CreigN]

I tried this the other day when I saw the AirPrint graphic and it worked great. Only one small discrepancy that we found.

From within iScore on the iPad, looking at the Game Manager>Game Info>Scorebook (for either team), it shows up on the iPad screen with Batter #'s and non-scored cells have a grey tint. However, when the Scorecard is printed using AirPrint, the large Batter #'s and the greyed out cells do not print. This also happens from the iPad when I use Safari to access iscorebaseball.com/TEAMNAME and print the Scorecard.

The exact opposite is true from my Team website at iscorebaseball.com/TEAMNAME accessed from my laptop. When I click 'Scorecard' on my Team's 'Games' page, it downloads the PDF and opens the Scorecard in Preview. The Scorecard does not show the large Batter #'s nor the greyed out cells on the MacBook Pro screen, but both of these print beautifully on the hard copy.

Both of these printing jobs were done on the same network tot he same printer.

Doesn't bother us, but we do like the large Batter #'s next to the players names and the greyed out cells on the Scorecard.

[FTMSupport]

It seems likely that the PDF viewer / print driver would be the issue in these cases. The "rendering" of the PDF to screen and the printing are both done from the same PDF file --- we do not generate different code for each. So we would have to guess it is the way the PDF viewer is handling the code. On a computer, you can try updating your Adobe PDF viewer to see if that helps. Another possibility is a combination of the PDF viewer with the printer (or options for the printer) selected.