However, with TightInset I was able to improve my old crop_figure. MATLAB doesn't provide a crop-figure function (Windows platforms).MLINT could at least have given me a warning. The Mathworks calls MATLAB a high level language and ask me to handle this "feature" of PRINT. OK, I hadn't made sure "all" units were set to normalized before exporting/printing. Handle graphic objects of the Trellis Display are dislocated on the printout.I have to create the strip before the bar graph (or better use UISTACK). OK, the order in which axes are created is important. Adjusting the positions doesn't really help. The "Trellis strip" above the bar graph interferes with the box of the bar graph.Some elements of the Trellis Display are not displayed on screen.Another failure to integrate functionality: validatestring can handle abbreviated inputs nicely, but if you use it as a validation function for inputParser the information as to which possible input whas given is lost, and you have to call it again on the parsed results.I can work round this with a wrapper function that catches the error but integrated design would have avoided the need. my input could be empty, or a row vector of length 3). That means that you can't combine two calls to it into a single expression for a validation function (e.g. For example validateattributes always throws an error for invalid inputs, rather than returning a result. The functions don't work nicely together. The documentated functionality appears to be the same, so there was no need for the change, but this is the biggest cause of users of old versions to run into trouble with my code on the FEX.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |