On Thu, 13 Apr 2000, Holger Kruse wrote:
> On Thu, Apr 13, 2000 at 09:07:27PM +0000, Don Cox wrote:
> > On 13-Apr-00, Holger Kruse wrote:
> > But the objection is to the console window taking over keyboard input
> > when you are working in a window on another screen. SnoopDOS, for
> > instance, displays a log in the background without grabbing the input
> > like this.
>
> I don't know if there is a parameter for CON:... strings to prevent the
> window from getting active (I don't have my AmigaDOS manuals here).
> If there is then use that in the console string. Otherwise you may want
> to check if a third-party console replacement offers this.
I thought I'd already posted a (shorter) response to this, but I don't
recall seeing it show up, so maybe it got lost.
Although I use KingCON, the feature in question is also present in the
standard CON: handler. The option is "INACTIVE". My complete logging
spec (manually retyped because of the #$^%$#^ MUI string gadgets that
don't support the clipboard) is:
KCON:0/0/672/50/Miami log/AUTO/CLOSE/INACTIVE
The main benefit of using KingCON is that the window can be small when the
scrollback option is available.
In general I think that automatic activation of "unsolicited" windows is a
bad idea for exactly this reason, though it gets a bit stickier in cases
where keyboard shortcuts are possible. Even in those cases, automatic
activation should at least be disablable, since some users might prerefr
to live with needing to use the mouse in order to avoid having keystrokes
stolen by an asynchronous window.
Fred Wright
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
