Documentation

Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
visionx:eplug_guide [2020/06/05 16:58]
cduncan [License and Trial]
visionx:eplug_guide [2020/06/05 17:06]
cduncan [Go To Complement Class]
Line 67: Line 67:
 ===== Commands ===== ===== Commands =====
  
-[[https://​eplug.sibvisions.com/​|EPlug]] provides various commands which can be used to navigate the project. These are either available from the context menu on a source fileor can be assigned custom keybindings through the Eclipse preferences.+[[https://​eplug.sibvisions.com/​|EPlug]] provides various commands which can be used to navigate the project. These are either available from the context menu on a source file or can be assigned custom keybindings through the Eclipse preferences.
  
 {{:​visionx:​eplug_guide:​eplug-context-menu.png?​nolink|The EPlug context menu that can be accessed through the editor.}} {{:​visionx:​eplug_guide:​eplug-context-menu.png?​nolink|The EPlug context menu that can be accessed through the editor.}}
Line 79: Line 79:
 Opens the complement class of the currently open file. Opens the complement class of the currently open file.
  
-The complement class is the "​counterpart"​ of every class on the client or server. So when invoked on a workscreen (client-side),​ it will open the server-side LCO classand vice versa.+The complement class is the "​counterpart"​ of every class on the client or server. Sowhen invoked on a workscreen (client-side),​ it will open the server-side LCO class and vice versa.
  
 ==== Go To application.xml ==== ==== Go To application.xml ====
This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information