Multiple Uses of UIMENU

Question

Jason 2024-3-4

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/2090081-multiple-uses-of-uimenu

评论： Voss 2024-3-5

Hello, I have just discovered the beauty of uimenu's and think there brilliant as can unclog a GUI since less button!

However, Im not too sure about reusing the code, for example if I have 3 UITables as below (in reality I have about 10), there seems to be a lot of duplicity. Is there a more elegant way to ahcieve this

Also, what if for one of the tables I wanted the menu to e.g. have one more item thats not in the other menu's?

        function startupFcn(app)
            fig= app.UIFigure;
            cm = uicontextmenu(fig);
            m = uimenu(cm,"Text","Delete Row");
            m1 = uimenu(cm,"Text","Paste Data");
            %m.Text = "Delete Row";
            %m1.Text = "Paste Data";
            tbl=app.UITable1;
            tbl.ContextMenu = cm;
            m.MenuSelectedFcn = @app.deleteRow;     %create callback. IMPORTANT: You must use app.****   
            m1.MenuSelectedFcn = @(src,event)app.TablePasteData(src,event,tbl);
            cm.ContextMenuOpeningFcn = @(src,event)app.toggleVisibility(src,event,m);
             %Apply row delete option to other UITABLE2
             cm2 = uicontextmenu(fig);
             m = uimenu(cm2,"Text","Delete Row");
             m1 = uimenu(cm2,"Text","Paste Data");
             tbl=app.UITable2;
             tbl.ContextMenu = cm2;
             m.MenuSelectedFcn = @app.deleteRow;     %create callback. IMPORTANT: You must use app.****   
             m1.MenuSelectedFcn = @(src,event)app.TablePasteData(src,event,tbl);
             cm.ContextMenuOpeningFcn = @(src,event)app.toggleVisibility(src,event,m);             
             %Apply row delete option to other UITABLE3
              cm3 = uicontextmenu(fig);
              m = uimenu(cm3,"Text","Delete Row");
              m1 = uimenu(cm3,"Text","Paste Data");
              tbl=app.UITable3;
              tbl.ContextMenu = cm3;
              m1.MenuSelectedFcn = @(src,event)app.TablePasteData(src,event,tbl);

and here is one of my functions for example

           function deleteRow(app,src,event)
            tbl = event.ContextObject;
            row = event.InteractionInformation.Row;
            tbl.Data(row,:) = [];
           end           
       

(and do I need the src & event in the function argument if instead I call it like this:

m.MenuSelectedFcn = @(src,event)app.deleteRow

instead of

m.MenuSelectedFcn = @app.deleteRow;

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Voss 2024-3-4

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/2090081-multiple-uses-of-uimenu#answer_1420746

编辑：Voss 2024-3-4

"there seems to be a lot of duplicity. Is there a more elegant way to ahcieve this"

Multiple components (e.g., uitables) can share the same context menu.

"what if for one of the tables I wanted the menu to e.g. have one more item thats not in the other menu's?"

If all uitables share a context menu:

have the context menu contain all menu items you need for all uitables
when right-clicking on a component, the component's ButtonDownFcn (if defined) executes before the context menu appears, so any logic you need to update the menu items for the specific component can be in the ButtonDownFcn
in this case, put code in the ButtonDownFcn to set the "extra" menu item visible if right-clicking on the one specific table and invisible if right-clicking on any other table (the first input to the ButtonDownFcn is the clicked component, so you can use that to know which uitable was clicked on)

If each table has its own context menu: make one context menu have an additional menu item.

"and do I need the src & event in the function argument"

Depends on how the MenuSelectedFcn works.

16 个评论
显示 14更早的评论隐藏 14更早的评论

Jason 2024-3-4

在 MATLAB Online 中打开

Hmm, I got it all working for UITables, and tried to do the same for UIAxes, but its not working and I can't see my error: Is not picking up the axes from that trick of using ax = event.ContextObject;

%Create Menu for UIAXES
cm2 = uicontextmenu(fig);
m = uimenu(cm2,"Text","LineScans"); m.ForegroundColor='b';
m1 = uimenu(cm2,"Text","Brightness"); m1.ForegroundColor='r';
%Apply to all UIAxes in one go like above
set([app.UIAxes app.UIAxes2],'ContextMenu',cm2);
%Sub Menus
sbm1=uimenu(m1,"Text","Brighter x 2", "MenuSelectedFcn",@(src,event)app.Brighter(src,event,0.5));
sbm2=uimenu(m1,"Text","Dimmer x 2", "MenuSelectedFcn",@(src,event)app.Brighter(src,event,2));

And this is my function

        function Brighter(app,src,event,factor)  
             factor
             %src
             %properties(event)
             ax=event.ContextObject;                  
             ax.CLim(2)= ax.CLim(2)*factor;
        end
        

This is the error:

Unrecognized method, property, or field 'ContextObject' for class 'matlab.ui.eventdata.ActionData'.
Error in LuthienAlignmentSoftware/Brighter (line 2854)
             ax=event.ContextObject;
Error in LuthienAlignmentSoftware>@(src,event)app.Brighter(src,event,0.5) (line 2925)
              sbm3=uimenu(m1,"Text","Brighter x 2", "MenuSelectedFcn",@(src,event)app.Brighter(src,event,0.5));
 
Error using matlab.ui.internal.controller.WebMenuController/fireMenuSelectedEvent
Error while evaluating Menu Callback.

Voss 2024-3-5

You need to be able to access the uimenu in order to update its MenuSelectedFcn in the axes ButtonDownFcn. In an app, the simplest way to make something accessible is to make it an app property.

If you create the uicontextmenu and uimenus in Design View of App Designer, then they each become separate app properties automatically, so maybe you want to do it that way.

However, they do not need to be separate properties. If you create them programmatically (e.g., in the startupFcn the way I've shown), then you can easily have them all contained in a single app property, say a structure containing all the handles (uimenus and whatever else) you need.

See the two attached apps for examples of the two approaches - both apps do the same thing. Each app has a few different uimenus. In one the menus were created in Design View and are separate app properties; in the other the menus are created in the startup function and are all contained in the app property "h".

As for sub-menus (i.e., any uimenu that is the child of another uimenu), just like the menus themselves (i.e., any uimenu that is the child of a uicontextmenu), you only need to access them if you need to be able to update them on-the-fly as the app is running. It depends on what you want to do, but in this case so far, you'd only need to access those that are going to have a MenuSelectedFcn assigned to them, so that's typically the uimenus that don't have any child uimenus.

Jason 2024-3-5