MATLAB: Migrated GUIDE to App Designer — App partially off screen

app designerguideMATLABmigrate tool

Hello,

Just started using App Designer after years with GUIDE. Succesfully migrated a small test program, but when run, it starts with half of the app off the top of the screen.

Nothing special in terms of position at the start. GUIDE .fig has four buttons, a few text boxes two axes, and a button group.

Any idea?

Thanks.

Doug

Best Answer

Open the app in appdesigner.

In the component browser, select the main figure.

Then check the "Position" property and determine if has a large vertical location (2nd element of the position vector).

190909 193238-Migrated GUIDE to App Designer -- App partially off screen - MATLAB Answers - MA.jpg

Related Solutions

MATLAB: MatLab returns false figure size in script

Add a call to drawnow after creating the figure

%% Creating GUI
GUI=uifigure('Name','Spectrograms',...
                'NumberTitle','off',...
                'WindowState','maximized');
            
% Update figures and process callbacks
drawnow;
            
% get window size
Position=get(GUI, 'Position');
GUI_Width=Position(3);
GUI_Height=Position(4);

MATLAB: App Designer How to “StartUp” within the App

(1) Two possibilities to reset your app to its default state:

https://www.mathworks.com/matlabcentral/answers/489003-reset-or-clear-property-values-in-app-designer#comment_763148

https://www.mathworks.com/matlabcentral/answers/489003-reset-or-clear-property-values-in-app-designer#answer_399598

I prefer the first. A simple example using a function called resetComponents:

classdef app1 < matlab.apps.AppBase
    % Properties that correspond to app components
    properties (Access = public)
        UIFigure        matlab.ui.Figure
        EditFieldLabel  matlab.ui.control.Label
        EditField       matlab.ui.control.EditField
        Button          matlab.ui.control.Button
    end
    % Component initialization
    methods (Access = private)
        % Create UIFigure and components

        function createComponents(app)
            % Create UIFigure and hide until all components are created
            app.UIFigure = uifigure('Visible', 'off');
            app.UIFigure.Position = [100 100 640 480];
            app.UIFigure.Name = 'UI Figure';
            % Create EditFieldLabel

            app.EditFieldLabel = uilabel(app.UIFigure);
            app.EditFieldLabel.HorizontalAlignment = 'right';
            app.EditFieldLabel.Position = [382 282 56 22];
            app.EditFieldLabel.Text = 'Edit Field';
            % Create EditField

            app.EditField = uieditfield(app.UIFigure, 'text');
            app.EditField.Position = [453 282 100 22];
            % Create Button

            app.Button = uibutton(app.UIFigure, 'push');
            app.Button.Position = [129 282 100 22];
            app.Button.Text = 'Reset';
            app.Button.ButtonPushedFcn = @app.resetButtonCallback;
            % Show the figure after all components are created
            app.UIFigure.Visible = 'on';
        end
        
        function resetComponents(app)
            % Create EditFieldLabel
            app.EditFieldLabel = uilabel(app.UIFigure);
            app.EditFieldLabel.HorizontalAlignment = 'right';
            app.EditFieldLabel.Position = [382 282 56 22];
            app.EditFieldLabel.Text = 'Edit Field';
            % Create EditField
            app.EditField = uieditfield(app.UIFigure, 'text');
            app.EditField.Position = [453 282 100 22];
            % Create Button
            app.Button = uibutton(app.UIFigure, 'push');
            app.Button.Position = [129 282 100 22];
            app.Button.Text = 'Reset';
            app.Button.ButtonPushedFcn = @app.resetButtonCallback;
            
            % Or, alternatively, instead of redefining each component, just figure out all
            % properties which could be changed by the user and reset them to their
            % defaults:
            %

            % app.EditField.Value = '';
            %
            % Simpler here, but takes more work for more complicated apps.
        end
        
        function resetButtonCallback(app, ~, ~)
            resetComponents(app);
        end
    end
    % App creation and deletion
    methods (Access = public)
        % Construct app
        function app = app1
            % Create UIFigure and components
            createComponents(app)
            % Register the app with App Designer
            registerApp(app, app.UIFigure)
            if nargout == 0
                clear app
            end
        end
        % Code that executes before app deletion
        function delete(app)
            % Delete UIFigure when app is deleted
            delete(app.UIFigure)
        end
    end
end

(2) You can access a callback function if you have access to an instance of the app and you are calling from a location allowed by the function's Access attribute (e.g. Public, Private, etc).

Example 1: You cannot call a callback function from within a static method, because the static method does not have access to an instance of the app.

Example 2: You cannot call a callback function externally if its Access attribute is Private.

Best Answer

Related Solutions

MATLAB: MatLab returns false figure size in script

MATLAB: App Designer How to “StartUp” within the App

Related Question