On 9/13/2015 1:14 PM, jean-pierre charras wrote:
> Yes, it mean we have to fix this everywhere wxEVT_UPDATE_UI is used.
> I am afraid we should use the wxSetEnv(wxT("UBUNTU_MENUPROXY"), wxT("0")); solution, because I found an other issue when UBUNTU_MENUPROXY is not set, or set to 1:
> If the footprint editor is run from Kicad (without the board editor) and if the Legacy mode is used at start, after switching to the GAL mode the main menu is no more shown.
> When UBUNTU_MENUPROXY is set to 0, I did not see these issues.
>
If this is the case, you should probably change your last commit to an
assertion and implement the environment variable solution. I don't have
Ubuntu so I have no way of testing the fix. Some how we will have to
test if the WM is Unity and set it accordingly. It will be an ugly hack
because it has to be set before GTK+ is initialized which means this
code will have to live the wxApp constructor. Hopefully this is only
temporary until either Canonical or the wxWidgets devs fix this issue.
Did you try wxWidgets trunk to see if this issue was fixed yet?
On 9/13/2015 1:14 PM, jean-pierre charras wrote: wxT("UBUNTU_ MENUPROXY" ), wxT("0")); solution, because I found an other issue when UBUNTU_MENUPROXY is not set, or set to 1:
> Yes, it mean we have to fix this everywhere wxEVT_UPDATE_UI is used.
> I am afraid we should use the wxSetEnv(
> If the footprint editor is run from Kicad (without the board editor) and if the Legacy mode is used at start, after switching to the GAL mode the main menu is no more shown.
> When UBUNTU_MENUPROXY is set to 0, I did not see these issues.
>
If this is the case, you should probably change your last commit to an
assertion and implement the environment variable solution. I don't have
Ubuntu so I have no way of testing the fix. Some how we will have to
test if the WM is Unity and set it accordingly. It will be an ugly hack
because it has to be set before GTK+ is initialized which means this
code will have to live the wxApp constructor. Hopefully this is only
temporary until either Canonical or the wxWidgets devs fix this issue.
Did you try wxWidgets trunk to see if this issue was fixed yet?