'Re: Automatic completion mode'

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

List:       kde-usability
Subject:    Re: Automatic completion mode
From:       Jos Poortvliet <jospoortvliet () gmail ! com>
Date:       2008-11-17 6:49:21
Message-ID: 200811170749.22194.jospoortvliet () gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

On Monday 17 November 2008 02:38:31 Aaron J. Seigo wrote:
> On Sunday 16 November 2008, Maciej Pilichowski wrote:
> >   KDE suggestion list needs a bit of polishing, it is already
> > reliable, so I don't see any reason to come up with something
> > different especially with so many drawbacks.
>
> a) this completion mode comes from KDE3, so all the comments regarding 3 vs
> 4 are a little misinformed
>
> b) the obvious reason for defaulting to this completion mode in krunner is
> that it has a list of matches. those matches are occluded from view  if
> there is a drop down list.

Also, if you set text completion on automatic, it seems to interfere with what 
krunner chooses as default - hitting enter doesn't always start the matched 
app but autocompletes and nothing happens. Anyone noticed that?

[Attachment #5 (text/html)]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" \
"http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" \
content="1" /><style type="text/css">p, li { white-space: pre-wrap; \
}</style></head><body style=" font-family:'Sans Serif'; font-size:10pt; \
font-weight:400; font-style:normal;">On Monday 17 November 2008 02:38:31 Aaron J. \
Seigo wrote:<br> &gt; On Sunday 16 November 2008, Maciej Pilichowski wrote:<br>
&gt; &gt;   KDE suggestion list needs a bit of polishing, it is already<br>
&gt; &gt; reliable, so I don't see any reason to come up with something<br>
&gt; &gt; different especially with so many drawbacks.<br>
&gt;<br>
&gt; a) this completion mode comes from KDE3, so all the comments regarding 3 vs<br>
&gt; 4 are a little misinformed<br>
&gt;<br>
&gt; b) the obvious reason for defaulting to this completion mode in krunner is<br>
&gt; that it has a list of matches. those matches are occluded from view  if<br>
&gt; there is a drop down list.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"><br></p>Also, if you set text completion on automatic, it seems to \
interfere with what krunner chooses as default - hitting enter doesn't always start \
the matched app but autocompletes and nothing happens. Anyone noticed \
that?</p></body></html>

_______________________________________________
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] 