Child pages
  • What's New in 2020.2
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Select next sibling on pressing Shift + Left/Right 

Using Shift + Left/Right key combination it is now possible to select multiple sibling nodes. Examples include: method parameters, array literal values or statement siblings. You can then copy and paste this list into other suitable places that would accept copied nodes.


UI improvements in Diff/Merge dialog windows in VCS

The width of the editor areas is not fixed anymore, one can move the splitter in both directions. Highlighting of changes has been improved. Triangles and trapezia we had before in the spliiter area have been replaced by smooth polygons  Tooltips for the changes are displayed both in the editor area and in the splitter area.


Improved history for a root + history for a node in VCS

Existing "Show Root History" action did not always display correct results. Sometimes a revision in a history list did not correspond to any real change. In the new approach models are compared rather than files. Besides, a similar action for the node has been added.


'Show Generation Plan` action gives more details

When a model has a plan that controls its transformation, 'Show Generation Plan' action offers a handy way to understand exact steps the transformation would go through. In this EAP, the action got few improvements. Now, in addition to transformation steps, the action tells where it derived generation plan from (e.g. through a custom module facet or a devkit), gives name and a link to generation plan node (MPS-31935). Besides, transformation steps bear name of the generator module when template model name is not qualified (MPS-31354), which helps to distinguish similarly named model (MPS used to create template model named 'main' in all new generators. Having few such generators in the plan make it quite confusing). Another common complaint was that the languages excluded from a model transformation due to restrictions of a generation plan are not easily discoverable, which has been addressed as well. Languages used in the model but not covered by the associated plan are reported by 'Show Generation Plan' action now. In addition, 'Used Languages' tab in model properties warns about such languages, too (MPS-29720).

  • No labels