Version: CVS (using KDE KDE 3.1) Installed from: RedHat RPMs I was in the debugger and I decided to add/remove some button from the browse toolbar. When exiting the toolbar edit session and of my debugger options were disabled. For example, step into, out, etc. These should have still been enabled as the debugger was still active. The bug maybe that after exiting the toolbar editor the state of the toolbar buttons is not refreshed. PS - It is not clear to me why the debugger buttons are located on the Browse toolbar. Normally there is a standalone toolbar for debugging.
yeap, the toolbars are a mess rigth now! :(
the debug toolbar forgets its state, too. I disable it and next time, there it is again :(
regarding comment #2: are you talking about the floating toolbar?
Interesting. The debugger plugin uses a probably little used feature - KXMLGUIClient::stateChanged() to switch between states from a set of predefined states defined in the ui.rc file. (kdevelop/languages/cpp/debugger/kdevdebugger.rc) From a quick glance at the KXMLGUIClient::stateChanged() code it seems KXMLGuiClient doesn't store the state, it only applies the setting it's been called with. The problem is that this means that when the toolbars have been rearranged (which apparently reverts state to the default) it has no idea what state the buttons should be in. As far as I can tell there is no reasonable way for the application to know if the toolbars have changed, so even if it were to store the needed state, it wouldn't know when to reapply it. Unless I'm missing something (highly likely, this is KXMGUI, after all.. ;) ) this is a kdelibs issue. Reassigning. (Ignoring comment #2 - open a new bug report for different issues.)
Is this bug still relevant with a recent KDE version?
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!