Is this a bug?
-
Johno
It's simply too difficult to figure out how to check if this is already a reported bug, but I've recently noticed a problem when using the "next track" "play/pause" shortcuts. When you have the Music Store open in a separate window (which I've been experimenting with lately; and I'm using iT7), everything works correctly as long as iTunes is the frontmost app. As soon as you switch to another app, even when making sure iT is displaying the store in it's frontmost window when you switch, the shortcuts don't work correctly. If you hit the "next track" then the "play/pause" shortcuts, it works on the window that's in the *background* in iTunes!
Can someone confirm this behavior, or is it a known issue (Wincent?)??
Thanks, John
-
Johno
I just discovered it works as it should *if* a track is playing in the store when you switch, *and* if you keep hitting the "next track" shortcut before the current track sample finishes playing... If you let the track sample finish, and therefore it stops playing, and you try and switch to, and play, the next track, it will lose focus and play what is selected in the background window. Weird, eh?
-
Greg Hurrell
Quote: It's simply too difficult to figure out how to check if this is already a reported bug
To check if a bug has already been reported, go to Bugzilla and in the text field that's labelled, "Enter a feature request/bug number or some search terms:", you enter some search terms. For example, if you enter the terms "music store" (no quotes) you'll get this relatively short list of bug reports/feature requests. It appears that no one else has brought up your issue.
Now, to respond to your comments:
The shortcuts merely send "playpause" and "next track" and "previous track" events. I think you'll be able to confirm that the behaviour is the same no matter which application sends those events. Try the following scripts in the AppleScript Script Editor application:
Code:tell application "iTunes" to playpause
And:
Code:tell application "iTunes" to next track
And:
Code:tell application "iTunes" to previous track
Basically you should see that the behaviour is the same sending those events from the Script Editor as it is when triggering those events via hot keys (or menu bar control buttons etc) in Synergy.
If you find any discrepancies between Synergy's behaviour and that of the Script Editor then I'll be pretty surprised, and stumped as to what the cause might be! It's the same event after all!
-
Johno
Okay, so you're saying it's an AppleScript bug? It's definitely a bug. It doesn't make any sense that the background window would get focus if a track isn't be previewed, but not if one is being previewed! I'm guessing it's a bug in iTunes 7, eh?
And yes, of course I understand how to search for an existing bug report, it's just that this particular issue doesn't have a short, simple description to enter in the search field. I didn't think to try "music store" though...
Thanks for the reply, regardless.
-
Greg Hurrell
Quote: Okay, so you're saying it's an AppleScript bug? It's definitely a bug.
To be clear, if the behaviour is weird it's not a bug in AppleScript itself, but in iTunes and the way it responds to AppleScripts (Apple Events).
When you see this kind of weird behaviour you can rule out that it might be a bug in Synergy by doing some experiments from the Script Editor. If you're able to reproduce the behaviour from within the Script Editor then you know the problem actually lies within iTunes and the way in which it responds to events.
Sometimes the bug is very clear because you send a simple command like "playpause" and iTunes responds with bizarre and inconsistent behaviour. That's when it's time to file a bug report with Apple (http://bugreporter.apple.com/, at a minimum requires free "Online" ADC membership), or send them feedback.
Quote: It doesn't make any sense that the background window would get focus if a track isn't be previewed, but not if one is being previewed! I'm guessing it's a bug in iTunes 7, eh?
I really don't know. You can file a bug report or feedback with Apple and they might tell you that that's intended behaviour, but there's only one way to find out...
Reply
This topic is now closed.