Bug 195343 - New sub-basket does not respect color scheme
Summary: New sub-basket does not respect color scheme
Status: RESOLVED WORKSFORME
Alias: None
Product: basket
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Kelvie Wong
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-05 16:40 UTC by David Rankin
Modified: 2023-01-12 05:16 UTC (History)
1 user (show)

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 David Rankin 2009-06-05 16:40:22 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

I live by basket notepads. In kde4.3 beta1 the import of my baskets went perfect and everything looked great. I am using the Obsidian Coast color scheme.

The first time I added a sub-basket, the entire sub-basket was added with a white background. Curiously, the text color was close to white so it made it next to impossible to see. All other existing baskets were shown with the proper "Obsidian Coast" color scheme. I had to manually edit the sub-basket properties to set the color scheme to make it look right.

I have a screen shot showing the way the new sub-basket got added:

http://www.3111skyline.com/download/openSUSE_bugs/kde4/screenshots/basket-add-basket-bug.jpeg
Comment 1 Robert Marmorstein 2010-01-18 09:14:29 UTC
I am unable to reproduce this with the latest basket from gitorious.  The background color is selectable in the "New Basket" dialog, so I am not quite sure why you are having trouble.  Could you better explain the manner in which you are creating the sub-basket?
Comment 2 Andrew Crouthamel 2018-11-02 23:04:43 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 3 Andrew Crouthamel 2018-11-16 05:38:37 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 4 Justin Zobel 2022-12-13 02:53:34 UTC
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version?  
  
If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-12-28 05:23:43 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 6 Bug Janitor Service 2023-01-12 05:16:43 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!