How to prevent trimming of characters from visdiff output?

4 次查看（过去 30 天）

Jayanth Suresh 2023-1-25

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1900310-how-to-prevent-trimming-of-characters-from-visdiff-output

评论： Jayanth Suresh 2023-2-28

comparisonReportCharacterTrim.png

I have developed a MATLAB app programatically and wanted to compare it with a different version and get a "comparison" output from visdiff for the same. The idea is to parse through the output comparison and add any buttons, tabs or tables programatically since MATLAB merge mode is not very reliable for my case.

When I use

comparison = visdiff('file1.m', 'file2.m');

I do get an output in the form of character array but some of the classes for the components are trimmed out. For eg, matlab.ui.container.Button is trimmed and displayed only as matlab.ui.container.Bu

More examples are shown in the figure.

Are there any available options here to prevent that from happening?

4 个评论
显示 2更早的评论隐藏 2更早的评论

dpb 2023-1-25

编辑：dpb 2023-1-25

在 MATLAB Online 中打开

I don't find anything in the command line version of visdiff but there is an option in the interactive "Comparison Tool" it appears to change column widths...

There's also the fallback to revert to the OS command line tools -- "fc" on Windows or "diff" on 'nix. Not sure about Mac

ADDENDUM:

How do you manage to generate a LHS assignment from that syntax for m-file comparisons? The visdiff documentation explicitly states that's only possible for comparison of Simulink models and in trying to test here, I find it apparently is true...

>> vdiff=visdiff('app2.mlapp','app1.mlapp');
Error using visdiff (line 81)
Incompatible file formats: No method to compare "C:\Users\Duane\Documents\MATLAB\Answers\app2.mlapp" and "C:\Users\Duane\Documents\MATLAB\Answers\app1.mlapp" outside of the
Comparison Tool GUI. 
>>

The comparison tool opens if don't assign to a LHS, but errors as above otherwise...I've never used it (didn't even know it existed, actually) but don't see any way to get the same result as you're showing...

dpb 2023-1-26

The latter must be an undocumented change since R2020b...it fails on m-files here, too, so can't see anything except the display version. The comparison report engine is also different for .mlapp and .m files here; only a binary dump shows up for m-files while the enhanced comparison/merge facility is there for appliction files.

Don't guess I can give any further help/advice, sorry...I'm not in position to upgrade at the moment; that's going to have to wait for a completion of current tasks before happening; probably at least another month.

I'd venture it's time to submit official support request; if it's undocumented behavior they may just blow it off, but there may be a workaround they'll help with if it is in an active development mode and beta testing is beneficial on their end, too.

Jayanth Suresh 2023-2-28