You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should check if the user is exporting from a version of MATLAB which supports the language being exported due to the following scenario:
User is in older version of MATLAB which does not support all the languages in the most up to date version. (Language ABC is not included in their version.)
User imports scheme X which contains additional languages, with every language specified in the .prf file (including ABC). Now user has settings saved in matlab.prf for languages which their GUI will not present.
User designs a new scheme for MATLAB syntax.
User ignores advised instructions for the creation of a scheme with additional languages (which specify to create MATLAB syntax, export, import, fix additional languages) and designs the additional languages colours without importing the MATLAB syntax as a base.
User exports the colour scheme to Y.prf, with additional languages included. The exported scheme will have colours for ABC from scheme X because these settings will exist in matlab.prf, but they do not match the background etc specified for their scheme, Y.
User distributes their scheme, Y. Others import it into up-to-date MATLAB. Colours for ABC syntax do not work.
This scenario will presumably happen eventually, but it is not a high priority. I anticipate the majority of designers will not do anything for the Additional Languages.
In order to do this, we first need to know which MATLAB versions introduced support for which language syntax. As far as I am aware, MathWorks do not indicate this in their changelog.
We should check if the user is exporting from a version of MATLAB which supports the language being exported due to the following scenario:
This scenario will presumably happen eventually, but it is not a high priority. I anticipate the majority of designers will not do anything for the Additional Languages.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: