Yair Altman

Robert - you are correct: there is no need for the aerospace blockset - it got in there by some mistake

@Ward - thanks - I believe that you may be right. This has no effect unless there are several overlapping/similar results in the filtering process, which is very rare. But in such rare cases, your fix would solve a problem of returning both the parent and the child handles.

Thanks! Just another tiny issue that I came accross when using the new version. It seems that, under Linux, copyfile() may return status=1 even if the .bak file could not be created due to the lack of write permission in the relevant folder. At least in my Debian squeeze system I get status=1 but msg='Operation not permitted' and the .bak file is not created. Is this a MATLAB bug? So there is the possibility that the owner of TC.xml can now rewrite TC.xml (by changing permissions automatically) but fails to create a backup copy, as the toolbox/local directory is read-only by default. For the sake of safety I would test that the msg returned by copyfile is empty as well as checking that status is not zero.

Really helpful stuff. And the technical explanations at your blog are incredibly insightful. Thanks a lot for sharing this. I would suggest just two very minor modifications:

- Adding the MCOSPCG and MCOSCLASS options
- Under unix systems, automatically changing the permissions of the xml file before editing it. Usually you will be the owner of that file but by default its permissions are set to read-only. You could change the permissions back to read-only after the editing.

Robert - you are correct: there is no need for the aerospace blockset - it got in there by some mistake