I've done this before but am struggling now!
What is the best way to list all the menu items on a form?

 At a guess, I'd say that you'd need to parse the .form file?

Use the Form.Menus property

Thanks Bruce, but that lists only top menus and their immediate child menus, some of these could themselves have child menus and so on

bill-lancaster said

Thanks Bruce, but that lists only top menus and their immediate child menus, some of these could themselves have child menus and so on

Yes i know.
Did you want me to write the complete function for you?  :roll:

I'd probably use a recursive function


But I have no idea what you want to do with the info.
That's where you do your own coding.

I'm with 'thatbruce'. All the details are in the .form file: -


This is some of the output from my program 'Screenhot"

 { MenuMain Menu
    Text = Shortcut(("File"), "F")
    Checked = True
    { MenuPrint Menu AllToolButtons
      Name = "MenuPrint"
      Text = Shortcut(("Print"), "P") & "…"
      Picture = Picture["icon:/medium/print"]
      Tag = "Menu"
      Shortcut = "Ctrl+P"
    { MenuExit Menu AllToolButtons
      Name = "MenuExit"
      Text = Shortcut(("Exit"), "E")
      Picture = Picture["icon:/medium/close"]
      Tag = "Menu"
      Shortcut = "Alt+F4"
  { MenuShot Menu
    Text = Shortcut(("Screen shot"), "S")
    { MenuCapture Menu AllToolButtons
      Name = "MenuCapture"
      Text = Shortcut(("Capture"), "C")
      Picture = Picture["icon:/medium/camera"]
      Tag = "Menu"
      Shortcut = "Ctrl+Shift+C"

If you want to parse the menu items to toggle 'enabled/disabled, I wrote this subroutine a few years ago to manage popup menus (right click or context menus)
You can set the menu item by 'block' or by text name. You can set multiple menu items buy sending each name separated by a comma.

example: The menu MyMenu contains the elements Menu1, Menu2, Menu3, Menu4.
  
 
Subroutine:

 Thank you for the solutions, the solution from BruceS was the one I was looking for, but the thatbruce/cogier solution is very interesting.
Thank you once again.
Bill

Be aware if you use the .form file reading option then the source directory path must always be available.
If you use an absolute path to the .form file then the folder can not be moved unless you change the path in the code too.

Or If you use relative ./paths and then make a standalone .gambas executable archive file (not in the project folder) then the .form files are not included in the .gambas archive so that will also fail.

My method will be without any of those problems

Also my method will be "live/current"
Ie. Toggle/Radio menu Values will show as they are currently set not as they are initially configured.
and additional menus added by code will also be detected.

Thanks Bruces

Yes, your points are taken, moot.
Howsomeever, I have a little mind experiment that may destroy both our theories. (Sorry, I've just been viewing a Brian Cox video and if you think you understand quantum physics then both you and I are mad.)

Suppose you have a custom component that is a menu… it isnt in the form nor is it in the menus…

Just to stick my tongue out, we have used such "virtual menu" components for years now. :-)
The are really cool for things like AboutMe's, SystemInfo's, and other things that we can just drag onto a form as a control with no code needed and yet when the proggie runs, woof! there is a menu item.

sleep now
b