why after making my executable gui some buttons do not work?

Question

Erwin Avendaño 2017-11-5

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/365251-why-after-making-my-executable-gui-some-buttons-do-not-work

评论： Walter Roberson 2017-11-6

I made a gui that links another 9 more, each one has a method in which it calculates and graphs. Before making it executable they worked for me but after doing it an .exe file and opening it some buttons do not work, why?

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

请先登录，再进行评论。

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

Answer 1

Walter Roberson 2017-11-5

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/365251-why-after-making-my-executable-gui-some-buttons-do-not-work#answer_289566

Did you specifically tell the compiler to add the files for the other GUIs ? If you used GUIDE then because of the way it constructs callbacks, it would be common for the compiler to not be able to figure out that some files were needed. You would need to either add the files specifically or you would need to use %#function pragmas. https://www.mathworks.com/help/compiler_sdk/ml_code/function.html

13 个评论
显示 11更早的评论隐藏 11更早的评论

Erwin Avendaño 2017-11-5

在 MATLAB Online 中打开

function varargout = metodo2(varargin) % METODO2 MATLAB code for metodo2.fig % METODO2, by itself, creates a new METODO2 or raises the existing % singleton*. % % H = METODO2 returns the handle to a new METODO2 or the handle to % the existing singleton*. % % METODO2('CALLBACK',hObject,eventData,handles,...) calls the local % function named CALLBACK in METODO2.M with the given input arguments. % % METODO2('Property','Value',...) creates a new METODO2 or raises the % existing singleton*. Starting from the left, property value pairs are % applied to the GUI before metodo2_OpeningFcn gets called. An % unrecognized property name or invalid value makes property application % stop. All inputs are passed to metodo2_OpeningFcn via varargin. % % *See GUI Options on GUIDE's Tools menu. Choose "GUI allows only one % instance to run (singleton)". % % See also: GUIDE, GUIDATA, GUIHANDLES

% Edit the above text to modify the response to help metodo2

% Last Modified by GUIDE v2.5 05-Nov-2017 10:22:45

% Begin initialization code - DO NOT EDIT gui_Singleton = 1; gui_State = struct('gui_Name', mfilename, ... 'gui_Singleton', gui_Singleton, ... 'gui_OpeningFcn', @metodo2_OpeningFcn, ... 'gui_OutputFcn', @metodo2_OutputFcn, ... 'gui_LayoutFcn', [] , ... 'gui_Callback', []); if nargin && ischar(varargin{1}) gui_State.gui_Callback = str2func(varargin{1}); end

if nargout [varargout{1:nargout}] = gui_mainfcn(gui_State, varargin{:}); else gui_mainfcn(gui_State, varargin{:}); end % End initialization code - DO NOT EDIT

% --- Executes just before metodo2 is made visible. function metodo2_OpeningFcn(hObject, ~, handles, varargin) movegui(gcf,'center')

axes(handles.axes1) imshow('logo.jpg') axes(handles.axes3) imshow('recuadro.jpg') axes(handles.axes4) imshow('recuadro.jpg') axes(handles.axes5) imshow('recuadro.jpg') axes(handles.axes6) imshow('recuadro.jpg') axes(handles.axes7) imshow('recuadro.jpg') axes(handles.axes11) imshow('recuadro.jpg') axes(handles.axes12) imshow('biseccion.jpg')

handles.output = hObject;

% Update handles structure guidata(hObject, handles);

% UIWAIT makes metodo2 wait for user response (see UIRESUME) % uiwait(handles.figure1);

% --- Outputs from this function are returned to the command line. function varargout = metodo2_OutputFcn(~, ~, handles) % varargout cell array for returning output args (see VARARGOUT); % hObject handle to figure % eventdata reserved - to be defined in a future version of MATLAB % handles structure with handles and user data (see GUIDATA)

% Get default command line output from handles structure varargout{1} = handles.output;

function edit1_Callback(~, ~, ~) % hObject handle to edit1 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of edit1 as text % str2double(get(hObject,'String')) returns contents of edit1 as a double

% --- Executes during object creation, after setting all properties. function edit1_CreateFcn(hObject, ~, ~) % hObject handle to edit1 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. % See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

% --- Executes during object creation, after setting all properties. function axes1_CreateFcn(~, ~, ~) % hObject handle to axes1 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles empty - handles not created until after all CreateFcns called

% Hint: place code in OpeningFcn to populate axes1

function pushbutton1_Callback(~, ~, ~) % hObject handle to pushbutton1 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of pushbutton1 as text % str2double(get(hObject,'String')) returns contents of pushbutton1 as a double

