This is expected behavior for SelectCallback. As a workaround, you can use the "dbstack" function inside of the callback function to determine if code generation is occurring when the callback is being triggered. For example:
function mySelectCallback(hDlg, hSrc)
s = dbstack;
if ~ismember('build_target.p',{s.file})
disp('Running SelectCallback!!!\n');
% perform callback function logic as intended here
else
% do nothing if 'build_target.p' is in the callstack
end
end
