Page 1 of 1
Corrupted? Menu
Posted: Wed Jan 16, 2013 12:54 am
by lohill
I have a menu which I believe has somehow been corrupted. The first 3 options of File are blank and the last option shows. ( I do mean blank rather than disabled.) In the Menu Builder disabling or enabling does not seem to make any difference. Also I have recently noticed that in the Application Browser' Menubar 1' does not show up like I think it used to - with File, Edit etc. indented to MenuBar 1. I have copied the MenuBar to other stacks and all the menu items went to the new stack but they still do not show up as indented. Any suggestions short of delete and start all over would be appreciated.
A related question is: How is the best way to get one common menu (e.g. MenuBar 1) into each of the stacks in the application?
Thank You,
Larry
Re: Corrupted? Menu
Posted: Wed Jan 16, 2013 12:45 pm
by Klaus
Please, please, please give us more info: Platform, version of Livecode, content of menuitems incl. shortcuts etc.

This is a Livecode forum, not one for clairvoyants

Re: Corrupted? Menu
Posted: Wed Jan 16, 2013 4:56 pm
by lohill
Sorry Klaus,
I'm working on a Macintosh using LiveCode version 5.5.3 Build 1497. It is the File Menu with the problem.
When pulled down the File Menu it shows:
Blank (nothing)
Blank (nothing)
Blank (nothing)
Blank (nothing)
New Browser Cmnd-B
The Munu Builder for File shows:
&Open
&Close
-
New New &Browser/B
-
&Quit/Q
Is there a way to incorporate screen shots into these conversations?
Thanks,
Larry
Re: Corrupted? Menu
Posted: Wed Jan 16, 2013 5:18 pm
by Klaus
Hi Larry,
and the content of btn "File" of your menu group is correct when checked via its "inspector"?
What text should be in these menuitems?
No "menu modifying" handlers involved anywhere?
Click "Upload attachment" (right to "Options") at the bottom of the EDIT page
Best
Klaus
Re: Corrupted? Menu
Posted: Wed Jan 16, 2013 6:10 pm
by lohill
Klaus,
There are no special menu modifying handlers that I am aware of.
I have attached a screenshot that should show everything.
Thanks,
Larry
Re: Corrupted? Menu
Posted: Wed Jan 16, 2013 10:14 pm
by Klaus
Hi Larry,
sorry, don't see a screenshot?
Re: Corrupted? Menu
Posted: Thu Jan 17, 2013 12:07 am
by jacque
I don't see a screenshot either, but I think I understand what you're describing. Put this into the message box and tell us what you get:
put btn "File"
I'm betting you get 3 blank lines at the top.
Re: Corrupted? Menu
Posted: Thu Jan 17, 2013 6:36 pm
by lohill
Test reply. Something is wrong with posting a reply. It blanks out my message and then tells me my message has too few characters.
Re: Corrupted? Menu
Posted: Thu Jan 17, 2013 6:41 pm
by lohill
Re: Corrupted? Menu
Posted: Thu Jan 17, 2013 6:44 pm
by lohill
Jacque,
The message box showed no blank lines.
larry
Re: Corrupted? Menu
Posted: Thu Jan 17, 2013 7:15 pm
by jacque
Right. Well. I looked at your screen shot and couldn't see anything wrong there either. It's pretty bizarre, I've never seen that kind of wonkiness before. So wandering off into the weeds here...could the textcolor of the menu items be white? Could there be some invisible odd character before those blank lines that would throw off the engine? What happens if you remove the left-parentheses so that the items are enabled?
I think if I were doing this, I'd just delete the whole contents of the File menu and type it back in by hand into the property inspector (bypassing the menu builder.) Don't copy/paste, just retype it all. If that doesn't work, I'd be tempted to just rebuild a new menu.
Re: Corrupted? Menu
Posted: Thu Jan 17, 2013 11:01 pm
by lohill
Thanks Jacque,
I think that answers my original question.
Larry
Re: Corrupted? Menu
Posted: Thu Jan 17, 2013 11:25 pm
by jacque
For the second part of your question, you can show the same menu in all stacks by setting the one in the mainstack as the defaultMenuBar. This can cause issues in the IDE, where the LiveCode menu is the default. I usually just set mine to default if the environment is not "development". Alternately, you can install duplicates of the menubar into each stack, but that's a lot of trouble to maintain if you need to make changes.