% --- Executes on button press in pushbutton3. function pushbutton3_Callback(~, ~, handles) syms x %variable simbolica x f=get(handles.edit8,'string'); xl=str2double(get(handles.edit3,'string')); xu=str2double(get(handles.edit5,'string')); tol=str2double(get(handles.edit4,'string')); E=100; xa=100; i=0; while(tol<E) xr=(xl+xu)/2; fxl=subs(f,x,xl); fxr=subs(f,x,xr); m=fxl*fxr; if(m)<0

        xu=xr;
    else
        xl=xr;
    end
    E=abs(xr-xa);
    xa=xr;
    i=i+1;
end
xr;
vpa(E,5)
set(handles.edit6,'string',xr);
set(handles.edit9,'string',E);
% --- Executes on button press in pushbutton4.
function pushbutton4_Callback(~, ~, handles)

f=inline(get(handles.edit8,'string')); xl=str2double(get(handles.edit3,'string')); xu=str2double(get(handles.edit5,'string'));

if xl~=xu axes(handles.axes2); ezplot(f,[xl,xu]),grid on; else axes(handles.axes2); ezplot(f),grid on;

end function edit3_Callback(~, ~, ~)

% --- Executes during object creation, after setting all properties. function edit3_CreateFcn(hObject, ~, ~) % hObject handle to edit3 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. % See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

function edit4_Callback(~, ~, ~)

% --- Executes during object creation, after setting all properties. function edit4_CreateFcn(hObject, ~, ~) % hObject handle to edit4 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. % See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

function edit5_Callback(~, ~, ~)

% --- Executes during object creation, after setting all properties. function edit5_CreateFcn(hObject, ~, ~) % hObject handle to edit5 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. % See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

function edit6_Callback(~, ~, ~)

function edit6_CreateFcn(hObject, ~, ~) % hObject handle to edit6 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. % See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

% --- Executes during object creation, after setting all properties. function edit7_CreateFcn(~, ~, ~) % hObject handle to edit7 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles empty - handles not created until after all CreateFcns called

function edit8_Callback(~, ~, ~) % hObject handle to edit8 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of edit8 as text % str2double(get(hObject,'String')) returns contents of edit8 as a double

% --- Executes during object creation, after setting all properties. function edit8_CreateFcn(hObject, ~, ~) % hObject handle to edit8 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. % See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

% --- Executes during object creation, after setting all properties. function axes2_CreateFcn(~, ~, ~) % hObject handle to axes2 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles empty - handles not created until after all CreateFcns called

% Hint: place code in OpeningFcn to populate axes2

function edit9_Callback(~, ~, ~) % hObject handle to edit9 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of edit9 as text % str2double(get(hObject,'String')) returns contents of edit9 as a double

% --- Executes during object creation, after setting all properties. function edit9_CreateFcn(hObject, ~, ~) % hObject handle to edit9 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. % See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

% --- Executes on button press in pushbutton5. function pushbutton5_Callback(~, ~, ~) close(metodo2); metodo1

% --- Executes on button press in pushbutton6. function pushbutton6_Callback(~, ~, handles) set (handles.edit8, 'String', ''); set (handles.edit3, 'String', ''); set (handles.edit5, 'String', ''); set (handles.edit4, 'String', ''); set (handles.edit9, 'String', ''); set (handles.edit6, 'String', ''); axes(handles.axes2); cla reset

% --- Executes during object creation, after setting all properties. function axes12_CreateFcn(~, ~, ~) % hObject handle to axes12 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles empty - handles not created until after all CreateFcns called

% Hint: place code in OpeningFcn to populate axes12

% --- Executes during object creation, after setting all properties. function pushbutton4_CreateFcn(~, ~, ~) % hObject handle to pushbutton4 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles empty - handles not created until after all CreateFcns called

% --- Executes during object creation, after setting all properties. function axes5_CreateFcn(~, ~, ~) % hObject handle to axes5 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles empty - handles not created until after all CreateFcns called

% Hint: place code in OpeningFcn to populate axes5

Erwin Avendaño 2017-11-5

the previous code is from the button that no longer serves

Walter Roberson 2017-11-6

The cause of this is the same as https://www.mathworks.com/matlabcentral/answers/365294-does-my-code-have-an-error#answer_289606 . It even looks to me as if that is a duplicate question . Duplicate questions keep the volunteers spending time cleaning up questions instead of spending time answering the questions.

请先登录，再进行评论。