I remember trying virtual box in snow leppard, it didn't work at all, the qt applications can also give windows screen readers problems. This is why developers should use the native controls for their applicatioons and not take short cuts like using these nonstandard tool kits. On Mar 29, 2012, at 2:04 PM, Jacob Schmude wrote:
> Hi > QT, not quicktime. QT, the GUI toolkit. Rockbox, for example, has absolutely > zero to do with quicktime at all. Perhaps I should have specified that, but I > guess I thought the names of apps would have made that clear. > On Mar 29, 2012, at 11:50 AM, Esther wrote: > >> Hi Jacob, >> >> Is it possible that most of these applications ran QuickTime 7? If Rockbox >> was built for the earlier versions, it almost certainly ran QuickTime 7. In >> Snow Leopard QuickTime 7 was still distributed on the system DVDs -- it just >> wasn't loaded by default. In Lion you're going to have to separately >> download QuickTime 7 if you want older AppleScripts based on it to work. >> You'll also have to change those references from QuickTime to QuickTime 7. >> I had to do this to update my AppleScripts that speed up podcast listening. >> >> To download QuickTime 7 for Lion, check the Apple KnowledgeBase support page: >> • Installing QuickTime Player 7 on Mac OS X v10.6 or Later >> http://support.apple.com/kb/HT3678 >> >> HTH. Cheers, >> >> Esther >> >> On Mar 29, 2012, at 4:33 AM, Jacob Schmude wrote: >> >>> Hi all, >>> So, I'm back on Mac (finally) now that Lion has fixed all of the bugs I >>> considered show stoppers in Snow Leopard. It's good to be back, however, >>> I'm having a rather strange problem that I can't account for. No >>> applications based on QT seem to be accessible anymore. These include >>> TeamTalk, Rockbox Utility, VirtualBox, and a few others. I didn't use >>> TeamTalk back in sl, but I did use Rockbox Utility and VirtualBox >>> regularly. In sl, QT applications were quirky but useable. In Lion, >>> however, I can't use them at all. Everything renders as unknown, and >>> interacting with these unknowns either reveals nothing or reveals more >>> blank unknowns inside. The bewildering part about this is that I know a few >>> people who do not have this issue with these same programs, so I'm trying >>> to trace it. So far, I've had no luck. I've tried in both 32-bit and 64-bit >>> modes (I come from a Linux background so I know how 32-bit and 64-bit >>> libraries can have trouble interacting with one another) but that doesn't >>> make a difference. I'm wondering if I'm missing a library somehow, but if I >>> am, it's one that doesn't come with Lion as I've set up Lion in a Fusion >>> virtual machine and still have the same problem. >>> Can anyone shed some light on this? Those who have QT applications working >>> with VoiceOver, did you install or configure anything to make it work? If I >>> can get this bit working, I can ditch Windows for good. >>> >>> Thanks >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "MacVisionaries" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/macvisionaries?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/macvisionaries?hl=en. > -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en.
