<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sun, Jun 29, 2014 at 8:33 AM, David T. Lewis <span dir="ltr"><<a href="mailto:lewis@mail.msen.com" target="_blank">lewis@mail.msen.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>On Sun, Jun 29, 2014 at 12:45:29AM -0500, Chris Muller wrote:<br>
> ><br>
> > It turns out that the preference lives in category "browsing", as opposed<br>
> > to<br>
> > say "windows".<br>
> ><br>
> ><br>
> -- I guess it could be either but it's also a browser function. If there<br>
> is already a usable browser on the desktop for whatever you're asking for,<br>
> implementors, senders, hierarchy browser, package browser, MC browser,<br>
> etc., it'll bring forth that browser rather than open yet another, using<br>
> more memry, and that you'll just have to close someday.<br>
><br>
> Oh, if you search preferences for "Windows" it's right there..<br>
><br>
> I'm curious whether, when you say, "open..." | Transcript, and you get the<br>
> same Transcript instead of a new one, does that annoy you too?<br>
<br>
</div></div>It's probably mainly a matter of habit and training, but no that does not<br>
annoy me.<br>
<br>
I am accustomed to thinking of the transcript as a single thing that can<br>
be written to from anywhere, somewhat like a stdout stream. I am also<br>
accustomed to thinking of the transcript window itself as being the thing<br>
that gets written to. So if I tell the system to open that singleton window,<br>
and it is already open, I am not surprised that the system refuses to make<br>
two instances of something that is supposed to only have one. </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On the other hand, if I tell the system to inspect something, I expect it<br>
to open an inspector on that thing.</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">When I ask the system to this, and it<br>
decides to do something else instead, I am annoyed.<br></blockquote><div><br></div><div>Ah, I think I finally realized the root cause of the annoyance. You had the inspector window already open, but it was not occluded by any other window. So when you invoked 'inspect' in another window, there was not as dramatic a change on the screen, just the focus shift. If you didn't notice that, it may have left you thinking the inspect command "didn't work." By opening a new window every time, the users attention is more effectively directed to the location of the window on the screen.</div>
<div><br></div><div>This makes me wonder if a #flash would help for that scenario..</div></div></div></div>