--===============6958917596833962393==
Content-Type: multipart/signed;
  boundary="nextPart3895733.E9rzY24OET";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart3895733.E9rzY24OET
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

On Tuesday, 2012-02-28, Milian Wolff wrote:
> On Tuesday 28 February 2012 12:03:13 Kevin Krammer wrote:
> > On Tuesday, 2012-02-28, Milian Wolff wrote:
> > > Hey there,
> > >=20
> > > I just wanted to try the potentially awesome new search features to
> > > finally
> > > get a smart folder that shows all my unread emails... Well it "works"
> > > but the behavior is really bad:
> > >=20
> > > - you select some unread email in the smart folder to read it
> > > - it gets marked as read
> > > - the search gets updated
> > > - since the mail is not unread anymore, it gets removed from the smart
> > > folder - kmail selects the next email
> > > - repeat from above
> > >=20
> > > hence, selecting such a folder is like "mark all new email as read"
> > > which is of course not what I want :]
> > >=20
> > > But how could this be fixed? Any ideas? I'd be willing to invest some
> > > time on this, but quite frankly wonder how this should be done. Andras
> > > told me there is a similar bug when you apply a folder-filter on
> > > unread emails.
> > >=20
> > > My use-case could be "solved" by different ways, e.g.:
> > >=20
> > > - never mark emails as read in search folders that search for unread
> > > emails
> > > - only update the search folder after the mail is de-selected
> >=20
> > - do not move selection automatically unless the currently selected item
> > is deleted?
>=20
> yes that could work as well, but how does one differentiate between these
> two? after all, it's the model/qt that does this, no? I'll ask steve later
> if he knows whether this would be feasable

My guess is that the model removes the row, the view clears the selection a=
nd=20
creates a new one.

In this case the view would have to check if an item still exists when the=
=20
model removes a row which is currently the selection.

Maybe it could even monitor the selected item itself.

Cheers,
Kevin

=2D-=20
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

--nextPart3895733.E9rzY24OET
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iD8DBQBPThC0nKMhG6pzZJIRAisrAJ9F1xW+V2Ph0cDbEYqhRTVOC9MrBgCfQxSP
DfNn4zhDSlcfU37XqGPgm0Q=
=xP/R
-----END PGP SIGNATURE-----

--nextPart3895733.E9rzY24OET--

--===============6958917596833962393==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
--===============6958917596833962393==--