MATLAB: Issue with GUI.

guiguideMATLABpushbutton

Hello,

My problem is that in my GUI, I have six pushbuttons with alternating text. I also have a status bar to indicate how much time the user has to select a button. My problem is that the change in text and the status bar is not synced. When I do get it to sync, the status bar is opened in another window, instead of remaining on the GUI with the buttons. By using a pushbutton, I can have the status bar remain on the GUI but it stays filled instead of being synced with the change in text. When I have it synced, I have it part of the timer function callback, but it opens in another window. Can someone please help?

Best Answer

Justin - I think what you can do is create another timer to periodically update the status bar, rather than relying a while loop that is called from within a hidden button (your pushbutton8).

For example, in the GuiTImerUpdateTextExample_OpeningFcn, you can instantiate your two timers, the original one and one for your progress bar as

 handles.timerQuery = timer('Name','MyQueryTimer',               ...
                            'Period',3,                     ...
                            'StartDelay',1,                 ...
                            'TasksToExecute',inf,           ... 
                            'ExecutionMode','fixedSpacing', ...
                            'TimerFcn',{@timerQueryCallback,hObject}); 
 handles.timerProgress = timer('Name','MyProgressTimer',        ...
                               'Period', 0.01,                   ...
                               'TasksToExecute',inf,            ...
                               'ExecutionMode', 'fixedSpacing', ...
                               'TimerFcn', {@timerProgressCallback, hObject});

The "query timer" will expire after three seconds, corresponding to the query that is asked of the user. The "progress timer* will expire every 10 milliseconds and will call the timerProgressCallback. Once we have created the timers, we can initialize your progress axes as

 % set the axes
 cla(handles.axes1);
 set(handles.axes1,'Visible','on','color',[.9 .85 .3]); %this will set the color of the patch
 axis(handles.axes1,[0,1,0,1]); %show only from x=0to 1 and y=0to1
 handles.hPatch = patch([0,0,0,0],[0,0,1,1],'g');
 axis(handles.axes1, 'off'); %do not show axis bars

Note how we create the patch and save its handle to the handles structure. We do this so that we can update this patch object rather than creating a new one every time we want to update the progress "bar".

We then save the updated handles structure and start the the query timer as

 guidata(hObject, handles);
 start(handles.timerQuery);

We don't start the other timer as we rely on the timerQueryCallback to do this for us as

 function timerQueryCallback(hTimer, eventdata, hFigure)
 handles = guidata(hFigure);
 % stop the progress timer
 stop(handles.timerProgress);
 % only set the progress timer to complete if there is text in pushbutton1
 % we pause for half a second to allow the progress bar to update
 if ~isempty(get(handles.pushbutton1,'String'))
    set(handles.hPatch,'XData',[0 1 1 0]);
    pause(0.5);
 end
 % etc.
 % reset the patch to show zero progress
 set(handles.hPatch,'XData',[0 0 0 0]);
 % use tic so that we can correctly update the progress
 tic;
 % start the timer
 start(handles.timerProgress);

That just leaves the timerProgressCallback which can be defined as

 function timerProgressCallback(hObject, eventdata, hFigure)
 handles = guidata(hFigure); 
 if ~isempty(handles)
    periodQuery    = get(handles.timerQuery,'Period');
    percentComplete = double(toc)/periodQuery;
    set(handles.hPatch,'XData',[0 percentComplete percentComplete 0]);
 end

We use toc and the period of the query timer to determine the progress and so how much of the patch to draw.

Try the above and see what happens! (See the attached for a working example.)

Related Solutions

MATLAB: Stop timer

Your timer function @axes1.handles is completly invalid, it's no function.

Also the way you start and stop the timer isn't correct, should give you too many errors.

Here's a GUI that I made with GUIDE, the fig file is just one axes and one pushbutton, the m file code is:

function varargout = rottest(varargin)
% ROTTEST M-file for rottest.fig
%      ROTTEST, by itself, creates a new ROTTEST or raises the existing
%      singleton*.
%




