Thread Subject: Odd gui(de) question

I am using GUIDE to creadt a GUI. I have a Browse button set to display the final file path in an editable text field. I chose editable because I like the idea of being able to change it without having to browse again. The problem is that the String is not recorded with the get(hObject,'String) unless I actually type something in there.

Now this does make some sense to me because it is an editable text box and I have not drectly edited it by having it display something from the pushbutton. But is there a way to get to save this without having a "direct" user input?

ps. Works fine with non-editable text and I will use that if nothing else works.

OK, to append to this in I cannot get any default settings for things, mainly buttons, to output at all. If a button is not clicked by the user, no variable is saved. I have a large list of options that effect the way the final code is run, and I have had to manually set the conditions for these using

if isfield(handles.EMMAX) ==0
EEMAX = 1;
end

This however does not affect buttons that are turned off/on via other buttons (not a button group) as it still does not output the value for the changed button. To get the data out I am just using

save('handles','handles').

I

>
> if isfield(handles.EMMAX) ==0
> EEMAX = 1;
> end

The call is ISFIELD seems fishy to me, does it need 2 arguments?

To set a default string property to a handle , use SET (not GET).

Bruno

"Travis" <sinusoid2@hotmail.com> wrote in message <gu2e4a$1js$1@fred.mathworks.com>...
> I am using GUIDE to creadt a GUI. I have a Browse button set to display the final file path in an editable text field. I chose editable because I like the idea of being able to change it without having to browse again. The problem is that the String is not recorded with the get(hObject,'String) unless I actually type something in there.
>
> Now this does make some sense to me because it is an editable text box and I have not drectly edited it by having it display something from the pushbutton. But is there a way to get to save this without having a "direct" user input?
>
> ps. Works fine with non-editable text and I will use that if nothing else works.

I am not sure what you have done, but I think what you are trying to do is something like this:

%PATH TYPER
        jdatapath=uicontrol('Style','edit',...
            'horizontalAlignment','center',...
            'FontWeight','bold',...
            'String',' Path to File',...
            'Position',[c2,r1,300,30],...
            'Value',2500);
        
        %File Browser
        jbrowse=uicontrol('Style','pushbutton',...
            'String','Browse',...
            'Position',[c2+300+10,r1,50,30],...
            'Callback',{@browse_button_Callback});

function browse_button_Callback(object,eventdata)

[cat,carrot]=uigetfile('*.lvm','Select Data File')
browsedatapathway=strcat(carrot,cat)
set(jdatapath,'String',browsedatapathway)

end

if you are using GUIDE, then guide has created the first parts for you, but the important thing is that you use set(handles.editbox,'String',browsedatapathway)

when you try to get(handles.editbox,'String') later, you will retrieve the pathway you selected with the browse function.

hope I haven't misunderstood your question!

--John

Bruno,

What do you mean 2 arguments? I am trying to retrieve the default arguments, I can set them, visually at least, just fine, it just doesn't kick it out when i use sav('handles','handles').

John,

You have no misunderstood my question at all. I think I have exaclty what you are suggesting. Here is the code I have, sorry for not including it in my original post.....

% --- Executes on button press in CoefBrowse.
function CoefBrowse_Callback(hObject, eventdata, handles)
% hObject handle to CoefBrowse (see GCBO)
% eventdata reserved - to be defined in a future version of MATLAB
% handles structure with handles and user data (see GUIDATA)
[CoefFile,CoefPath] = uigetfile('*.mat','Select the Correction Coefficient Matrix');
PathCoef = [CoefPath CoefFile];

set(handles.CoefLoc,'String',PathCoef)


function CoefLoc_Callback(hObject, eventdata, handles)
% hObject handle to CoefLoc (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 CoefLoc as text
% str2double(get(hObject,'String')) returns contents of CoefLoc as a double
MatLoc = get(hObject,'String');

handles.MatLoc = MatLoc;
guidata(hObject,handles)

"Travis " <sinusoid2@hotmail.com> wrote in message <gu45nm$bng$1@fred.mathworks.com>...
> Bruno,
>
> What do you mean 2 arguments?

You wrote somewhere:

>> isfield(handles.EMMAX)

??? Error using ==> isfield
Not enough input arguments.

>> help isfield
 ISFIELD True if field is in structure array.
    ISFIELD(S,FIELD) returns true if the string FIELD is the name of a
    field in the structure array S.
...

I have no idea what kind of code you post above, it does not even work let alone giving expected behavior.

Bruno

"Bruno Luong" <b.luong@fogale.findmycountry> wrote in message <gu4eu1$73b$1@fred.mathworks.com>...
> "Travis " <sinusoid2@hotmail.com> wrote in message <gu45nm$bng$1@fred.mathworks.com>...
> > Bruno,
> >
> > What do you mean 2 arguments?
>
> You wrote somewhere:
>
> >> isfield(handles.EMMAX)
>
> ??? Error using ==> isfield
> Not enough input arguments.
>
> >> help isfield
> ISFIELD True if field is in structure array.
> ISFIELD(S,FIELD) returns true if the string FIELD is the name of a
> field in the structure array S.
> ...
>
> I have no idea what kind of code you post above, it does not even work let alone giving expected behavior.
>
> Bruno

Since the handles structure does not export the default position of buttons, etc. If the field EEMAX does not exist it must be in its default state (1); if it does exist then keep the value that it has (0).

>
> Since the handles structure does not export the default position of buttons, etc. If the field EEMAX does not exist it must be in its default state (1); if it does exist then keep the value that it has (0).

OK now you confuse me big time. I give up, sorry.

Good luck,

Bruno

"Bruno Luong" <b.luong@fogale.findmycountry> wrote in message <gu4krd$44f$1@fred.mathworks.com>...
> >
> > Since the handles structure does not export the default position of buttons, etc. If the field EEMAX does not exist it must be in its default state (1); if it does exist then keep the value that it has (0).
>
> OK now you confuse me big time. I give up, sorry.
>
> Good luck,
>
> Bruno

hehe, I have confused the great Bruno!! Thank you for trying, and for previous help with other things.

>
> John,
>
> You have no misunderstood my question at all. I think I have exaclty what you are suggesting. Here is the code I have, sorry for not including it in my original post.....

HERE'S WHAT I WOULD DO :

 % --- Executes on button press in CoefBrowse.
 function CoefBrowse_Callback(hObject, eventdata, handles)
 % hObject handle to CoefBrowse (see GCBO)
 % eventdata reserved - to be defined in a future version of MATLAB
 % handles structure with handles and user data (see GUIDATA)
 [CoefFile,CoefPath] = uigetfile('*.mat','Select the Correction Coefficient Matrix');
 PathCoef = [CoefPath CoefFile];

%%%%%NEW
 COMBINEDPATHCOEF=STRCAT(CoefPath,CoefFile);
 set(handles.CoefLoc,'String',COMBINEDPATHCOEF)
 %%%%%NEW
 
 function CoefLoc_Callback(hObject, eventdata, handles)
 % hObject handle to CoefLoc (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 CoefLoc as text
 % str2double(get(hObject,'String')) returns contents of CoefLoc as a double
 MatLoc = get(hObject,'String');
 
 handles.MatLoc = MatLoc;
 guidata(hObject,handles)


I think this should fix it. You need to combine the two strings you get from uigetfile. I don't know about this MatLoc thing. If you are accessing it this way and it works, that's cool, but with a GUIDE gui you don't have to use guidata. You can just say

variable=get(objecthandle ,'property')
set(otherobjecthandle,'property',variable)

hope you get it straightened out!

--John

"Travis " <sinusoid2@hotmail.com> wrote in message
news:gu4jal$nk4$1@fred.mathworks.com...
> "Bruno Luong" <b.luong@fogale.findmycountry> wrote in message
> <gu4eu1$73b$1@fred.mathworks.com>...
>> "Travis " <sinusoid2@hotmail.com> wrote in message
>> <gu45nm$bng$1@fred.mathworks.com>...
>> > Bruno,
>> >
>> > What do you mean 2 arguments?
>>
>> You wrote somewhere:
>>
>> >> isfield(handles.EMMAX)
>>
>> ??? Error using ==> isfield
>> Not enough input arguments.
>>
>> >> help isfield
>> ISFIELD True if field is in structure array.
>> ISFIELD(S,FIELD) returns true if the string FIELD is the name of a
>> field in the structure array S.
>> ...
>>
>> I have no idea what kind of code you post above, it does not even work
>> let alone giving expected behavior.
>>
>> Bruno
>
> Since the handles structure does not export the default position of
> buttons, etc. If the field EEMAX does not exist it must be in its default
> state (1); if it does exist then keep the value that it has (0).

I understand that's what you want. But that's not what the code you wrote
does. If the handles struct doesn't have a field named EMMAX, then this:

isfield(handles.EMMAX)

will throw an error that handles doesn't have a field named EMMAX (because
it's trying to get the EMMAX field of the handles structure to pass it into
the ISFIELD function.) You want:

if isfield(handles, 'EMMAX')
    % do stuff that depends on handles having a field EMMAX
end

That's what Bruno was asking about.

--
Steve Lord
slord@mathworks.com

"Steven Lord" <slord@mathworks.com> wrote in message
> I understand that's what you want. But that's not what the code you wrote
> does. If the handles struct doesn't have a field named EMMAX, then this:
>
> isfield(handles.EMMAX)
>
> will throw an error that handles doesn't have a field named EMMAX (because
> it's trying to get the EMMAX field of the handles structure to pass it into
> the ISFIELD function.) You want:
>
> if isfield(handles, 'EMMAX')
> % do stuff that depends on handles having a field EMMAX
> end
>
> That's what Bruno was asking about.

Steve you are exactly correct, I typed it in incorrectly. I was able to find something in the blog section on exporting the current state of the buttons and whatnot to a .mat file. Sorry for the confusion.
>
> --
> Steve Lord
> slord@mathworks.com
>

OK, just found an odd thing. I have had the Browse buttons and editable text fields working in perfect sync for a while now, but OI just found that when I hit the 'cancel' button in the browser that pops up using 'uigetdir' the editable text field dissappeared completely.

here is what I have for the button...

% --- Executes on button press in ExBrowse.
function ExBrowse_Callback(hObject, eventdata, handles)
% hObject handle to ExBrowse (see GCBO)
% eventdata reserved - to be defined in a future version of MATLAB
% handles structure with handles and user data (see GUIDATA)
[FileEx,PathEx] = uigetfile({'*.xls'; '*.xlsx'},'Select the Excitation Correction File');
global ExPath
ExPath = [PathEx FileEx];


guidata(hObject,handles);
set(handles.ExLoc,'String',ExPath);

% --- Executes on button press in EmBrowse.
function EmBrowse_Callback(hObject, eventdata%

OK, just found an odd thing. I have had the Browse buttons and editable text fields working in perfect sync for a while now, but OI just found that when I hit the 'cancel' button in the browser that pops up using 'uigetdir' the editable text field dissappeared completely.

here is what I have for the button...

% --- Executes on button press in ExBrowse.
function ExBrowse_Callback(hObject, eventdata, handles)
% hObject handle to ExBrowse (see GCBO)
% eventdata reserved - to be defined in a future version of MATLAB
% handles structure with handles and user data (see GUIDATA)
[FileEx,PathEx] = uigetfile({'*.xls'; '*.xlsx'},'Select the Excitation Correction File');
global ExPath
ExPath = [PathEx FileEx];


guidata(hObject,handles);
set(handles.ExLoc,'String',ExPath);

% --- Executes on button press in EmBrowse.
function EmBrowse_Callback(hObject, eventdata%