Loading Profile...
Textcast hangs on opening iTunes
If iTunes is not already running, hitting "sync to iTunes" brings up the modal dialog that says "iTunes is not running...Lanuching iTunes...".
iTunes then launches in the background (but does not come forward, if that makes sense) and Textcast just keeps spinning saying it's launching iTunes.
I can click on iTunes on the dock and bring it forward, everything is working as expected, Textcast is just stuck launching it.
the only way to get out of this is to force-quit the app.
I'm on a powerbook, 1.67 GHz ppc G4, 1.5gb ram, leopard 10.5.6
iTunes then launches in the background (but does not come forward, if that makes sense) and Textcast just keeps spinning saying it's launching iTunes.
I can click on iTunes on the dock and bring it forward, everything is working as expected, Textcast is just stuck launching it.
the only way to get out of this is to force-quit the app.
I'm on a powerbook, 1.67 GHz ppc G4, 1.5gb ram, leopard 10.5.6
I’m confident
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?HI Clint,
It sounds to me like Textcast isn't receiving or isn't correctly processing the NSWorkspaceDidLaunchApplicationNotification notification that's sent when an application (in this case, iTunes) is launched or iTunes isn't responding to the `ping` AppleEvent we send it to ensure it Really, Truly Is Responsive. Or it could be some race condition.
Is the problem reproducible? That would be awesome. -
Inappropriate?Hrm... yeah. I've been able to reproduce this on my wife's PowerBook. I'll have to look into this more.
-
Inappropriate?I can reproduce it every time, but only on my powerbook, it works as expected on my intel iMac
I’m thankful
-
Inappropriate?Indeed, this only affects PowerPC machines. This is fixed in (the upcoming) version 1.0.1.
The company says
this solves the problem
EMPLOYEE
EMPLOYEE
