Version: 2.0-git (using KDE 4.4.5) OS: Linux When a new basket is created, a specific foreground and background colour is assigned to it. The same happens when creating a new tag. When creating a new note, a font is assigned to it. Baskets and tags created in Basket 1.x didn't carry a colour assigned, unless one was specified explicitly. In Basket 2.x, the baskets that I have created in the old version use the system colours for background and foreground, while I have to specify the colour for any new created. The only workaround to fix this broken behaviour is to edit the XML files by hand and remove the colour from there. The new behaviour causes the following major inconveniences: 1. When the system colour scheme is changed, the colour of old baskets and tags doesn't change, and one has to go and change them all by hand, or have notes that are in complete disagreement with the rest of the system, not to mention notes in all colours of the rainbow after several scheme changes. 2. Currently the explicitly assigned colours are wrong, they default to white text on white background with my current colour scheme unless I change them each time. (I don't think this a separate bug, because the colour choices should be "None" anyway.) 3. I have a Code tag that specifies a monospace font for notes with programming code. This doesn't work because all notes have an explicit font that overrides my monospace choice in the tag. I propose: 1. Add an option (default) or (none) to colour and font choices in the aforementioned places. 2. Default to them when creating anything. 3. Either remember the previous colour when creating a basket, *or* add a button/setting to change the default. Reproducible: Always
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!
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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
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!
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!
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!