From kde-pim Wed Aug 24 23:20:08 2005 From: Ingo =?iso-8859-1?q?Kl=F6cker?= Date: Wed, 24 Aug 2005 23:20:08 +0000 To: kde-pim Subject: Re: [Kde-pim] kmail separate reader window having previous/next Message-Id: <200508250120.10108 () erwin ! ingo-kloecker ! de> X-MARC-Message: https://marc.info/?l=kde-pim&m=112492562620253 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============1575024940==" --===============1575024940== Content-Type: multipart/signed; boundary="nextPart6512361.IrOZcY3yjP"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart6512361.IrOZcY3yjP Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 24 August 2005 11:04, martin.p.bradley@bt.com wrote: > In kmail mail can be opened in a separate window whenever it is > double clicked. I want to add two new buttons to the toolbar of the > separate reader window. These buttons are to change the contents of > the separate window to the next/previous email in the current list of > messages in the main window. This feature has been on the wish list > for a long time. > > > So far I have added one new button to the tool bar. It can be added > to using the usual configure toolbar dialogue. The button is > connected to a slot in kmreaderwin.cpp called void > KMReaderWin::moveToNextMessage(). > > void KMReaderWin::moveToNextMessage() uses > kmkernel->getKMMainWidget() to get mainWidget, a pointer to the main > widget. "mainWidget->headers() const" will give me a pointer to the > header. This can't work correctly from the separate reader window because the=20 user might have switched to another folder in the meantime. Fixing this=20 problem is extremely hard because of all the sorting and threading that=20 happens in kmheaders. You would have to create a fake kmheaders object=20 for each separate message window. Obviously this sucks. When switching=20 to KDE 4 this might become feasible by separating model and view, but=20 currently I don't see a nice way to implement this feature. I won't comment on the rest of the message because your approach is=20 unfortunately fundamentally flawed. Regards, Ingo --nextPart6512361.IrOZcY3yjP Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQBDDQCqGnR+RTDgudgRAlebAJ9O6DKe6Nws76vMMa+6DraJWUFcrACg3e08 0cY8R3NdHiT9A3SYEBzoucQ= =XJqZ -----END PGP SIGNATURE----- --nextPart6512361.IrOZcY3yjP-- --===============1575024940== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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/ --===============1575024940==--