Jamal Mazrui wrote:
I'm curious why Window-Eyes does not observe that convention. If memory serves, the Visible property is not only True by default, but cannot be changed.
It was a conscious decision on our part to not let Window-Eyes be an invisible COM server. There were a lot of reasons for it, but two big ones are:
- Unlike an application like Word, Window-Eyes has lots of effects on your system even if it doesn't have a UI visible. Making the UI invisible would just make things confusing, because you'd still have all the stuff like speech and Braille and hotkeys and whatnot, but you couldn't change any settings. Unless we also disabled those, in which case there's not a whole lot left.
- Window-Eyes lets COM clients do lots of things that make sense in the context of a screen reader but could be considered unsavory otherwise. We thought a user might want to know that it's running when it's running.
