Appeler une interface 2 à partir d'une interface 1

slt à tous
mon problème est le suivant
j'ai une interface 1 ou en arrière plan il ya une image
quand j'appelle l'interface 2 à partir de l'interface 1, l'image d’arrière plan de l'interface 1 apparaît dans l'interface 2.

comment je peux faire pour que cette image n'apparaisse plus dans mon interface 2
Merci

Bonjour,

Peux-tu nous montrer le morceau de code qui correspond à l'implantation de l'image en tant qu'arrière-plan de la figure 1 ?

Code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
function varargout = accueil(varargin)
% ACCUEIL Application M-file for accueil.fig
%    FIG = ACCUEIL launch accueil GUI.
%    ACCUEIL('callback_name', ...) invoke the named callback.
 
% Last Modified by GUIDE v2.0 18-Sep-2014 20:01:17
 
if nargin == 0  % LAUNCH GUI
 
 
	fig = openfig(mfilename,'reuse');
 
	% Generate a structure of handles to pass to callbacks, and store it. 
	handles = guihandles(fig);
	guidata(fig, handles);
 
 
 
	if nargout > 0
		varargout{1} = fig;
	end
 
elseif ischar(varargin{1}) % INVOKE NAMED SUBFUNCTION OR CALLBACK
 
	try
		if (nargout)
			[varargout{1:nargout}] = feval(varargin{:}); % FEVAL switchyard
		else
			feval(varargin{:}); % FEVAL switchyard
		end
	catch
		disp(lasterr);
	end
 
ax = axes('Position', [0.002 0.773 0.209 0.225]);  % Création d'un objet Axes prenant toute la fenêtre
X = imread('3IAC.BMP', 'bmp');  % Charge l'image
image(X);
axis image;
axis off;
 
ax = axes('Position', [0.226 0.102 0.562 0.627]);  % Création d'un objet Axes prenant toute la fenêtre
X = imread('nodal.jpg', 'JPG');  % Charge l'image
imagesc(X, 'Parent', ax)  % Affiche l'image 
set(ax, 'Visible', 'off');
 
ax = axes('Position', [0.783 0.777 0.207 0.221]);  % Création d'un objet Axes prenant toute la fenêtre
X = imread('telis.png', 'PNG');  % Charge l'image
imagesc(X, 'Parent', ax)  % Affiche l'image 
set(ax, 'Visible', 'off');
end
 
 
%| ABOUT CALLBACKS:
%| GUIDE automatically appends subfunction prototypes to this file, and 
%| sets objects' callback properties to call them through the FEVAL 
%| switchyard above. This comment describes that mechanism.
%|
%| Each callback subfunction declaration has the following form:
%| <SUBFUNCTION_NAME>(H, EVENTDATA, HANDLES, VARARGIN)
%|
%| The subfunction name is composed using the object's Tag and the 
%| callback type separated by '_', e.g. 'slider2_Callback',
%| 'figure1_CloseRequestFcn', 'axis1_ButtondownFcn'.
%|
%| H is the callback object's handle (obtained using GCBO).
%|
%| EVENTDATA is empty, but reserved for future use.
%|
%| HANDLES is a structure containing handles of components in GUI using
%| tags as fieldnames, e.g. handles.figure1, handles.slider2. This
%| structure is created at GUI startup using GUIHANDLES and stored in
%| the figure's application data using GUIDATA. A copy of the structure
%| is passed to each callback.  You can store additional information in
%| this structure at GUI startup, and you can change the structure
%| during callbacks.  Call guidata(h, handles) after changing your
%| copy to replace the stored original so that subsequent callbacks see
%| the updates. Type "help guihandles" and "help guidata" for more
%| information.
%|
%| VARARGIN contains any extra arguments you have passed to the
%| callback. Specify the extra arguments by editing the callback
%| property in the inspector. By default, GUIDE sets the property to:
%| <MFILENAME>('<SUBFUNCTION_NAME>', gcbo, [], guidata(gcbo))
%| Add any extra arguments after the last argument, before the final
%| closing parenthesis.
 
 
 
 
 
% --------------------------------------------------------------------
function varargout = edit1_Callback(h, eventdata, handles, varargin)
 
 
 
 
% --------------------------------------------------------------------
function varargout = edit2_Callback(h, eventdata, handles, varargin)
 
 
 
 
% --------------------------------------------------------------------
function varargout = edit3_Callback(h, eventdata, handles, varargin)
 
 
 
 
% --------------------------------------------------------------------
function varargout = edit4_Callback(h, eventdata, handles, varargin)
 
 
 
 
% --------------------------------------------------------------------
function varargout = edit5_Callback(h, eventdata, handles, varargin)
 
 
 
 
% --------------------------------------------------------------------
function varargout = edit6_Callback(h, eventdata, handles, varargin)
 
 
 
 
% --------------------------------------------------------------------
function varargout = pushbutton2_Callback(h, eventdata, handles, varargin)
 
h=findobj(gcf,'tag','edit2');
login = get(h,'String');
 
h=findobj(gcf,'tag','edit6');
mdp = get(h,'String');
 
if strcmp(login,'cedric') & strcmp(mdp,'cedric')
    close(gcf);
    %info_site;
    configuration;
else
 
 end
 
 
 
 
% --------------------------------------------------------------------
function varargout = edit6_CreateFcn(h, eventdata, handles, varargin)
if ispc & isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor'))
    set(hObject,'BackgroundColor','white');
end

Sans certitude aucune, peut être qu'un

Code:

clf(fig,'reset')

ajouté au tout début du code correspondant à la deuxième interface pourrait fonctionner (avec fig le handle de ta figure 2).