berengui Migration Report

Completed by Migration Tool

Generated berengui_App.mlapp from berengui.fig and berengui.m
Converted components and configured their properties
Copied GUIDE callback and utility function code
Analyzed berengui.m for unsupported MATLAB API usage

Your Next Steps

Decide whether to continue migrating the berengui app depending on whether it has important features that are not supported in App Designer.
Update the app code to use new APIs.

Step 1: Decide Whether to Continue Migrating the berengui App

The berengui app has functionality that is not supported in App Designer. If that functionality is an important aspect of your app, then it might not be practical to continue migrating it. Review this list, and confirm that none of the items are critical to the functioning of your app before continuing to the next step.

Functionality	Details	GUIDE Tag / Line #
ButtonDownFcn	This callback is not supported in App Designer.	plotAIgram
PickableParts	This property is not supported in App Designer.	plotAIgram plotCC plotEventGram plotMod1 plotMod2 plotPI Show more (3) Show less
gca	This is not supported in App Designer code.	line 1850
gcf	This is not supported in App Designer code.	line 62 line 195 line 204 line 623 line 674 line 1412 line 1462 line 1783 line 1787 line 1796 line 1800 Show more (8) Show less
ginput	This is not supported in App Designer code.	line 364 line 1321

Step 2: Update the App Code to Use New APIs

App Designer uses object-oriented code and new component APIs. Use the following process to update the code to be compatible with App Designer. For more details, see GUIDE Migration Strategies.

1. Choose Callback

Choose a callback to update, starting with the OpeningFcn callback.

2. Resolve Code Alerts

Resolve any code alerts () that appear in the editor.

3. Apply Workarounds

Apply workarounds for partially supported functionality.

5. Resolve Errors

Resolve any run time errors. For assistance, see Common Error Messages and Suggested Actions.

4. Run App

Run the app and exercise the callback you are updating.

Partially Supported Functionality in berengui and Workarounds

Functionality	Details and Workarounds	GUIDE Tag
SizeChangedFcn	App Designer only supports pixel units. You might need to update the `SizeChangedFcn` callback if it uses other units. Workaround: Update your `SizeChangedFcn` callback to work with pixel units.	main

Common Error Messages and Suggested Actions

Error Message	Example Line of Erroring Code	Suggested Action	Explanation
`Unrecognized property '<property name>' for class '<app name>'.`	`app.numCylinders = 6;`	Create an app property and access it using `app.<property name>` throughout your app's code.	Properties must be added before you can use them.
`Undefined function or variable 'hObject'.`	`app.output = hObject;`	Delete this code.	This code is not needed because App Designer uses the `app` object as the output.
	`guidata(hObject, handles);`	Delete this call to `guidata`.	The `guidata` function is not needed in App Designer.
	`miles = get(hObject, 'Value');`	Replace `hObject` with `app.<component>`, where `<component>` is the object that triggers the callback. `velocity = app.VelocityEditField.Value;`	`hObject` is used in GUIDE to access the object that triggered the callback. App Designer uses `app.<component>` instead.
`Undefined function or variable 'handles'.`	`calculateMPG(handles);`	Replace handles with `app`. `calculateMPG(app);`	GUIDE uses `handles` to share components and data. App Designer uses the `app` object instead.
`Error using matlab.ui.control.<component type> There is no <property name> property on the <component type> class.`	`set(app.Button, 'String', 'Go');`	Update the code to use the appropriate property for this component. `app.Button.Text = 'Go';`	To see a list of component properties, right-click a component on the canvas and select Help on Selection in the context menu.