How to show a picture only while pressing the button (Matlab GUIDE) - matlab

I am trying to create a Matlab GUI using GUIDE. I want to insert a picture with the picture shown only while I am pressing a button (Callback function) and show the default picture once the button is released. How can I implement this? I use axes to display the picture at the mentioned location
function mc_right_Callback(hObject, eventdata, handles)
% hObject handle to mc_right (see GCBO)
% eventdata reserved - to be defined in a future version of MATLAB
% handles structure with handles and user data (see GUIDATA)
matlabImage2 = imread('Coor2.png');
imshow(matlabImage2, 'Parent', handles.axes7);
%Vxm_Port_Send(handles.port_handle,sprintf('F,C,I3M-%d,R',handles.x_steps)); % Move along +x (right)

The problem is that MATLAB uicontrols don't allow you to create separate callback functions that execute on a button press or button release. For example, a push button will execute its Callback function on a button release. It also has a ButtonDownFcn function that will execute on a button press, but this callback is only active when the Enable property is set to 'off' or 'inactive', in which case the Callback function is disabled. In other words, you can't use the ButtonDownFcn and Callback together to get responses to both button presses and releases, respectively.
However...
The figure window does have a way to specify separate callback functions for button presses, button releases, and even mouse motion or scroll wheel activity. This is how I usually overcome shortcomings in uicontrol behavior: I define figure-level callbacks that execute when they are over certain parts of the window. Here's an example:
function press_release
% Load a sample image:
imgData = imread('peppers.png');
% Create the figure and graphics objects:
hFigure = figure('WindowButtonDownFcn', #press_fcn, ...
'WindowButtonUpFcn', #release_fcn);
hImage = image(imgData, 'Visible', 'off');
hButton = uicontrol(hFigure, 'Style', 'pushbutton', ...
'Position', [10 10 30 30], ...
'Enable', 'inactive');
function press_fcn(~, ~)
if isequal(hButton, get(hFigure, 'CurrentObject'))
set(hImage, 'Visible', 'on');
set(hButton, 'Value', 1);
end
end
function release_fcn(~, ~)
set(hImage, 'Visible', 'off');
set(hButton, 'Value', 0);
end
end
When you run the above, it will create a window with an axes and a small button in the lower left corner. The button has no callbacks defined. When you click the mouse anywhere but over the button nothing happens. However, when you click the mouse over the button (making it the CurrentObject for the figure) the image will become visible and the button will depress while you are holding the button down. Releasing the button makes the image invisible again and the button appears normal. Essentially, the button is just a dummy that does nothing at all except give the user the illusion that they are pressing it to make things happen. It's really the figure callbacks doing the work.

Related

Making push button visible in maingui after clicking close push button in subgui

I have a main gui with 2 pushbuttons. The first button opens a subgui and the other button is the "run" pushbutton which is 'Enable'=Off. It's grey and not clickable. I know I can turn the enable "on" with this command: set(handles.start_pushbutton,'Enable','on');
I execute this command in the subgui by clicking the "Close" button.
function pushbutton_Beenden_Callback(hObject, eventdata, handles)
closereq;
set(handles.start_pushbutton,'Enable','on');
How can I tell him to set the command but in the main gui?
Error: Reference to non-existent field 'start_pushbutton'
Since your start_pushbutton is defined in the main GUI, it is not available in the handles structure of your sub GUI. You'll want to either store a handle to your main GUI within your sub GUI's handles struct .
% From within your main GUI
hfig = subGUI();
% Add the (current) main GUI handle to the subGUI handles
handles = guidata(hfig);
handles.parentGUI = hObject;
guidata(hfig, handles);
Then from within the subGUI callback:
% Get the GUIDATA from the parent GUI
parentdata = guidata(handles.parentGUI);
% Change the pushbutton property
set(parentdata.start_pushbutton, 'Enable', 'on');
Or you can use a Tag on the uicontrol so that you can find it from the other GUI.
% From the GUI that has this button
uicontrol('Tag', 'MyPushButton')
% From the button that was defined in the parent GUI
button = findall(0, 'Tag', 'MyPushButton');
set(button, 'Enable', 'on')

How to detect a push button press and release in matlab

i have a GUI based in matlab 2015 to code
when i push/ press the button one of edit box data keeps changing but i want its value to keep on changing according to my call back until i release it
for now i have to keep on clicking my push button again and again which changes my edit box value
Kindly suggest me a workarround
% --- Executes on button press in pushbutton27.
function pushbutton27_Callback(hObject, eventdata, handles)
% hObject handle to pushbutton27 (see GCBO)
% eventdata reserved - to be defined in a future version of MATLAB
% handles structure with handles and user data (see GUIDATA)
Freq = (str2double(get(handles.edit4,'String')))+ 0.001;
if Freq > 20
set(handles.edit4,'String','20');
else
set(handles.edit4,'String',num2str(Freq));
end
uicontrol has only the Callback and ButtonDownFcn properties that respond to mouse clicks. If the property Enable of the uicontrol is set to 'on', only the function specified in Callback reacts to left-clicks. If the property is set to 'off' or 'inactive' it also reacts to right-clicks. Because for inactive uicontrols you cannot change the Value by clicking on it, I don't see a direct solution using uicontrol.
A solution is to use the figure's WindowButtonDownFcn and WindowButtonUpFcn properties. For the button down you could use something like:
function buttondown(hobj,~,hedit)
hobj.UserData = true;
while hobj.UserData
pause(0.2); % put a pause so it doesnt change too fast
hedit.String = datestr(now); % you can set it to anything you want here
end
end
For the button up:
function buttonup(hobj,~)
hObj.UserData = false;
end
Of course, if you have multiple buttons that have to work this way, in the buttondown function you must test where the cursor's position is that by checking the CurrentPoint property.

Matlab getrect function - How to skip the mouse input

In Matlab GUI, I need a user mouse input as a rectangle that I have to plot on the axes1.
For this, I have code below:
axes(handles.axes1);
filename = 'A';
img = imread(filename);
imshow(img);
hold on;
rect_cord = getrect(handles.axes1);
rectangle('Curvature', [0 0],'Position', [rect_cord],'EdgeColor',[1 0 0]);
This code runs fine (takes user input and plots the rectangle). However, for some images I don't want to get the user input from mouse (using getrect). In this case, how to skip the getrect function and move on to next image?
I have a pushbutton ("next"), I want to show next image when push button is pressed instead of taking user input.
Thanks,
I will try to rephrase and modify a bit: you want to draw a rectangle only if one clicks on the axes or image.
Therefore:
First of all I would suggest to put the getrect-part into another function. This function should only be triggered if one clicks on the image. The so called "ButtownDownFcn" seems to be suitable for this job. When using GUIDE, you will find it double-clicking on the axes within the property-inspector that is popping up.
Then put the getrect-part into this function:
function axes1_ButtonDownFcn(hObject, eventdata, handles)
% hObject handle to axes1 (see GCBO)
% eventdata reserved - to be defined in a future version of MATLAB
% handles structure with handles and user data (see GUIDATA)
rect_cord = getrect(handles.axes1);
rectangle('Curvature', [0 0],'Position', [rect_cord],'EdgeColor',[1 0 0]);
Now I thought that this is all that has to be done. But testing this with a plot or image within the axes prooved me wrong :o
Sadly one has to redirect the children of the axes to this function, because by default, it is only assigned to the background of the axes (=the blank axes).
by searching the net, I found the following solution here:
Matlab in Chemical Engineering: Interacting with your graph through mouse clicks
It works like this:
when plotting the image, you have to add the line
% and we also have to attach the function to the children, in this
% case that is the line in the axes.
set(get(gca,'Children'),'ButtonDownFcn', #mouseclick_callback)
Hope that helps!

Handles disappear when I create axis in GUI

I'm working on a GUI (created with guide in Matlab) with two axes and two pushbuttons. When the user presses pushbutton1 I want to display an image on axes1 and when the user presses pushbutton2 I want to display an image on axis2.
This is my code:
function pushbutton1_Callback(hObject, eventdata, handles)
axes(handles.axes1);
imagesc(table(:,:,1));colormap(gray),axis('square');
guidata(hObject,handles);
function pushbutton2_Callback(hObject, eventdata, handles)
axes(handles.axes2);
imagesc(table(:,:,1));colormap(gray),axis('square');
guidata(hObject,handles);
This code works fine only when the user presses the buttons for the first time. When he does it again, the program crashes and I get the following error: "Reference to non-existent field 'axes1'".
When I display all handles, I see that the handle "axes1" is missing indeed.
I don't get this error when I change the NextPlot property of my axes to "new". However, in that case I can't display images at all. I mean I don't get errors, but I one forth of the image (top right corner) is grey and the rest is white. The plotrange in both dimensions is (0,1), instead of (0,2000). It seems to me that this is only one pixel of my image.
What am I doing wrong?
I had a similar problem. I used a timer object and passed the different axes in a handle object which worked. My application was getting data from multiple cameras in realtime.

Using addlister in MATLAB GUI seems to "delete" existing handles

I am quite new to MATLAB GUI programming (using GUIDE sorry) and I have the following issue: The GUI displays on an axis an image sequence stored in a cell array. I have a couple of pushbuttons and a slider to scroll through the sequence. In order to get a 'continuous slider' I use a listener, which kind of works but creates some problems:
1) When I press the slider, a figure is created and the first frame of the sequence is displayed in it, but as I move the slider the sequence is displayed in the axis of my GUI (which is what I want) and the figure becomes empty. Can anybody tell me why this figure is created and how can I avoid it?
2) Once I press the slider button and thus use the listener, all handles inside the GUI are not functionnal as Matlab does not recognize them and I'm stuck with a functionnal slider/display but I can't use the pushbuttons.
Any ideas on why this happens? Here is the code I use in the Create Function of the slider:
function slider2_Frame_Video_Callback(hObject, eventdata, handles)
hListener = addlistener(hObject,'ContinuousValueChange',#(a,b) slider2_Frame_Video_Callback(hObject, eventdata, handles)); % a and b are dummy arguments
guidata(hObject,handles)
In the slider callback, the code looks like this (basically imshow in the current axis):
axes(hAxis)
imshow(Movie{frame},'parent',hAxis);
drawnow
% This does not work either as handles.edit_FrameNumber is not recognized by Matlab
set(handles.edit_FrameNumber, 'String', frame);
guidata(hObject,handles);
Any hints are welcome thanks!
I wonder if part of the problem is that a listener is being instantiated each time the user moves the slider since the listener code is within this callback AND that the callback being provided to the listener (seems like some kind of strange back-and-forth there). So every time the user releases the mouse button after a slide, a new listener is created. This may be causing some problems with the other buttons not being responsive.
Rather than instantiating the listener there, I would do this in the Opening_Fcn of your GUI:
% --- Executes just before frameSlider is made visible.
function frameSlider_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 frameSlider (see VARARGIN)
% Choose default command line output for frameSlider
handles.output = hObject;
if ~isfield(handles,'hListener')
handles.hListener = ...
addlistener(handles.slider1,'ContinuousValueChange',#respondToContSlideCallback);
end
% Update handles structure
guidata(hObject, handles);
My GUI is named frameSlider; yours will be something else. The above creates one listener with a callback to a function that you will need to define in the same *.m file, respondToContSlideCallback.
A sample body for the callback that is to respond to the continuous slide is
% --- Executes on slider movement.
function respondToContSlideCallback(hObject, eventdata)
% hObject handle to slider1 (see GCBO)
% eventdata reserved - to be defined in a future version of MATLAB
% Hints: get(hObject,'Value') returns position of slider
% get(hObject,'Min') and get(hObject,'Max') to determine range of slider
% first we need the handles structure which we can get from hObject
handles = guidata(hObject);
% test to display the current value along the slider
disp(['at slider coordinate ' num2str(get(hObject,'Value'))]);
If you run this code, the Command Window will display continuously the slider coordinate as you move the slider from end to end.
Your above code has a Movies cell array. How is that being accessed by your callback? Is it a global variable or ..? Where does hist come from? If Movies is the result of some other function call, then it can be saved to handles too (in whichever location it gets loaded from file). I suppose you will also have to map the slider control coordinates to the number of frames that you have (though maybe you have already done this?).