when a project is open, stand-alone editing windows and other windows (preferences, bundle editor, html view, you name it) don't react to the cmd+W keystroke (as would be appropriate), but only to cmd+shift +W. the "Close" shortcut in the File menu is still associated to cmd +shift+W, while cmd+W is bound to "Close tab". closing all open projects causes the "Close" shortcut to become again cmd+W.
stupid but annoying.
this bug was probably introduced in the latest revision, or at least I didn't notice it earlier.
bye,
domenico
Using the latest here, and I can't confirm this. If I have, say, the latex bundle open as a project, and I open the bundle editor, cmd-w closes it. Same with preferences, as well as new documents. Using 1161.
On Jul 15, 2006, at 1:45 PM, Domenico Carbotta wrote:
when a project is open, stand-alone editing windows and other windows (preferences, bundle editor, html view, you name it) don't react to the cmd+W keystroke (as would be appropriate), but only to cmd+shift+W. the "Close" shortcut in the File menu is still associated to cmd+shift+W, while cmd+W is bound to "Close tab". closing all open projects causes the "Close" shortcut to become again cmd+W.
stupid but annoying.
this bug was probably introduced in the latest revision, or at least I didn't notice it earlier.
bye,
domenico
Haris
I get this behavior in 1161.
On 15 Jul 2006, at 19:55, Charilaos Skiadas wrote:
Using the latest here, and I can't confirm this. If I have, say, the latex bundle open as a project, and I open the bundle editor, cmd-w closes it. Same with preferences, as well as new documents. Using 1161.
On Jul 15, 2006, at 1:45 PM, Domenico Carbotta wrote:
when a project is open, stand-alone editing windows and other windows (preferences, bundle editor, html view, you name it) don't react to the cmd+W keystroke (as would be appropriate), but only to cmd+shift+W. the "Close" shortcut in the File menu is still associated to cmd+shift+W, while cmd+W is bound to "Close tab". closing all open projects causes the "Close" shortcut to become again cmd+W.
stupid but annoying.
this bug was probably introduced in the latest revision, or at least I didn't notice it earlier.
bye,
domenico
Haris
Mark
On 15.07.2006, at 20:55, Charilaos Skiadas wrote:
Using the latest here, and I can't confirm this. If I have, say, the latex bundle open as a project, and I open the bundle editor, cmd-w closes it. Same with preferences, as well as new documents. Using 1161.
I'm with Haris on this one. Works for me.
Soryu
PS: Greetings to Italy. Long time no see, dom.
On Jul 15, 2006, at 2:45 PM, Domenico Carbotta wrote:
when a project is open, stand-alone editing windows and other windows (preferences, bundle editor, html view, you name it) don't react to the cmd+W keystroke (as would be appropriate), but only to cmd+shift+W. the "Close" shortcut in the File menu is still associated to cmd+shift+W, while cmd+W is bound to "Close tab". closing all open projects causes the "Close" shortcut to become again cmd+W.
stupid but annoying.
this bug was probably introduced in the latest revision, or at least I didn't notice it earlier.
bye,
domenico
I had this problem. But it has since gone away mysteriously.
thomas Aylott—subtleGradient
Domenico Carbotta <domenico.carbotta@...> writes:
when a project is open, stand-alone editing windows and other windows (preferences, bundle editor, html view, you name it) don't react to the cmd+W keystroke (as would be appropriate), but only to cmd+shift +W. the "Close" shortcut in the File menu is still associated to cmd +shift+W, while cmd+W is bound to "Close tab". closing all open projects causes the "Close" shortcut to become again cmd+W.
stupid but annoying.
this bug was probably introduced in the latest revision, or at least I didn't notice it earlier.
bye,
domenico
Do you, by chance, use MegaZoomer; posted by Allan recently on his blog. I personaly got rid of it because it was causing a lot of strange behaviors throughout my system (some “invisible” windows...)
If you use it, try disabling it...
Do you, by chance, use MegaZoomer; posted by Allan recently on his blog. I personaly got rid of it because it was causing a lot of strange behaviors throughout my system (some “invisible” windows...)
grrr...
I guess I gotta roll back to a mixed writeroom+textmate setup, until Allan doesn't start working on a fullscreen mode.
On Jul 16, 2006, at 1:10 PM, Domenico Carbotta wrote:
I'm not sure I get it... Do you confirm it was MegaZoomer causing the problem ?
yes
That's odd. I have MegaZoomer installed and I don't get the bug anymore. I did change MegaZoomer's keystroke to ⌘⌥⌃⇧Z in the Keyboard prefpane. Maybe that fixed it?
thomas Aylott—subtleGradient
thomas Aylott <thomas.42@...> writes:
That's odd. I have MegaZoomer installed and I don't get the bug anymore. I did change MegaZoomer's keystroke to ⌘⌥⌃⇧Z in the Keyboard prefpane. Maybe that fixed it? thomas Aylott—subtleGradient
That's odd but true : simply changing the Mega Zoom keyboard shortcut seems to solve all the strange issues I had with MegaZoomer. Thanks !
On Jul 16, 2006, at 1:10 PM, Domenico Carbotta wrote:
I'm not sure I get it... Do you confirm it was MegaZoomer causing the problem ?
yes
That's odd. I have MegaZoomer installed and I don't get the bug anymore. I did change MegaZoomer's keystroke to ⌘⌥⌃⇧Z in the Keyboard prefpane. Maybe that fixed it?
I was talking with Ian recently and he fixed a lot of the issues. In a nutshell, MegaZoomer had been inserting delegates and that had caused some troubles, so he switched to swizzling + notifications.
So it may be related to the keystroke as other things have suggested, but it might be a good idea to get 0.4.1 anyway. For me, the problem existed 'til I downloaded the new version.
BTW, Ian's a great guy and a fairly responsive developer, so if you've got requests, it might not be a bad idea to send them to him. Just don't tell him I sent you :D
Rob
-
Charilaos Skiadas -
Domenico Carbotta -
guerom00 -
Mark Eli Kalderon -
Rob Rix -
Soryu -
thomas Aylott