I am missing so many messages in this thread, that I don't know whether someone
has already brought up this point.
On the Mac, the menu bar does not follow *the mouse*, it follows *focus*. If you use any
mechanism (clicking on the window, alt-tab, selecting an app from the dock or a document
f
On Sun, 26 Dec 2010 09:46:34 +, Nicholas Clark
wrote:
> On Sun, Dec 26, 2010 at 10:41:47AM +0100, Aristotle Pagaltzis wrote:
>
> > That seems like a solution at first thought, doesn't it? But the
> > menu bar is at the top of the screen. The pointer is often far
> > away. A straight line fro
On Sun, Dec 26, 2010 at 10:41:47AM +0100, Aristotle Pagaltzis wrote:
> That seems like a solution at first thought, doesn't it? But the
> menu bar is at the top of the screen. The pointer is often far
> away. A straight line from the pointer to the menu bar will cross
> windows of other applicatio
* Nicholas Clark [2010-12-26 08:20]:
> On Tue, Dec 21, 2010 at 10:15:03PM +0100, Aristotle Pagaltzis wrote:
> > The point is that it does not work in the *general case*,
> > because a confluence of UI and API choices means that
> > applications *may* crash under FFM, because of how the menu
> > ba
On Tue, Dec 21, 2010 at 10:15:03PM +0100, Aristotle Pagaltzis wrote:
> The point is that it does not work in the *general case*, because
> a confluence of UI and API choices means that applications *may*
> crash under FFM, because of how the menu bar works. You can list
> exceptions to the rule (i
