{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Colter Reed <[EMAIL PROTECTED]>
On 3/29/02 15:57, "Chris Campbell" <[EMAIL PROTECTED]> wrote:
> How does OmniWeb do it? (Command-clicking URLs opens them in a new
> window behind the current one.)
On 3/29/02 15:46, "DiCioccio, Jason" <[EMAIL PROTECTED]> wrote:
> NSWindow#orderFront.. although this will make it go to the front, it won't
> change the key window. If that's what your looking for.. Sounds kinda nasty
> to me though :)
It's not a question of technical feasibility. It's just a matter of
deciding the best way to stick the legos together. I know that windows can
be created without making them key. But users expect the front window to be
the key window -- I see windows come up in front of the window I'm typing in
frequently and it throws me off each time.
When we create a new window while another chat window is actively being
used, the goal isn't to bring it to the front, it's to bring it second and
not make it key.
Again, it's a question of design, not ability. The software landscape is
peppered with examples of ugly software with no justification of its
existence other than "because we could". I would rather take a little extra
time approaching a problem and develop a good solution rather than rush
something and release it as half-baked.
Colter
{#} ----------------------------------------------------+[ fire ]+---
