| I would say even 3.3.1 ... but until the actual Safari 4 and WebKit are out, I don't think anyone wants to change something that may need to change again. I don't think the actual Safari 4 will fix anything, but there is no use in chasing a moving target on this fix.
Josh On May 6, 2009, at 7:35 AM, Axel Balley wrote: That's not so sure. The updated WebKit enforces a known restriction that requires calling WebKit methods from the main thread only. It was already stated in the WebKit docs before that not doing so could result in unpredictable behaviour. Maybe this should be on the list of issues to fix for 3.4 ?
Axel Le 6 mai 09 à 02:50, Josh Parmenter a écrit : I imagine things will be more compatible in the near future as Safari 4 is actually released (and not Beta)
Josh On May 5, 2009, at 5:43 PM, dani joss wrote: Thanks. I did search the archives, but apparently with the wrong keywords. Pity, I liked Safari 4.Cheers! ~ On Wed, May 6, 2009 at 2:15 AM, Josh Parmenter <josh@xxxxxxxxxxxxxxxxx> wrote: Do you have Safari 4 Beta installed? If so, it is not compatible with SC 3.3. You can search the archives for solutions and options.
Best,
Josh
On May 5, 2009, at 5:11 PM, dani joss wrote: Greetings
I have just installed v 3.3, and I'm experiencing crashes whenever I try to access the help system. In particular, pressing cmd-D either to bring up the main help page or with a class highlighted results in a spinning beachball and a non-responding SC (must force-quit). Calling the .gui method brings up the browser momentarily, with the same symptom after a couple of seconds.
Possibly relevant facts: * The last version that I had used was 3.1.1. I could swear it was working a year or so ago, but it appears that after restoring it (following the problem with the new version) I am experiencing the same symptom with that as well! * running on leopard 10.5.6 * same issue on a mac pro and a macbook, on a number of different user accounts * anything on the app support folder seems to be irrelevant (removed and retried)
Judging from the fact that the old version misbehaves as well, something else must have caused this. Unfortunately, I hadn't used SC for some time, so it is impossible to suspect something in particular. It seems to be the SC browser that crashes, but that's just my impression, I don't know. Otherwise, SC seems to be working fine.
Anybody with the same problem ever occurring? Any troubleshooting suggestions?
Thanks to all in advance
dani~ ****************************************** /* Joshua D. Parmenter
“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono */
****************************************** /* Joshua D. Parmenter
“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono */
****************************************** /* Joshua D. Parmenter http://www.realizedsound.net/josh/
“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono */ |