<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 01/13/2014 01:38 PM, Alessandro
Pasotti wrote:<br>
</div>
<blockquote
cite="mid:CAL5Q670zvvz2NxAG=n-1waY2mbBkNALw7g=bcsA-_MUN3r63ZQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">2014/1/13 Matthias Kuhn <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:matthias.kuhn@gmx.ch" target="_blank">matthias.kuhn@gmx.ch</a>></span><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>
<div class="h5">
<div>On 01/13/2014 11:46 AM, Alessandro Pasotti
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">2014/1/13 Régis
Haubourg <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:regis.haubourg@eau-adour-garonne.fr"
target="_blank">regis.haubourg@eau-adour-garonne.fr</a>></span><br>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi
there,<br>
as feature freeze is coming, I raise an
issue i didn't find in the lists or<br>
in the tracker.<br>
When working with attribute table, I had
many problems on a classical use<br>
case. I just explore attribute table,
filter, order, and then select lines,<br>
and zoom on the map.<br>
<br>
- selection of lines is very slow even for
small tables. Do we need to<br>
trigger redraws when the selected features
are not in current canvas?<br>
Anyway, selecting/ unselecting is to slow<br>
<br>
- selected line(s) are grey, and my eyes
can't see a difference with other<br>
non selected lines. I liked old blue 1.x
color.<br>
<br>
- When selecting a set of feature (using
maps tools or expression), my first<br>
idea is to explore the selected fetaures
one by one. So I click on one and<br>
then will zoom on the feature, but this
refreshes current selection. When<br>
displaying only selected items, I loose
then my set of selected objects.<br>
What is the right workflow? Is there a way
to convert a manual selection set<br>
into a filter? Or could we add a
contextual click to 'zoom on the feature',<br>
not modifying current selection?<br>
<br>
Tell me if I need to open tickets or if
someone is already on it.<br>
Cheers,<br>
Régis<br>
<br>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>I'd just add to your notes that IMHO
the current attribute search is much less
usable than the old one, I feel that the
most frequent operation is filtering but
you have now to dig into the combo and
choose "column filter" to actvate one,
while in previous versions the filtering
functions were immediately available.</div>
<div><br>
</div>
</div>
<br clear="all">
</div>
</div>
</blockquote>
</div>
</div>
What would be the solution to this?<br>
Promoting the columns to top-level items instead of
second-level items?<br>
Or having a single toplevel "Search" item, which
searches on all columns?<br>
</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>Hello Matthias,</div>
<div><br>
</div>
<div>Unfortunately I'm not a UX expert, I just noticed that
doing one of the most common operations on attributes is
IMHO harder than before.</div>
<div><br>
</div>
</div>
It would be great if those of us who have more experience in
collecting user's feedback (i.r. during courses or trainings)
could ask the users they meet what is their feeling about
this.</div>
<div class="gmail_extra">
<br>
</div>
<div class="gmail_extra">But what I would like to see is
something like this:</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra"><a moz-do-not-send="true"
href="http://www.flickr.com/photos/45502883@N06/11928403446/">http://www.flickr.com/photos/45502883@N06/11928403446/</a></div>
</div>
</blockquote>
<br>
Alessandro, thank you for the mockup.<br>
<br>
The issue I see with this is, that the filter is defined in two
different locations (in opposite corners of the window).<br>
This would probably be thought of as a two-step approach ( 1: Filter
for visible features 2: In addition, filter for features containing
"Australia") where the two conditions would probably be connected by
AND. I am not sure if this makes things easier ("Why is Australia
not listed? Ah yeah, I have to change back to "Show All". Or: "Why
are not all features shown even though I see a button saying "Show
All").<br>
<br>
However, these are only my thoughts and I probably do have a
strongly biased developers view.<br>
<br>
CC to UX list<br>
<br>
Matthias<br>
</body>
</html>