Focusing on Terminal should open new window

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Launch Terminal
2. There is no step two.

What is the expected output? What do you see instead?
I expect to see a new terminal window when I open the Terminal, or when I
focus onto it when there are no open terminal windows already.  Instead you
don't see any terminal windows and have to make a new one.

What version of the product are you using? On what operating system?
1.5a1 on 10.5.1

Please provide any additional information below.
MacBook Pro

Original issue reported on code.google.com by itisto...@gmail.com on 20 Nov 2007 at 12:04

[GoogleCodeExporter]

Confirmed. Happens in OS X 10.5.2

Original comment by tou...@gmail.com on 17 Feb 2008 at 2:13

[GoogleCodeExporter]

Confirmed on OS X 10.5.5

Original comment by geer...@gmail.com on 29 Nov 2008 at 9:06

[GoogleCodeExporter]

Actually the terminal window you opened is just the Visor window. Otherwise you
cannot start using Visor. And click the terminal icon again does not open a new
terminal, just as it did when you don't have Visor...

Original comment by lzh1...@gmail.com on 4 Dec 2008 at 5:23

[GoogleCodeExporter]

I believe that in the older version of this add-on, clicking on terminal did 
open up
a new window. 

Original comment by tou...@gmail.com on 4 Dec 2008 at 1:16

[GoogleCodeExporter]

Second toupsz's comment above.

Original comment by itisto...@gmail.com on 4 Dec 2008 at 2:50

[GoogleCodeExporter]

Third.

Original comment by cmhaa...@gmail.com on 11 Dec 2008 at 8:20

[GoogleCodeExporter]

just hit Command + N...

I think Visor binds on the first created Terminal window which is the default 
created when you launch the app...

I think Visor could take a differente approach for solving this and many other 
problems... Visor could be 
something like Yakuake, instead of a Terminal Plugin, it could use the 
Terminal's components and stay like a 
independent Native Cocoa Application, it could bring a vast flexibility to 
Visor, better effects using Core 
Animation and quartz and many other customizations, not to say, we could get 
rid of SIMBL.

Original comment by opti...@gmail.com on 5 Jan 2009 at 1:44

[GoogleCodeExporter]

Fixed in Visor 1.8.1.

Anyway, solution using "Terminal's components" is not viable. There is no such 
a thing as a Terminal.app 
components usable in standalone Cocoa app.

Original comment by antonin....@gmail.com on 7 Mar 2009 at 3:45

• Changed state: Fixed

[GoogleCodeExporter]

I just installed 1.8.1, and instead of opening a new Terminal window upon 
focus, it
opens the Visor window... :-\

Original comment by itisto...@gmail.com on 7 Mar 2009 at 6:16

[GoogleCodeExporter]

I don't understand what you exactly want. By term "terminal window" I mean both 
visor-ed window and standard 
non-visor-ed terminal window. Do you want opening just standard terminal window 
on Dock icon click when 
there is no Terminal.app running? How would you run Visor-ed window with this 
feature in place?

Current behavior is consistent with Terminal.app without Visor. When you click 
dock icon and Terminal.app is 
not running. One terminal window is created and is immediately Visor-ed, that 
is the rule. You get focus into is. 
Creating new terminal windows must be done via right-click on dock icon. Left 
clicking dock icon does just focus 
of currently running terminal window (be it Visor-ed or not).

Original comment by antonin....@gmail.com on 7 Mar 2009 at 10:38

[GoogleCodeExporter]

The way the previous version worked (the Tiger one), was that a *new* Terminal 
window
would open if no other windows (except the Visor window) were open.

> Do you want opening just standard terminal window on Dock icon click when 
there is no Terminal.app running?

No, the Terminal can be running or not running.  When it's activated (either on
first-launch or not), then if there are no windows open *besides the visor 
window*, a
new window should be created.

The Visor window should only be activated by the hotkey - not by activating the 
Terminal.

Hope that makes sense!

Original comment by itisto...@gmail.com on 7 Mar 2009 at 8:03

[GoogleCodeExporter]

Yes it makes sense, now I see. I'm sorry, but I'm not going to implement this 
feature. I don't personally need it 
and I want code as simple as possible. Current behavior maps directly to 
standard Terminal.app behavior. Visor-
ed window is standard terminal window executed with special flags (border-less 
and positioned off-screen).

I guess, you can always create applescript which will launch New Window command 
from Terminal.app dock 
context menu, give it Terminal.app icon and you get requested behavior.

Original comment by antonin....@gmail.com on 8 Mar 2009 at 8:02

[GoogleCodeExporter]

That's unfortunate, as this behavior makes the Terminal behave improperly, for
example when switching spaces, or when quitting all applications but the 
Terminal, as
in these situations it activates the Terminal and brings down the Visor window,
something the user is not expecting (nor wanting).

How do you change the status back to "Not Fixed"?

Original comment by itisto...@gmail.com on 9 Mar 2009 at 12:41

[GoogleCodeExporter]

Original comment by antonin....@gmail.com on 9 Mar 2009 at 8:37

• Changed state: WontFix

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

So, looking at the project members page, there is currently only one active 
member of
this project, and that's you.  Thank you for putting your time into improving 
this
program, but it as appears there are a lot of people who consider this a 
serious bug,
and a lot of people who also want to join the project (see the project page).

I think it's fairly ridiculous to set the status to "WontFix", when it's 
clearly a
serious bug, at the very least let someone else give it a go if you don't have 
the
time or the will to do it.

Original comment by itisto...@gmail.com on 9 Mar 2009 at 6:30

[GoogleCodeExporter]

* Serious bug refers to the behavior of your new 1.8.1 build, which causes the 
visor
to pop down at times when it shouldn't.

Original comment by itisto...@gmail.com on 9 Mar 2009 at 6:47

[GoogleCodeExporter]

I'm here just because I personally wanted to clear this list of Visor issues 
:-) But with this #4 will be problem.

But you are right, I've opened the bug again. But I personally don't consider 
this as a serious bug.

I don't see any people who want to join the project (where do you see them?). 
Anyone is welcome fork the 
project and contribute as I did here: 
http://github.com/darwin/visor/tree/master, there is no need to ask 
beforehand.

Original comment by antonin....@gmail.com on 9 Mar 2009 at 6:50

• Changed state: New

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Thanks Antonin!

Sorry, I was confused, as were a lot of other people, by the "How to join?" 
link on
the project page: http://code.google.com/p/support/wiki/HowToJoinAProject

Apparently many people did not realize that that's not a project-specific page 
but a
general info page on the topic. :-p

Original comment by itisto...@gmail.com on 9 Mar 2009 at 6:53

[GoogleCodeExporter]

Yeah, would be cool to have those people working on Visor day/night :-)

Original comment by antonin....@gmail.com on 9 Mar 2009 at 7:03

[GoogleCodeExporter]

I would give it a go myself if only I had the time!

Original comment by itisto...@gmail.com on 9 Mar 2009 at 7:10

[GoogleCodeExporter]

I consider this fixed in 1.9.

Opening a new terminal window by clicking on dock icon is not original terminal 
behavior. It won't be 
implemented.

Original comment by antonin....@gmail.com on 14 Apr 2009 at 2:37

• Changed state: Fixed