A kind of clugy workaround that I sometimes use is to enable the Clipboard plugin and set up a trigger to bring up the clipboard contents (useful even if you don't use it for this workaround). Then, whenever you want to do something to text in Word or Firefox, or some such application, you select it, hit Cmd-C, hit whatever your hotkey is for the clipboard contents in QS, and now you can work as if you had just invoked QS with the selected text. Granted, that's one extra key command, but it does work...
On Aug 31, 9:30 am, mason k <[EMAIL PROTECTED]> wrote: > Just to riff on what Melman said, "Cocoa" is mainly a library (API) > that offers a bunch of interface elements to programmers. MS word > doesn't use cocoa because it's a fake Mac port (and nothing MS touches > is right). Firefox doesn't use cocoa because their cross platform > plugin architecture is heavily reliant on the interface API that they > do use, which is called XUL. As long as Firefox offers the > extensibility that makes it Firefox, it won't be written with Cocoa. > I actually switched to Safari because of this problem, but I do miss > Firefox - a lot. Especially since FF3 is so snappy compared to > Safari. > > I bet someone could hack up a workaround to this problem using a > firefox plugin... > > On Aug 28, 8:54 pm, Howard Melman <[EMAIL PROTECTED]> wrote: > > > Getting the selection from another application is difficult. An > > operating system, in part is supposed to keep apps from interacting. > > QS's method works with applications that use the cocoa framework. > > Those apps that don't, don't work. If the apps start using cocoa (and > > probably something specific within cocoa) they should work. > > > Howard > > > On Aug 28, 2008, at 7:38 PM, RC wrote: > > > > I've read that QS does not support these applications in regards to > > > Queing up QS with selected text? are there any solutions what so > > > ever? Mozillas new ubiquitous does it well, a mix between the two > > > would be wonderful.
