Hi,
I generated simple application with AppWizard and noticed strange
default menu behavior.
Some menu labels are repeated in key shortcut labels, or even placed
instead key labels.
I observed the same situation in "File" menu after setting
dApp.ShowCommandWindowMenu to False.
"Close window" label is missing in his place, but is displayed together
with key label.
Sample illustration here: http://img40.imageshack.us/img40/8485/dabomenu.jpg
Is there something I don't know about it?
Did someone noticed this?
--
Regards
Jacek Kaóucki
On Aug 8, 2009, at 4:24 AM, Jacek Ka=B3ucki wrote:
> I generated simple application with AppWizard and noticed strange
> default menu behavior.
> Some menu labels are repeated in key shortcut labels, or even placed
> instead key labels.
> I observed the same situation in "File" menu after setting
> dApp.ShowCommandWindowMenu to False.
> "Close window" label is missing in his place, but is displayed =20
> together
> with key label.
> Sample illustration here: =
http://img40.imageshack.us/img40/8485/dabomenu.jpg
> Is there something I don't know about it?
> Did someone noticed this?
There were some odd menu problems with submenus when running =
under =20
Windows, but these were fixed a while back. What version of Dabo and =20
Windows are you running?
-- Ed Leafe
Author: Jacek Kałucki
Posted: 2009-08-08 11:23:42 Link
Uÿytkownik Ed Leafe napisaó:
> There were some odd menu problems with submenus when running under
> Windows, but these were fixed a while back. What version of Dabo and
> Windows are you running?
>
Windows XP SP3
Dabo 0.9.2 5308
wxPython 2.8.10.1 unicode
Python 2.5.4
--
Regards
Jacek Kaóucki
Jacek Kaóucki wrote:
> Hi,
>
> I generated simple application with AppWizard and noticed strange
> default menu behavior.
> Some menu labels are repeated in key shortcut labels, or even placed
> instead key labels.
> I observed the same situation in "File" menu after setting
> dApp.ShowCommandWindowMenu to False.
> "Close window" label is missing in his place, but is displayed together
> with key label.
> Sample illustration here: http://img40.imageshack.us/img40/8485/dabomenu.jpg
> Is there something I don't know about it?
> Did someone noticed this?
I've noticed this for at least the last 2 years, on Windows. I figured
it was how Windows menus work. But it does look dumb.
I also set ShowCommandWindowMenu to False. You are saying that doing
this causes the observed behavior in the Reports menu?
Paul
Author: Jacek Kałucki
Posted: 2009-08-08 11:41:42 Link
Uÿytkownik Paul McNett napisaó:
> I've noticed this for at least the last 2 years, on Windows. I figured
> it was how Windows menus work. But it does look dumb.
>
> I also set ShowCommandWindowMenu to False. You are saying that doing
> this causes the observed behavior in the Reports menu?
>
No, Reports menu isn't relatet with ShowCommandWindowMenu property,
but it always displays wrong.
With ShowCommandWindowMenu equals True, "Close window" item is displayed
properly
on fourth position, but when set to False, is displayed with labeling
problem on second position.
--
Regards
Jacek Kaóucki
2009/8/8 Paul McNett <p@ulmcnett.com>
> I've noticed this for at least the last 2 years, on Windows. I figured
> it was how Windows menus work. But it does look dumb.
I did some work that improved the menu's a while back but windows
menus are still quirky in their display and event handling.
Regards,
Nate
Author: Jacek Kałucki
Posted: 2009-08-11 08:08:48 Link
UÃâŠÃÂŒytkownik Nate Lowrie napisaÃâŠÃ¢â¬Å¡:
> I did some work that improved the menu's a while back but windows
> menus are still quirky in their display and event handling.
>
It's not a good news for me, since my application usage proportion
is 70/30% Windows/Linux.
I have two questions:
1) Could somebody explain me, what is purpose of adding empty menu item
at every first element of menu in dMenu._createMenuItem method,
2) Why mehods own/disown in dMenu.remove method, are called twice,
first in wx.Menu.RemoveItem method, and second therein.
I didn't noticed any difference in application working with or without them.
--
Regards
Jacek KaÃâŠÃ¢â¬Å¡ucki
2009/8/11 Jacek Ka=B3ucki <laborm@rz.onet.pl>:
> U=BFytkownik Nate Lowrie napisa=B3:
>> I did some work that improved the menu's a while back but windows
>> menus are still quirky in their display and event handling.
>>
>
> It's not a good news for me, since my application usage proportion
> is 70/30% Windows/Linux.
>
> I have two questions:
> 1) Could somebody explain me, what is purpose of adding empty menu item
> at every first element of menu in dMenu._createMenuItem method,
> 2) Why mehods own/disown in dMenu.remove method, are called twice,
> first in wx.Menu.RemoveItem method, and second therein.
> I didn't noticed any difference in application working with or without th=
em.
It's a legacy issue. What version of WX are you using? When I was
working with the menus, we were still on wx 2.7. It was an issue in
wx, and the methods above got around the inherent problems enough to
make the menu usable. See
http://www.nabble.com/weird-menu-problem-with-mnxml-to18795225.html#a187952=
25
and http://www.nabble.com/Sub-Menu-display-problem-to18813741.html#a1881374=
1
for the applicable threads. I never did get it fixed.
Regards,
Nate