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

List:       kde-usability
Subject:    Re: standardizing modes of text selection
From:       Leo Savernik <l.savernik () aon ! at>
Date:       2004-03-18 15:30:46
Message-ID: 200403181630.47435.l.savernik () aon ! at
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Donnerstag 18 März 2004 14:15 schrieb Sébastien Laoût:
[...]
> : in some Windows applications (not all !) the selection automatically
>
> select by words (as MS IE...) : it's a disgrace. You can return to a
> letter by letter selection by moving the cursor on the oposite side of
> the selection, but it's too sensible, and word by word behaviour
> reappears as soon as we go back on the initial direction :-/
> I love your way !!

Oh yeah, IE selection drives me nuts whenever I have to cope with it. I do not 
*ever* want that emulated in the free software world.
>
> Because of the need of consistency, must this behaviour be a
> freedesktop.org recommendation ?

No, it needs not. I even think that it is not the right place for such 
proposals. Maybe it should be filed under openusability.org?

[...]
> > - - Konqueror: khtml only supports single and doubleclick, but cannot
> > extend the selection word wise. Tripleclick will select the whole
> > paragraph, not the whole line. Shift works only for single clicks.
>
> I want to precise that we can't drag selected text in Konqueror to
> another application :-( We must act with a copy/paste or a selection
> paste.

Yes, this is a bug. It's an easy fix -- no, it would be an easy fix if someone 
(who very likely happens to be me) fixed it eventually.

> The behaviour must so allow dragging of selected text => then erase
> selection and begin a new one on _mouse release_, if no drag was
> occured.

Heh?!?
>
[...]
> > Another behaviour that annoys me is the "autoselection" of some of the
> > text widgets, especially since the "selected" text cannot be pasted with
> > the middle mouse button.
> > In fact I'd really prefer the "autoselection" could be disabled in some
> > way, since its inconsistency.

Watch out who you are quoting. I didn't write this.

Nonetheless, I did not refer to text selection behaviour in textareas/input 
fields in konqueror, but to text selection of (read only) html text itself.

>
> I agree !
> It's a pain and useless !!!!!!

Hehe, this is a usability issue of its own. It would go way beyond the scope 
of this proposal ;-).

[...]
>
> Well, a last subject is selecting by words.
> It's the same problem as Shift+Ctrl+directionnal_keys.
> e.g. text "Hello worls, how| are you ?" (| is the cursor).
> Ctrl+Shift+right must select " are you" or " are you " ???

No, it must select " ", because the caret is always placed at the beginning of 
the next word. Analogically, for backwalking, the caret is placed at the 
beginning of the immediately previous word.

However, if you select "how| are you" at | with a doubleclick, IMHO "how" 
should be selected (and not "how are" as is currently done in khtml).

[...]
> - "Hello worls, how| are you ?" Right will select " are"

Khtml selects " " here on Ctrl+Shift+Right which is conceptually reasonable as 
it is the beginning of the immediately next word.

> - But left will select " how" (this time, include the space à left
> because user hasn't taken one on right).

Khtml selects "how". Note that we are not talking about textareas, as these 
are controlled by Qt.

[...]

mfg
	Leo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQFAWcCmj5jssenUYTsRAvduAJ0UuV1gql/+OnCxWVn0EkqGb7HECACggFX7
qeD4KbjQNW8w0LTC5ZoeQog=
=6MOZ
-----END PGP SIGNATURE-----
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability

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