Hello Vladimir,
Could you possibly describe your problem with the "Step Into" functionality more precisely?
In case of debugging features available in MDT we are not able to solve some problems due to the limitations of modules/classes that are provided with Smallworld Core (4.1 or higher) for debugging purposes. Some of the issues are related to "Step Into" functionality as well. To be more precise I will try to describe briefly those limitations:
"Step Into" will work like "Step Over" if you try to jump into internal expression and i.e. related method definition does not have sources available in provided file path.
If you have more than one internal expression, and sources are available, then "Step Into" will jump only to the first one and after all it will jump to the next "outer" expression (it won't step into the next internal expressions)
Generally speaking, MDT uses the same base/support classes that are also used by "Very Simple Debugger" available in development tools from Smallworld Core installation and we have to deal with some related limitations. If you can check out a behavior of "Very Simple Debugger" in the same situation and the effect will be the same in MDT then it means that the Smallworld Core support classes are the ones to blame.
With best regards.