I see. Thanks. I've got to find a mac hack to disable that then.

That's likely to do with the visual feedback done by the system when highlighting the title of the File menu.

On 08/09/2005, at 23.00, Chris Mear wrote:

...

...

Expected behaviour: Cmd+W closes the file as fast as clicking the "x" icon on the tab Actual behaviour: Cmd+W takes a bit longer to close a file than clicking the "x" icon on each tab\

That's likely to do with the visual feedback done by the system when highlighting the title of the File menu.

If that's what it is, then why don't we see this discrepancy on any other application?

Probably because TM does rendering of stuff when you close a tab, whereas other applications close a window.

OS X in many cases will flush the rectangle encompassing all changes made since last flush, which for TM, when the menu bar highlights, would be the tab + the menu item, plus what's between them. If the window was closed, this wouldn't require any traffic over the graphics bus (at least with QE 2D).

For me though, the two ways of closing a tab is the same in speed, but then, I have AGPx8. The path through my code should also be the same.

If you want to experiment with this, try making the window smaller, and move it closer to the menu bar, to see if it affects the speed.