Bug 147588 - Irregular Font and style Settings across a chat screen
Summary: Irregular Font and style Settings across a chat screen
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: Chat Window (show other bugs)
Version: unspecified
Platform: Gentoo Packages Other
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-05 20:20 UTC by Smak
Modified: 2023-01-06 05:22 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Smak 2007-07-05 20:20:12 UTC
Version:            (using KDE KDE 3.5.7)
Installed from:    Gentoo Packages
Compiler:          Gcc 
OS:                Other

It is my opinion that the way font and style properties are set and assigned in kopete don't logically flow. 
If one uses the font and style settings selection tool under the kopete configure settings, the setting are only applied to the "chat window" portion of a chat screen. The "users list" (IRC Protocol) and "user input box" are left unchanged. The font settings from the user input box seems to be only effected by the kconfig global font settings. This should be changed. The font and style settings for all the possible text displays "chat window", "user list", "user input box" should all be configurable from the kopete settings and possibly have different configurable options.  I personally run my monitor at 1600x1200 and my chat window font I can easily set to a readable level through kopete, but the user input box that I use to type my message is way to small to be readable. This has been a problem for a long time and I can't believe I am the first person to report that this is a problem.

-Smak
Comment 1 Andrew Crouthamel 2018-11-02 04:24:07 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-16 02:41:18 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2022-12-07 00:23:45 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-12-22 05:19:05 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2023-01-06 05:22:58 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!