[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice
Subject:    Re: auto-switching to frame mode-behaviour
From:       "Stephan Hachinger" <StephanHachinger () compuserve ! de>
Date:       2001-06-10 10:29:37
[Download RAW message or body]

On Sun, Jun 10, 2001 at 11:47:48AM +0200, Stephan Hachinger wrote:
> > ----- Original Message -----
> > From: "Thomas Zander" <zander@planescape.com>
> > To: <koffice@max.tat.physik.uni-tuebingen.de>
> > Sent: Sunday, June 10, 2001 1:01 AM
> > Subject: Re: auto-switching to frame mode-behaviour
> >
> >
> > > On Sat, Jun 09, 2001 at 10:07:50PM +0200, David Faure wrote:
> > > > On Saturday 09 June 2001 22:18, Stephan Hachinger wrote:
> > > > > Hello!
> > > > >
> > > > > I like the new auto-switching behaviour, but I'd change it in the
> > following
> > > > > mode:
> > > > >
> > > > > - Clicking once onto a frame (object/formula/etc.) activates frame
> > mode, not
> > > > > only clicking on the frame borders.
> > > >
> > > > I'm inclined to do that for pictures. But formulas and objects are
> > editable,
> > > > just like text frames, so I don't see why they should act
differently.
> > > > The current behaviour is consistent (click inside something to edit
it).
> > > > Changing it to the above would break that.
> > > >
> > > > > - A doubleclick onto a frame calls the application to edit edit
the
> > contents
> > > > > (I think this is done by a single click now, or am I wrong? The
reason
> > for
> > > > > my suggestion is that I think that newbies would recognize the way
> > they can
> > > > > switch to frame mode more easily and that an sometimes unwanted
single
> > click
> > > > > into an object frame already calls the application in the current
> > state and
> > > > > so these unwanted clicks take much time at my P133 :)).
> > > >
> > > > Yes, I acknowledge that the single-click-to-open-the-object is a
little
> > bit...
> > > > unexpected sometimes... But I think we decided against double-click
in
> > KDE
> > > > (for main actions. We use double-click for e.g. selecting in a list
and
> > closing a dialog
> > > > at the same time, but those two actions can be done separately with
> > single clicks).
> > > >
> > > > Hmm, I'm a bit undecided. Any other opinion on this ?
> > > >
> > > > PS: no, this won't be made dependent on the "single click vs double
> > click to activate"
> > > > global setting, this would lead to too many bugs due to testing only
one
> > mode most of
> > > > the time.
> > >
> > > I agree with David here, double click is evil, ask your doctor ;)
> > >
> > > I think that since ctrl->click will select the frame, and ctrl->drag
will
> > > allow you to drag it; we have created a very consistent way of
> > manipulating
> > > frames, and the contents.
> > >
> > > It may not be what you would expect at first, but the solve Stephan
> > > suggested will only lead to confusion.
> >
> > OK, I see. Sorry, didn't notice this with the ctrl key.. should have
> > examined it more thourougly (I've got so little time at the moment :(( )
But
> > a change for the picture frames would be ok, I think... or does anybody
> > think this also makes the behaviour inconsistent?
>
> That only picture frames (which can not (yet) be edited) behave
differently
> from all others?

Hmm, right, if there will be a possibility of editing them, there will only
be one more problem... the possibilities with ctrl+click etc. are absolutely
convenient, as I see now. Another thing ... those things like "ctrl
activates frame dragging/selecting mode"... shouldn't they be placed in some
tip database (did you know ? :)))) - an absolutely perfect M$ solution; I
usually click on this "don't show me again" checkbox and close) or faq
or...? Until June 30th I won't have much time to help due to a scholarship
exam, but I always have the kindness to give proposals which mean work ;).
But... I could do something like this in July, before the final release.

Cheers,

Stephan

[prev in list] [next in list] [prev in thread] [next in thread]