The World's Premier Listing Software
for Birders and Naturalists!
Celebrating 24 Years Serving Birders
and Naturalists around the World!
I know I should know better by now, but instinctively, when I want to print a report that I've generated, I try to press Ctrl-P, since that's pretty much standard in all of Windows. But in BD, as you know, it's mapped to a Petey function (to play instructions for the current window).
I'm using Windows 7 (still) and I'm pretty sure I don't have whatever voice thingie that was such an issue years and years ago that was deprecated out of newer Windows versions. So I get this run time error as soon as I press Ctrl-P (and the program just terminates on the spot).
I don't know whether you can trap for that error so that if a user presses those keys and there's no functional Petey to load, it simply doesn't do anything - but that would be helpful. Or if there's some other way to work around this when the keys are pressed in error, I'm okay with that too.
It's just that I know I will NEVER get used to "Alt-i" to print, given how many dozens of times a day I have to hit Ctrl-P. I'm not expecting you to change the key combos (though: is Petey still widely used enough to merit keeping the keystroke off-standard? I don't know which Windows versions have the component needed for him). But not crashing - that I could go for.
Is it the Print/Preview window where you are pressing the Ctrl+P? Only here - or other places also?
Fixed in Build 53 and later. Ctrl+P opens Petey. But now you don't get an error.