gottlieb_at_research.nj.nec.com writes:
> > Sender: mkrisch_at_bbn.com
> > Date: Thu, 03 Jul 1997 13:04:54 -0400
> > From: Mark Krischer <mkrisch_at_bbn.com>
> > References: <199707031559.LAA09801_at_allan.nj.nec.com>
> >
> > gottlieb_at_research.nj.nec.com wrote:
> >
> > > Warping the mouse is not so nice. I would prefer the behavior used by
> > >
> > > ghostview where the pupup window is put under the mouse's current
> > > postion.
> >
> > actually, i don't know why the mouse needs to move at all. in xemacs if
> > i move to a different frame, focus moves with me and the mouse stays
> > where it is....
>
> It sounds like we are agreeing that the mouse should stay put.
>
> I suggested poping up the window under the current mouse position.
> You seem to be suggesting poping the window anywhere and giving focus
> to it dispite the mouse not being in the poped up window. I would
> have no objection to either scheme, but do not like having the system
> move the mouse.
What I'd like to see is
1) "child" windows such as file dialogs and popups (sometimes called
"application modal" windows) "always on top", of
their parent but not necessarily of any other app's windows.
2) Limit the placement of said popups to screen space occupied by
their parent window, or at least put the upper left corner inside
the parent.
3) A "dynamic focus for popups" option, where popup windows always got
the focus regardless of the focus policy, but only when they first
appear.
4) Don't warp the mouse, that's evil. Not even microsoft does it. ;)
Some of this can probably be done currently. Some of it is probably
impossible or impractical. And all of it is problematic, given
applications such as netscape where things seem at first glance to be
modal dialogs but really arn't (ie., save-to-disk status windows,
host/proxy unreachable at startup error windows, etc.)
Perhaps, while I'm daydreaming, we need a "-DMAKE_NETSCAPE_BEHAVE"
option? ;)
- Jim
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Thu Jul 03 1997 - 13:38:57 BST