https://bugs.kde.org/show_bug.cgi?id=440366
--- Comment #3 from nttkde <watisthis...@outlook.com> --- I think this is because sometimes DolphinView::setActive() doesn't emit the writeStateChanged signal. It seems some other call to the function at wrong time messes it up and the signal doesn't get emitted and/or then the active==m_active ends up being equal and returns. Especially FocusIn event that calls it somewhere inbetween is maybe a bit sus? If I (for the sake of testing) comment out the line "setActive(true)" in DolphinView::eventFilter in "case QEvent::FocusIn" (dolphinview.cpp:903), the menu seems to start working again. There is a bug that perhaps might be related; see https://bugs.kde.org/show_bug.cgi?id=379135 and search/dolphinsearchbox.cpp:219. It affects Create New submenus in the background-context menu, File menu and the hamburger menu, since those use the same DolphinNewFileMenu/KNewFileMenu object. Right-click menu above a folder seems to create a separate DolphinNewFileMenu instance and selectedItemsProperties.supportsWriting() etc are used for setting other actions' enabled/disabled state so they're not affected. -- You are receiving this mail because: You are watching all bug changes.
