Call up Visor the first time does not focus it

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Call up Visor after it has been started
2. Attempt to write something

What is the expected output?
I expect the text to be written in the command line.

What do you see instead?
I hear the alert sound of MacOS X.

The current workaround is to click into the Visor terminal window.  After 
clicking in there all 
subsequent call ups are immediately allowing one to write commands after call 
up without 
clicking into it with the mouse.

What version of the product are you using? On what operating system?
While I downloaded and installed Visor 1.5a1, it still reports v1.2 when using 
"About Visor...".
SIMBL is v0.8.2

Please provide any additional information below.
Running
- MacOS X 10.5.6
- Mac Pro & MacBook Pro

Original issue reported on code.google.com by Phx...@gmail.com on 29 Mar 2009 at 8:12

[GoogleCodeExporter]

Priority can be Low

In general Visor works, but just has this annoyance to click into after first 
call up.

Original comment by Phx...@gmail.com on 29 Mar 2009 at 8:18

[GoogleCodeExporter]

Please, try Visor 1.8.1 and report here again.
http://github.com/darwin/visor

Original comment by antonin....@gmail.com on 31 Mar 2009 at 9:42

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Downloaded the latest version (v1.8.1).

The new version immediately calls up the terminal window visor-style, but 
inactive.  At this state (right after 
startup):
- If typing anything it would type something in the underlying application
- Clicking the Visor-style terminal window to set the focus lets it disappear 
(without rolling up), so one needs 
to call it up again using the shortcut.
- Clicking anywhere else (where the Visor window is not covering the screen) 
will not roll up the Visor window
- Pressing the keyboard shortcut would let it disappear, then roll down and 
then up, so one needs to call it up 
again using the shortcut

All in all, the update made it actually worse as more steps are required to 
type something within Visor the first 
time after start.

Again, after Visor finally has the focus, all subsequent call-ups work 
flawlessly.  It's just the first call-up after 
start, which produces the odds described.

Original comment by Phx...@gmail.com on 1 Apr 2009 at 1:47

[GoogleCodeExporter]

Yes, reproducible here. I'm starting visor during OSX start so this is not big 
issue for me.

Anyway I'll look what can I do about it. Thanks for reporting.

Original comment by antonin....@gmail.com on 1 Apr 2009 at 1:58

• Changed state: Accepted

[GoogleCodeExporter]

I also usually start Visor during login time and I agree that it does not 
display right away at those points.  
However, I had it at that time, that switching spaces or ending a program you 
called up right after login could 
display Visor in the fashion described above.  Besides those more seldom 
occurrences, pressing the keyboard 
shortcut would still let it disappear, then roll down and then up, so one needs 
to call it up again using the 
shortcut.

Considering this, the the severity is similar to the initial report with a 
slightly different visual effect.

Thanks for looking into it.

Original comment by Phx...@gmail.com on 1 Apr 2009 at 2:27

[GoogleCodeExporter]

It seems to be fixed in 1.9. When clicking on dock icon and termnal.app 
launches it opens and has cursor in 
command line. You may start typing.

I'm not sure what change caused proper behavior, but it seems to be working for 
me now. Please reopen if you 
bounce into this again.

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

• Changed state: Fixed

[GoogleCodeExporter]

Unfortunately v1.9 did not fix it.  In fact, it let both described problems 
appear now: Those from v1.5a1 and 
from v1.8.1.

Calling it up, opens the Visor window immediately with the focus still 
remaining in the previous top-most 
application and clicking the Visor window in the attempt to let it get the 
focus, it disappears and immediately 
rolls down (like described in v1.8.1), but again without having the focus (like 
described in v1.5a1) receiving 
the default alert sound of MacOS X when typing.

To work around this, one needs to either:
- Close the Visor window (press the hotkey assigned) and call it up again
  - or -
- Click outside the Visor window (Visor will remain open) and then within it to 
let it get the focus

Original comment by Phx...@gmail.com on 15 Apr 2009 at 7:09

[GoogleCodeExporter]

Original comment by antonin....@gmail.com on 15 Apr 2009 at 9:51

• Changed state: Accepted

[GoogleCodeExporter]

Hopefully fixed in Visor 2.0

At least it works for me on my both Snow Leopard and Leopard machines.

Original comment by antonin....@gmail.com on 6 Sep 2009 at 6:22

• Changed state: Fixed

[GoogleCodeExporter]

Version 2.0 indeed made the trick.  I also recognized that there is a new Visor 
settings item in the Terminal 
preferences to set up colors and such.  However, the lines set up for the 
window size will not be used as it had 
been before, but this is an issue for another number.

Issue 63 can be laid to rest.

Thanks for the fix!

Original comment by Phx...@gmail.com on 7 Sep 2009 at 11:13