qtcreator recently used file/project submenu empty
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | appmenu-qt5 (Ubuntu) |
High
|
Łukasz Zemczak | ||
| | qtcreator-plugin-ubuntu (Ubuntu) |
Undecided
|
Unassigned | ||
Bug Description
Using current vivid, with integrated menu (appmenu-qt5), the qtcreator files-> recent files/projects submenus are empty, they work fine if the qt theme env variable is empty (use local menus instead)
| Changed in appmenu-qt5 (Ubuntu): | |
| assignee: | nobody → Łukasz Zemczak (sil2100) |
| Łukasz Zemczak (sil2100) wrote : | #1 |
| Łukasz Zemczak (sil2100) wrote : | #2 |
I just sat down to it once again. I probably found what specific thing in qtcreator causes the unwanted behaviour. It seems those two sub-menus are the only places where the creator is doing menu()->clear(); which I think might be what results in those issues in either appmenu-qt5 or the menu exporter itself. I'll prepare a stand-alone test-case and try debugging it. For now I'll set the appmenu-qt5 task as In Progress and then change it to the root cause itself.
I actually wonder if we didn't have the same problems in previous series?
| Changed in appmenu-qt5 (Ubuntu): | |
| status: | New → In Progress |
| Benjamin Zeller (zeller-benjamin) wrote : | #3 |
Not in scope of the SDK plugin
| Changed in qtcreator-plugin-ubuntu (Ubuntu): | |
| status: | New → Invalid |
| Roman Shchekin (mrqtros) wrote : | #4 |
I can confirm this bug - out of the box my menu isn't working. Little bit annoying.
| Changed in appmenu-qt5 (Ubuntu): | |
| importance: | Undecided → High |
| Eugene Pelekhay (pelekhay) wrote : | #5 |
I think that reason of this issue is another bug https:/
| Sebastien Bacher (seb128) wrote : | #6 |
those menus seem to work in wily now, unsure what changed though...
| tags: | added: rls-w-incoming |
| tags: |
added: rls-x-incoming removed: rls-w-incoming |
| Changed in appmenu-qt5 (Ubuntu): | |
| status: | In Progress → Confirmed |
Interesting - I can reproduce it as well. This must be caused by those entries being added differently which makes appmenu-qt5 confused. In theory appmenu should handle all cases as we're basically fetching the QMenuBar's pointer from the application and just exporting things as they go, so in theory there should be no issue with getting out-of-sync.