%      H = ROTTEST returns the handle to a new ROTTEST or the handle to
%      the existing singleton*.
%
%      ROTTEST('CALLBACK',hObject,eventData,handles,...) calls the local
%      function named CALLBACK in ROTTEST.M with the given input arguments.
%
%      ROTTEST('Property','Value',...) creates a new ROTTEST or raises the
%      existing singleton*.  Starting from the left, property value pairs are
%      applied to the GUI before rottest_OpeningFcn gets called.  An
%      unrecognized property name or invalid value makes property application
%      stop.  All inputs are passed to rottest_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 rottest
% Last Modified by GUIDE v2.5 04-Jun-2011 18:27:20
% Begin initialization code - DO NOT EDIT
gui_Singleton = 1;
gui_State = struct('gui_Name',       mfilename, ...
                   'gui_Singleton',  gui_Singleton, ...
                   'gui_OpeningFcn', @rottest_OpeningFcn, ...
                   'gui_OutputFcn',  @rottest_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 rottest is made visible.
function rottest_OpeningFcn(hObject, eventdata, handles, varargin)
% This function has no output args, see OutputFcn.
% hObject    handle to figure

% eventdata  reserved - to be defined in a future version of MATLAB



% handles    structure with handles and user data (see GUIDATA)



% varargin   command line arguments to rottest (see VARARGIN)
% Choose default command line output for rottest
handles.output = hObject;
spy %just to put something in the axes so we can see it rotating
MyTimer=timer('TimerFcn',@RotImgFcn,'BusyMode','queue','executionmode','fixedspacing','period',0.5);
%tag the timer and axes to have easy access to their handles
set(MyTimer,'tag','MyTimer')
set(handles.axes1,'tag','MyAxes')
% Update handles structure
guidata(hObject, handles);
% UIWAIT makes rottest wait for user response (see UIRESUME)
% uiwait(handles.figure1);
% --- Outputs from this function are returned to the command line.
function varargout = rottest_OutputFcn(hObject, eventdata, 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;
% --- Executes on button press in pushbutton1.
function pushbutton1_Callback(hObject, eventdata, handles)
% 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)
MyTimer=timerfind('tag','MyTimer');
MyTimerStatus=get(MyTimer,'Running');
if strcmp(MyTimerStatus,'off')
start(MyTimer)
else
stop(MyTimer)
end
function RotImgFcn(a,b)
%this function does the rotation
camorbit(findall(0,'tag','MyAxes'),1,0,'data',[0 0 1]); 
% --- Executes when user attempts to close figure1.
function figure1_CloseRequestFcn(hObject, eventdata, handles)
% hObject    handle to figure1 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)
% when the user closes the GUI it stops the timer if it is running
% and deletes the timer from memory
MyTimer=timerfind('tag','MyTimer');
MyTimerStatus=get(MyTimer,'Running');
if strcmp(MyTimerStatus,'on')
stop(MyTimer)
end
delete(timerfind('tag','MyTimer')); %delete our timer
%delete(timerfindall) %delete all timer objects
% Hint: delete(hObject) closes the figure
delete(hObject);

MATLAB: Displaying Timer Function in Graph

sufyan - suppose that your timer starts when you press the start button in your GUI. The pushbutton callback would look something like

 function start_Callback(hObject, eventdata, handles)
 handles.timer = timer('Name','MyTimer',               ...
                       'Period',1.0,                   ... 
                       'StartDelay',0,                 ... 
                       'TasksToExecute',inf,           ... 
                       'ExecutionMode','fixedSpacing', ...
                       'TimerFcn',{@timerCallback,handles.figure1}); 
 guidata(hObject,handles);
 start(handles.timer);

The above timer will fire (roughly) every second. Note how we pass the GUI figure handle as an input to the timerCallback function. This is necessary so that we can access the handles structure (from there) to (potentially) update the axes with new data. The callback can be defined as

 function [] = timerCallback(~,~,guiHandle)
 if ~isempty(guiHandle)
      % get the handles
      handles = guidata(guiHandle);
      if ~isempty(handles)
          % use EEG handles.data (?) to update the axes
          % if new data, then update the axes
      end
  end

In the above, we get the handles structure using guihandles so that we can get the current set of data in the axes control. In your stop button callback, you would then stop the timer

 function stop_Callback(hObject, eventdata, handles)
 if isfield(handles, 'timer')
     stop(handles.timer);
 end

Best Answer

Related Solutions

MATLAB: Stop timer

MATLAB: Displaying Timer Function in Graph

Related Question