Bug 75427 - Signature not visible with mouse wheel when replying a message which is longer then then the composer.
Summary: Signature not visible with mouse wheel when replying a message which is longe...
Status: RESOLVED FIXED
Alias: None
Product: kmail
Classification: Applications
Component: composer (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-17 11:00 UTC by raimund
Modified: 2007-12-11 22:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description raimund 2004-02-17 11:00:05 UTC 
Version:            (using KDE KDE 3.2.0)
Installed from:    Gentoo Packages

When replying to messages KMail does not append a signature if configured to read the signature read from "command output". This feature only works when composing new messages.
Comment 1 raimund 2004-02-17 11:48:10 UTC 
UPDATE:
Signatures read from files do not work either.
Comment 2 raimund 2004-02-17 11:59:14 UTC 
Ok, sorry for the confusion, it's something completely different:

KMail DOES append signatures correctly, but there seems to be a problem with the scrollbar of the compose window:
When I scroll down using the mouse wheel only, no signature is shown. But as soon as I press a key, the signature is inserted and the scrollbar shows that there is some more text.

I'm using QT 3.3.0.
Comment 3 Tom Albers 2004-08-07 17:05:18 UTC 
I can confirm this problem with the development version of KMail:
- take a long signature (command: cat /etc/whatever)
- make sure your composer window popups in a size which is not very high.
- reply to a larger e-mail.
- as long as you use the mouse wheel, you can't see the signature.
- Whenever you press an arrow for example, the scrollbar is resized to the correct length
- you can see the signature.
Comment 4 Allen Winter 2006-08-09 23:11:02 UTC 
Can I close this bug?  Is it still happening in KDE 3.5.3 and above?
Comment 5 Edwin Schepers 2007-12-11 22:14:28 UTC 
works with at least KDE 3.5.7