User Tools

Site Tools


mycnc:mycnc_screen_configuration

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
mycnc:mycnc_screen_configuration [2018/10/01 10:46]
skirillov
mycnc:mycnc_screen_configuration [2019/09/13 09:37] (current)
ivan
Line 4: Line 4:
  
 === Label === === Label ===
-=== Display === 
-=== BDisplay === 
-=== RadioDisplay === 
-=== KDisplay === 
-=== KSpinBox === 
-=== KSpinBox2 === 
-=== LED Display === 
-=== SVG Display === 
-=== Myitems Widget === 
-=== Button === 
  
-A PushButton screen item can be used on myCNC screen. A typical button definition is shown below+Labels are static text elements which are displayed as a text box (typically simple text headings/​titles/​etc). An example of such a label can be seen in the User Settings window of the 1366M4 profile, in the Oil Change tab:
  
-<code XML > +{{:​mycnc:​screen-config-003-label-mileage-scaled640.png}}
- <​gitem where="​main"​  +
- ​position="​160;​0"​ width="​80"​ height="​80"​  +
- ​image="​button-refresh"​ action="​file-refresh"​ type="​button"​ /> +
-</​code>​+
  
 +Here, the **Mileage/​Oil Change** title is a Label. The code for this label would be the following:
  
-Attributes description  +<code c><​gitem ​where="oil-change" ​ 
-  * **where** parent widget name the button placed to  + ​position="​0;​0" ​width="​490" ​height="​30"​ labelWidth="​490" ​ 
-  * **position** - X and Y position of the button inside a parent widget + ​type="​label" ​labelFgColor="##​f-title" ​ 
-  * **width** - button width in pixels + labelBgColor="##​b-title" labelFontSize="​18"​ labelFontStyle="​bold" ​ > 
-  * **height** - button height in pixels + <​message>​Mileage/​Oil Change</​message>​ 
-  * **type** - type definitionof the item (should be type="button"+ <​message_ru>​Счетчик смены масла</​message_ru>​ 
-  * **image** ​a image (icon) file in SVG format for the button +</​gitem>​ 
-  * **action** ​action for the button (which procedure will be executed if event triggered) +</​code>​
-  * **event** - event type the button is sensitive to. Event can be  +
-    * **pressed** - action is executed if the button pressed +
-    * **released** - action is executed if the button released ​ +
-    * **both** - there are separate actions (";"​ semicolon separated) for **pressed** and **released** events +
-  * **skinbase** - besides the Image file for each button there is a common **skin** SVG file for all the buttons. For selected buttons skin file can be redefined with **skinbase** attribute. This SVG file will be used as a bottom layer for the button image.+
  
 +  * **where** describes the tab that this label element will be inserted into (in this example, it's the oil-change tab)
 +  * **position** specifies the xy pixel position for the label. This position is specified not within the overall screen, but within the **where** tab (in this example, the position is specified in reference to the oil-change section).
 +  * **width** and **height** are specified in pixels. Since the entire text box will be taken up by the label, the labelWidth is equal to the overall width.
 +  * **type** assigns a category to the element that this code will display on the page. In this case, it is set to "​label"​
 +  * **labelFgColor** specifies the foreground colour of the label. The colour can be typed in directly, in the HTML RGB format, or, as in this case, with the two pound signs in front (##​f-title). This specifies to the program to retrieve this colour from Screen > Colors, or, if it is not there, it will be added to the list and can be later chosen from the Screen > Colors tab. Changes will take effect on the next reload (not instant). The following window shows an example of such a Screen > Colors list:
 +{{:​mycnc:​screen-config-009-colors.png}}
 +  * **labelFontSize** specifies the font size, **labelFontType** is set to bold in this case. **labelFontFamily** can also be specified if a particular font is required (an example of using a labelFontFamily is available in the BDisplay section on this page). If it is not specified, the default font will be used. 
 +  * **message** can be written in the required languages (which must be specified). The program will automatically display the correct message for each selected program language. ​
  
-=== XButton === 
  
-XButton is a Push Button with built in Light indicator. Light is mostly used to show a current state of CNC controller input, output pin, CNC global variable register value etc.+=== Display ===
  
-A XButton XML definition ​example is shown below +**Display** allows to show dynamic info (such as a changing value), and often works in conjunction with a Label (a label will create some title, and the dynamic changing value will be placed on the screen next to the Label as a Display). An example ​of a Display ​is the Trip Counter from the User Settings window in the 1336M4 profile:
-<code XML> +
-<gitem where="​x-mill"​  +
- ​xattr="​3;​3;​16;​16;​led;​red;​round"​  +
- ​address="​outputs"​ number="#​OUTPUT_SPINDLE"​. +
- ​position="​720;​10"​ width="​70"​ height="​70"​  +
- ​image="​M/​button-m03"​ action="​plc-run:M03/#​5524"​  +
- ​type="​xbutton"​ /> +
-</​code>​+
  
 +{{:​mycnc:​screen-config-004-trip-counter.png}}
  
-Attributes description  +The code for this element ​will look like this:
-  * **where** - parent widget name the button placed to  +
-  * **position** - X and Y position of the button inside a parent widget +
-  * **width** - button width in pixels +
-  * **height** - button height in pixels +
-  * **type** - type definitionof the item (should be type="​button"​) +
-  * **image** - a image (icon) file in SVG format ​for the button +
-  * **action** - action for the button (which procedure ​will be executed if event triggered) +
-  * **event** - event type the button is sensitive to. Event can be  +
-    * **pressed** - action is executed if the button pressed +
-    * **released** - action is executed if the button released  +
-    * **both** - there are separate actions (";"​ semicolon separated) for **pressed** and **released** events +
-  * **skinbase** - besides the Image file for each button there is a common **skin** SVG file for all the buttons. For selected buttons skin file can be redefined with **skinbase** attribute. This SVG file will be used as a bottom layer for the button image. +
-  * **xattr** - defines light positionm size and attributes - semicolon separated +
-      * X,Y position of the led/light inside the button +
-      * width and height of the led +
-      * type of light (actually ​this field is always "​led",​ reserved for future options) +
-      * shape of the standard led light. A standard shape can be "​round"​ and "​rect"​ +
-  * **address** - defines CNC controller hardware the light attached to  +
-      * "​inputs"​ - the light attached to input pin +
-      * "​outputs"​ - the light attached to output pin +
-      * "​number"​ - defines pin number the light attached to. A number can be assigned directly, for example \\ number="​0"​ for pin #0 \\ number="​15"​ for ipn #15 \\ or through pin definition file used in Hardware PLC - "​pins.h"​. In this case sign "#"​ and the pin name defined in "​pins.h"​ should be instead of pin number. For example \\ **number="#​OUTPUT_SPINDLE"​** \\ and "​pins.h should contain this name definition, for example <code C>#​define OUTPUT_SPINDLE 7</​code>​+
  
 +<code c><​gitem where="​oil-change"​ position="​10;​40"​ width="​250"​ displayWidth="​90"​ height="​60"​ labelWidth="​160" ​
 + ​name="​display-cnc-gvariable-6090"​ K="​0.001"​
 + ​bgColor="##​b-display"​ fgColor="##​f-display" ​
 + ​labelFgColor="##​f-label"​ labelFontSize="​14"​ labelFontStyle="​normal" ​
 + ​fontSize="​18"​ fontStyle="​bold"​ format="​%6.3f"​ type="​display"​ >
 +            <​message>​X Trip counter</​message>​
 +<​message_ru>​Счетчик пути по Х</​message_ru>​
 +</​gitem></​code>​
  
-=== GLView === +  * **where** descibes the section into which the Display element will be inserted
-=== NCView === +  * **position** describes the xy position within that tab 
-2D Visualization widget+  ​* **width** and **height** specify the overall dimensions of the Display element, while **displayWidth** and **labelWidth** describe the size of the Display and Label parts (Display being the dynamic changing part and Label being the static text part)
-  * Basic setup. +  * **name** specifies the variable name for the displayed element (global variable #6090 is brought up on the screen in this case) 
-<code XML> +  ​* **bgColor** and **fgColor** specify the background and foreground colours of the Display element (or any other element, depending on where they are specified) respectively. As with a Label, these colours can either be set directly, through an HTML RGB code, or by writing out the colour name from Screen > Colors prefaced by two pound signs (##). If no specified colour with that name is found in that list, then the new name will be added to the list and the user will be able to edit it (changes will take effect on the next program reload). ​  
-<gitem where="​olicut"​ name="​ncview"​ type="​ncview"​ +  ​* Similarly, **labelFGColor** specifies the foreground color of the Label (static text) element (this is set separately from the Display element colour). 
-  ​position="​100;​100" ​width="​880" ​height="​440"​ /> +  ​* **format** specifies how the values are presented. The first number specifies the overall digits that the value will display, while the second number specifies the amount of digits after the dot. F stands for float, while d stands for integer. For example, in this case, %6.3f specifies a float number with six total digits maximum and which allows the number to display up to the third decimal place (degree of accuracy). ​ 
-</​code>​ +  ​* **deviation** can be specified to indicate the minimum absolute value change that would require the program to display a new value. For example, deviation of 0.01 means that the value needs to change by at lease 0.01 (absolute value) for the new numeric value to be displayed. This allows to eliminate visual changes/jumps in numbers due to small changes which can be disregarded. ​
-  ​Advanced setup+
-<code XML> +
-<gitem where="​olicut" ​name="​ncview"​ type="​ncview"​ +
-  position="​100;​100"​ width="​880"​ height="​440"​  +
-  singlepath="​yes"​ +
-  bgColor="#00E0E0"​  +
-  ColorT0="​gray:​1"​  +
-  ColorT1="​#D000D0:​5"​  +
-  ColorT2="#​D05000:​5" ​ +
-  ​ColorT3="​red:​2" ​ +
-  ​ColorT4="​green:​2" ​ +
-  ​ColorT5="#​0000D0:​2" ​/+
-</​code>​+
  
 +=== BDisplay ===
  
-=== Logview === +The BDisplay element allows to display a dynamic value, like a typical Display, which can also be clicked. When clicked, a popup element will be brought up on the screen that will allow the user to enter a new value. For example, the program coordinates displayed on the main screen of the software are BDisplay elements which bring up a popup when clicked, allowing to change their values:
-=== NCList === +
-=== CentringView === +
-=== Rotation2View ===+
  
-==== MyCNC Actions ====+{{:​mycnc:​screen-config-005-bdisplay.png}}
  
-All button-like screen components (button, xbutton, bdisplay, kspinbox2) runs **Handler** procedure when "​Pressed"​ or "​Released"​ avent activated by mouse click or touch screen tap. The Handler defined in "​action"​ attribute ​of xXML configuration item.+An example ​of BDisplay code would be the following:
  
-List of actions is shown below+<code XML> 
 +<gitem where="​x-coordinates"​ position="​74;​10" ​  
 +  width="​150"​ height="​34" ​ displayAlignment="​right;​bottom"​ 
 +  fgColor="##​f-workpos"​ format="​%8.3f"​ fontFamily="​Open Sans" fontSize="​21"​  
 +  type="​bdisplay"​ deviation="​0.0005"​ action="​direct-run:​G90 G92 X %v" 
 +  name="​display-work-pos-axis-0"​ bgColor="##​b-display"​  
 +  displayWidth="​150"​ fontStyle="​bold"></​gitem>​ 
 +</​code>​ 
 +  ​
  
-^ Action Name ^ Description ^ +  * **fgColor** and **bgColor** specify the colours used for the foreground and the background of the BDisplay element respectively. ​ 
-| advanced-config | | +  * **displayAlignment** allows to position the displayed element in the right bottom corner of the specified area 
-| basic-config | | +  * **format** works in the same way as the Display format 
-| toggle-button-coordinates | | +  * **type** is specified to be "​bdisplay"​ 
-| toggle-button-jog-enable | | +  * **deviation** specifies the minimum change in the value to display a new value for the user. This is done in order to prevent excessive value jumping due to small changes. 
-| toggle-button-soft-limits | | +  * **action** allows to perform some sort of action or command after the confirmation checkmark in the popup window is pressed (after the new value is entered). This value is stored as %v and will be used to change the program coordinates to the necessary value in the selected axis. This is extremely useful for changing the values which would require an action to do so (e.g. some kind of machine movement). If no actions are required (i.e., if all that is required is a value/​variable change which does not lead to direct machine actions immediately),​ KDisplay can also be used. 
-| toggle-button-mist | | +  * **name** specifies the global variable or the item that the element will be receiving its value from to display. In this case, it is receiving a value from the work-pos-axis-item. A comprehensive [[mycnc:item_list|Common Item list]] and [[mycnc:​global_variables|Global Variables list]] can be used for reference in choosing a name for a BDisplay element. ​
-| toggle-button-flood | | +
-| toggle-button-spindle | | +
-| toggle-button-ccw-spindle-spindle | | +
-| toggle-item: | | +
-| laser-marker- | |+
  
-=== Player actions ​===+=== RadioDisplay ​===
  
-^ Action Name ^ Description ^ +RadioDisplay allows ​to display some value from a list. For example, the display of the coordinate system in the Diagnostics window of the 1366M4 profile is done by using a RadioDisplay element. This allows the user to select some coordinate system (which is not labeled G54/G55/etc within the software, but rather 1, 2, 3, etc), and then display the selected choice as some sort of a user-facing text string (thus, for example, displaying a software "​2",​ which would not be useful ​to the user without an external reference sheet, as "​G55"​). This is useful to "​translate"​ machine settings or error codes into a text string that the user can easily read:
-| player-play | | +
-| player-play-confirm | | +
-| player-play-edge | | +
-| player-play-edge-confirm | | +
-| player-jump1 | | +
-| player-pause | | +
-| player-stop | | +
-| player-skip-forward | | +
-| player-skip-forward-10 | | +
-| player-skip-backward | | +
-| player-skip-backward-10 | | +
-| player-skip-part-f | | +
-| player-skip-part-b | | +
-| player-nc-reset | | +
-| player-nc-reset-confirm | | +
-| player-back-to-path | | +
-| player-back-to-path-confirm | | +
-| player-play-back | | +
-| player-nc-tie | | +
-| player-play-step | | +
-| player-play-step-backward | | +
-| mdi-play | | +
-| mdi-open | |+
  
 +{{:​mycnc:​screen-config-006-radio-display.png}} ​
  
-=== Jog actions ===+An example of code for such a RadioDisplay element is presented here:
  
-^ Action Name ^ Description ^ +<code c><​gitem fgColor="##​f-display"​ labelFgColor="##​f-label" where="​coord-sys0" ​ 
-| jog-0-plus, jog-1-plus, \\ jog-2-plus, jog-3-plus, \\ jog-4-plus, jog-5-plus, \\ jog-6-plus, jog-7-plus \\ jog-8-plus | Jog Positive direction in Axis X, Y, Z, A, B, C, U, V, W | +labelWidth="​80"​ displayWidth="​160"​ format="​---;​G54;​G55;​G56;​G57;​G58;​G59;​G59.1;G59.2;G59.3" ​ 
-| jog-0-minus, jog-1-minus, \\ jog-2-minus, jog-3-minus, \\ jog-4-minus,​ jog-5-minus,​ \\ jog-6-minus,​ jog-7-minus,​ \\ jog-8-minus ​  | Jog Negative direction in Axis X,​Y,​Z,​A,​B,​C,​U,​V,​W ​ | +height="​40"​ type="​radio-display"​ name="​display-gvariable-5220" ​ 
-| jog-0-plus-1-plus | Simultaneous two-axes Jog X+ Y+ | +bgColor="##​b-display"​ fontStyle="​bold"​ orientation="​horizontal">​
-| jog-0-plus-1-minus | Simultaneous two-axes Jog X+ Y- | +
-| jog-0-minus-1-plus | Simultaneous two-axes Jog X- Y+ | +
-| jog-0-minus-1-minus | Simultaneous two-axes Jog X- Y- | +
-| jog-overspeed-inc \\ jog-overspeed-dec | Increment/​Decrement Jog Overspeed value (%) | +
-| jog-overspeed-set:  | Set given Jog Overspeed value (%) |+
  
 +<​message>​Current Num</​message>​
 +<​message_pl>​Aktualny numer</​message_pl>​
 +<​message_ru>​Номер</​message_ru>​
 +<​message_kr>​Current Num</​message_kr>​
 +<​message_vn>​Số hiện tại</​message_vn>​
 +<​message_es>​Actual</​message_es>​
 +</​gitem></​code>​
  
-=== Motion Settings Actions===+  * **Colours** are selected the same was as described in the Display and Label sections (foreground/​background,​ label colours, etc) 
 +  * **format** lists the list of all possible user-facing text strings. These are numbered 1, 2, 3, etc, separated by a semicolon.  
 +  * **type** is set to "​radio-display"​ 
 +  * **name** is the system variable which will be used to choose the user-facing text string. The system will read, for example, Global Variable #5220, and see what value (for example, 4) is written in it. Then, if 4 is written in 5220, G57 will be displayed to the user.  
 +  * **orientation** can be set to be horizontal or vertical
  
-^ Action Name ^ Description ^ +NOTE: RadioDisplay and Radio2Display allow for some rudimentary actions to be assigned to the action of clicking the RadioDisplay elementThese are limited compared to the Button/XButton/etc elements, however they are still extremely useful:
-| step-float-inc \\ step-float-dec ​ | Increase/​decrease Jog Step Size | +
-| step-size-inc \\ step-size-dec ​ | Increase/​decrease Jog Step Size | +
-| motion-linear-acceleration-inc \\ motion-linear-acceleration-dec ​ | Increase/​decrease Motion Linear Acceleration value | +
-| motion-linear-jog-speed-inc \\ motion-linear-jog-speed-dec \\ motion-linear-jogspeed-inc \\ motion-linear-jogspeed-dec ​ | Increase/​decrease Motion Linear Jog Speed value | +
-| motion-jog-speed-x-inc,​ \\ motion-jog-speed-x-dec,​ \\ motion-jog-speed-y-inc,​ \\ motion-jog-speed-y-dec,​ \\ motion-jog-speed-z-inc,​ \\ motion-jog-speed-z-dec,​ \\ motion-jog-speed-a-inc,​ \\ motion-jog-speed-a-dec,​ \\ motion-jog-speed-b-inc,​ \\ motion-jog-speed-b-dec,​ \\ motion-jog-speed-c-inc,​ \\ motion-jog-speed-c-dec,​ \\ motion-jog-speed-u-inc,​ \\ motion-jog-speed-u-dec,​ \\ motion-jog-speed-v-inc,​ \\ motion-jog-speed-v-dec,​ \\ motion-jog-speed-w-inc,​ \\ motion-jog-speed-w-dec,​ \\ motion-jog-speed-xy-inc,​ \\ motion-jog-speed-xy-dec,​ \\ motion-jog-speed-xyz-inc,​ \\ motion-jog-speed-xyz-dec | Increase/​decrease Motion **Jog** Speed value for given Axis | +
-| motion-rapid-speed-x-inc,​ motion-rapid-speed-x-dec,​ \\ motion-rapid-speed-y-inc,​ motion-rapid-speed-y-dec,​ \\ motion-rapid-speed-z-inc,​ motion-rapid-speed-z-dec,​ \\ motion-rapid-speed-a-inc,​ motion-rapid-speed-a-dec,​ \\ motion-rapid-speed-b-inc,​ motion-rapid-speed-b-dec,​ \\ motion-rapid-speed-c-inc,​ motion-rapid-speed-c-dec,​ \\ motion-rapid-speed-u-inc,​ motion-rapid-speed-u-dec,​ \\ motion-rapid-speed-v-inc,​ motion-rapid-speed-v-dec,​ \\ motion-rapid-speed-w-inc,​ motion-rapid-speed-w-dec,​ \\ motion-rapid-speed-xy-inc,​ motion-rapid-speed-xy-dec,​ \\ motion-rapid-speed-xyz-inc,​ motion-rapid-speed-xyz-dec | Increase/​decrease Motion **Rapid** Speed value for given Axis | +
-| motion-feed-speed-x-inc,​ \\ motion-feed-speed-x-dec \\ motion-feed-speed-y-inc \\ motion-feed-speed-y-dec \\ motion-feed-speed-z-inc \\ motion-feed-speed-z-dec \\ motion-feed-speed-a-inc \\ motion-feed-speed-a-dec \\ motion-feed-speed-b-inc \\ motion-feed-speed-b-dec ​ \\ motion-rapid-speed-c-inc \\ motion-rapid-speed-c-dec \\ motion-rapid-speed-u-inc \\ motion-rapid-speed-u-dec \\ motion-rapid-speed-v-inc \\ motion-rapid-speed-v-dec \\ motion-rapid-speed-w-inc \\ motion-rapid-speed-w-dec \\ motion-rapid-speed-xy-inc \\ motion-rapid-speed-xy-dec \\ motion-rapid-speed-xyz-inc \\ motion-rapid-speed-xyz-dec | Increase/​decrease Motion **Rapid** Speed value for given Axis | +
-| motion-overspeed-inc \\ motion-overspeed-dec \\ motion-overspeed | Increase/​decrease/​set Motion **Overspeed** value (%) |  +
-| spindle-speed-inc \\ spindle-speed-dec \\ spindle-speed | Increase/​decrease/​set Current Spindle Speed (S) for current operationNew "​S"​ value in running g-code will overwrite Current Spindle Speed | +
-| spindle-speed-restore | **Restore Default** Spindle Speed (S) | +
-| spindle-overspeed-inc \\ spindle-overspeed-dec \\ spindle-overspeed | Increase/decrease/set Spindle Speed (S) |+
  
-=== Built-in Editor Actions ===+^ Action ^ Description ^ 
 +| cnc-gvariable-switch | Switches between different values for a global variable (these variables are preassigned and set as a list separated by commas) |  
 +| cnc-gvariable-toggle | Toggles a global variable between 0 and 1 upon RadioDisplay/​Radio2Display clicks | 
 +| item-switch | Switches between preassigned values/​entries for an item | 
 +| toggle-item | Toggles an item from the Item list (toggle writes 0 or 1 to the item depending on the previous item state) |
  
-^ Action Name ^ Description ^ +An example of actions being assigned to the RadioDisplay can be seen in the 1366V profile when creating a per-program z-height map to account for uneven material positioning. The RadioDisplay element switches between "​Area"​ and "​Rectangle"​ depending on the mode chosen to create the probe mesh:
-| editor-arrow-up | | +
-| editor-arrow-down | | +
-| editor-ncline-edit | | +
-| editor-ncline-insert | | +
-| editor-ncline-remove | | +
-| editor-font-inc | | +
-| editor-font-dec | | +
-| editor-numbers-toggle | | +
-| editor-selection-begin | | +
-| editor-selection-end | | +
-| editor-selection-remove | | +
-| editor-selection-insert | | +
-| editor-new | | +
-| editor-save-as | | +
-| editor-save | |+
  
 +{{:​mycnc:​screen-config-27-radiodisplay-actions.png}}
  
-=== File Manipulation Actions ===+If we look at the code, the RadioDisplay element is actually using the cnc-gvariable-toggle to change between the two modes (0 for Rectangle, 1 for Area):
  
-^ Action Name ^ Description ^ +<code XML> 
-| save | | +<gitem where="​map-z-view"​ position="​150;​5"  ​ 
-| open | | + displayWidth="​110"​ width="​110"​ height="​70" ​ displayAlignment="​_center"​ 
-| load-file: | | + fgColor="##​f-display" ​ 
-| load-macro: | | + format="​Rectangle;​Area"​ fontFamily="​Open Sans" fontSize="​20" ​ 
-| file-close | | + type="​radio-display"​ deviation="​0.5" ​ 
-| file-close | | + action="​cnc-gvariable-toggle-8255"​ 
-| dxf-import | | + name="​display-cnc-gvariable-8255" ​ 
-| file-close | | + bgColor="##​b-display"​ fontStyle="​bold">​ 
-| image-import | |+</​gitem>​ 
 +</​code>​
  
 +  * **action** is set to "​cnc-gvariable-toggle-8225"​. Here, when the RadioDisplay element is clicked, the action is triggered and the global variable is toggled between 0 and 1.
 +  * **format** is set to "​Rectangle;​Area"​. This corresponds to the 0/1 toggle for the global variable, when the RadioDisplay is clicked, the visual display element also switches - however, it is important to note that it is the **action** and not the **format** which determines what actually happens to the program when the click occurs.  ​
  
-=== Visualization Actions ​===+=== Radio2Display ​===
  
-^ Action Name ^ Description ^ +Radio2Display allows for a more granular display configuration than the simpler RadioDisplay. Similar ​to RadioDisplay,​ Radio2Display transforms some system values into a user-facing string from a list of options which are specified beforehand. For examplethe step size values ​for the jog buttons on the main screen of the 1366M4 profile use Radio2Display elements:
-| zoom-in | | +
-| zoom-out | | +
-| fit-to-view | | +
-| zoom-in | | +
-| zoom-in | | +
-| 3dview-xy | 3D Visualization:​ show XY view | +
-| 3dview-xz | 3D Visualization:​ show XZ view  | +
-| 3dview-yz | 3D Visualization:​ show YZ view  | +
-| 3dview-iso | 3D Visualization:​ show ISO view  | +
-| 3dview-custom:​ | 3D Visualization:​ show Custom viewdefined by Alfa,​Beta,​Gamma angles ​for rotation matrix ​ |+
  
 +{{:​mycnc:​screen-config-007-radio2display.png}}
  
-=== Widget Manipulations Actions ===+Example code for this screen element: ​
  
-^ Action Name ^ Description ^ +<code c><​gitem where="​x-jog" position="​90;​100"​ width="​80"​ height="​40"​ displayWidth="​80" ​ 
-| show-inputbox | | + fgColor="##​f-display"​ bgColor="​transparent"​ 
-| show-widget-centring | | + alignment="​center"​ fontSize="​14"​ type="​radio2-display" ​ 
-| show-widget-rotation | | + format="​0.001=0.001;​0.01=0.01;​0.1=0.1;​1.0=1.0;​10=10;​∞=88.88=2.3" ​ 
-| show-widget-sawcutting | | + deviation="​0.0005"​ name="​display-gvariable-5522" ​ 
-| show-widget-diagnose | | + fontStyle="​bold"​ orientation="​vertical"​ ></​gitem></​code>​
-| show-widget-config | | +
-| show-widget-edit | | +
-| show-widget-lib | | +
-| show-widget-tools | | +
-| show-widget-lof | | +
-| show-widget-report | | +
-| show-widget-support | | +
-| show-widget-user | | +
-| show-widget-work | | +
-| mywidget-show:​ | | +
-| mywidget-hide:​ | | +
-| mywidget-toggle:​ | | +
-| pendant-widget-open | | +
-| measure-surface | | +
-| toggle-virtual-keyboard | | +
-| mywidget: | |+
  
 +  * **bgColor** (background colour) can be set to be transparent
 +  * **type** is set to be radio2-display
 +  * **format** lists all the available options. For example, when the input is equal to 0.1, the system will display 0.1. And when the input is equal to the jog step of 88.88, the system will recognize this command and set the jog to infinity (infinite step). If another number is added to each component, like in the ∞=88.88=2.3 line, that third number specifies the font size for that particular text element. Here, the infinity sign will be 2.3 times larger than the default of the same font, allowing for the infinity sign to be more clearly visible to the end user. 
 +  * **deviation** specifies the minimum value by which the parameter should change by for the change to be visually represented on the screen
 +  * **name** indicates the global variable that the system is monitoring (global variable #5522 in this case)
  
 +Similar to RadioDisplay,​ Radio2Display allows for a limited number of actions which can be assigned to the action of pressing or clicking the Radio2Display element:
  
-=== Application Actions ===+^ Action ^ Description ^ 
 +| cnc-gvariable-switch | Switches between different values for a global variable (these variables are preassigned and set as a list separated by commas) |  
 +| cnc-gvariable-toggle | Toggles a global variable between 0 and 1 upon RadioDisplay/​Radio2Display clicks | 
 +| item-switch | Switches between preassigned values/​entries for an item | 
 +| toggle-item | Toggles an item from the Item list (toggle writes 0 or 1 to the item depending on the previous item state) |
  
-^ Action Name ^ Description ^ +The example in RadioDisplay code can also be used to assign actions to Radio2Display if type="​radio2-display"​.
-| close-application | Close myCNC Control software | +
-| cnc-config-save | Save myCNC configuration files to disk |+
  
 +=== KDisplay ===
  
-=== Hardware Manipulation ​actions ​===+KDisplay is similar to BDisplay, as it allows to display some dynamic changing variable/​number and to register when it is clicked on the software screen (after which the user can enter a new value). It is different from BDisplay in that it is geared towards keyboard/​mouse combos (rather than touchscreen setups) and does not bring up a full popup screen, and because it does not allow for actions ​to be executed after the new value has been inputted. As such, it is typically used on simple value changes which do not cause direct machine actions immediately after. ​
  
-^ Action Name ^ Description ^ +For example, the gantry alignment correction value can be changed from the Diagnostics window of myCNC software using a KDisplay element: ​
-| servo-pid-on |  | +
-| servo-pid-off |  | +
-| hw-pwm-inc |  | +
-| hw-pwm-dec |  | +
-| hw-dac-inc |  | +
-| hw-dac-dec |  | +
-| hw-direct- | | +
-| thc-arc-voltage-ref-inc | | +
-| thc-arc-voltage-ref-dec | | +
-| thc-jog-speed-dec | | +
-| thc-jog-speed-inc | | +
-| thc-jog-pos | | +
-| thc-jog-neg | | +
-| dev-thc-jog-pos | | +
-| dev-thc-jog-neg | |+
  
-| toggle-widget-centring | | +{{:​mycnc:​screen-config-008-gantry.png}}
-| toggle-widget-rotation | | +
-| toggle-widget-sawcutting | | +
-| toggle-widget-user | |+
  
-| toggle-button-flood | | +<code c> 
-| toggle-button-coolant | | +   <gitem fgColor="##​f-display"​ labelFgColor="##​f-label" where="​gantry-correction"​ labelHeight="​40" ​ 
-| toggle-button-spindle | | +   labelWidth="​200"​ displayWidth="​90"​ format="​%6.3f"​ height="​40"​  
-| toggle-button-ccw-spindle | | +   ​type="​kdisplay"​ name="​display-cnc-gvariable-7525" bgColor="##​b-display" ​ 
-| toggle-button-mist | | +   fontStyle="​bold"​ orientation="​horizontal"​ deviation="​0.001"​ > 
-<del>toggle-button-cv-mode</del| |+   <message>Gantry Alignment Correction (#​7525)</​message>​ 
 +   <​message_ru>​Коррекция для выравнивания портала (#​7525)</​message_ru>​ 
 +   <​message_vn>​cái dá căn chỉnh điều chỉnh(# 7525)</​message_vn>​ 
 +   <​message_es>​Corrección de alineamiento Gantry (#​7525)</​message_es>​\ 
 +   </​gitem>​ 
 +</code>
  
-=== PLC Actions ===+  * **Colours** are set similarly to the other elements (Display, BDisplay, etc), allowing to change the foreground/​background and label colour of the displayed element.  
 +  * **type** is set to "​kdisplay"​ 
 +  * **name** displays the global variable that will be used in this field (in this example, it's global variable #7525 for the gantry alignment procedure) 
 +  * **deviation** specifies the minimum value by which the parameter (global variable used in this case) should change for the change to be visually represented on the screen. This cutoff allows to disregard some small changes. ​
  
 +=== KSpinBox ===
  
-^ Action Name ^ Description ^ +KSpinBox shows a certain value with an arrow on either side, allowing the user to change the value upon pressing (or pressing and holding) the arrow buttons. The PWM outputs section of the Diagnostics window is done using KSpinBoxes:
-| soft-plc-run| | +
-| soft-plc-stop:​ | | +
-| *soft-plc-stop:​ | | +
-| plc-run: | | +
-| direct-plc: | | +
-| multidev-plc-run:​ | | +
-| switch-cnc-gvariable | |+
  
-=== Job Actions ===+{{:​mycnc:​screen-config-010-pwm-kspinbox.png}}
  
-^ Action Name ^ Description ^ +Example of KSpinBox code:
-| direct-run| | +
-| direct-run-confirm:​ | | +
-| radio-confirm | | +
-| mode-cutting-ignore | | +
-| mode-cutting-accept | |+
  
-| mdi-save-list | |+<code c> <gitem fgColor="##​f-display"​ labelFgColor="##​f-label"  
 +  where="​pwms"​ format="​%d"​ labelWidth="​80"​ displayWidth="​80"​ alignment="​left"​  
 +  action="​hw-pwm-dec;​hw-pwm-inc"​ height="​40"​ address="​pwm-outputs"​ number="​0"​  
 +  type="​kspinbox"​ bgColor="##​b-display"​ fontStyle="​bold">​ 
 +  <​message>​PWM 1</​message>​ 
 +  <​message_pl>​PWM 1</​message_pl>​ 
 +  <​message_cn>​PWM的1</​message_cn>​ 
 +  <​message_ru>​ШИМ1</​message_ru>​ 
 +  <​message_kr>​PWM 1</​message_kr>​ 
 +  <​message_es>​PWM 1</​message_es>​ 
 +  </​gitem>​ 
 +</​code>​
  
-| mode-show-ruler | |+  * **colours** are done in a similar manner to Labels, Display, BDisplay elements and others (foreground/​background colours, label colours, etc).  
 +  * **where** specifies the location of the displayed element (the PWM section of the screen) 
 +  * **alignment** specifies the positioning of the displayed element 
 +  * **action** specifies the two action that are taken when the user presses on the left and on the right arrow respectively. Here, "hw-pwm-dec" and "​hw-pwm-inc"​ are used to increase and decrease PWM outputs values. The full list of available actions is available on the page below, in the **Actions** section.  
 +  * **address** specifies the address of the value/item the user is changing (pwm-outputs in this case) 
 +  * **number** specifies the particular hardware port that the on-screen element will be monitoring. Here, it is the number of the PWM output, as specified in the address. It is counted from 0, not from 1, so PWM output 1's number is 0, PWM Output 2 is number 1, etc. 
 +  * **type** is set to "​kspinbox"​
  
-| mode-show-dimension | |+=== KSpinBox2 ===
  
-| mode-show-workarea | |+KSpinBox2 allows the user to add an element similar to a regular KSpinBox, displaying a value between two arrows, which also allows the user to click on the current value and change it using a popup screen in addition to changing the value by pressing the respective arrows. This element is used, for example, on the main screen of myCNC software'​s 1366M4 profile to change overspeed, jog overspeed, and spindle speed. Below is an example of such a screen element when the value in the jog overspeed box has been clicked, bringing up a popup screen:
  
 +{{:​mycnc:​screen-config-011-kspinbox2-jog-overspeed.png}}
  
-=== OS/System Actions ===+Example KSpinBox2 code:
  
-^ Action Name ^ Description ^ +<code c> 
-| system-cmd | Run system command | +  <​gitem fgColor="##​f-display"​ position="​880;​560"​ height="​60"​ width="​320" ​ 
-| application-close | Close MyCNC application | +  ​where="​main"​ suffix="​%"​ format="​%d"​ K="​1." ​ 
-| application-close-confirm | Run confirmation dialog to Close MyCNC application | +  ​action="​jog-overspeed-dec;​jog-overspeed-inc"​ type="​kspinbox2" ​ 
-| application-minimize | Minimize MyCNC Application |+  ​name="​display-jog-overspeed"​ bgColor="​black"​ fontStyle="​bold"​  
 +  labelFontSize="​14"​ displayWidth="​100"​ labelWidth="​100"​ orientation="​horizontal">​ 
 +     <​message>​Jog over speed</​message>​ 
 +     <​message_pl>​Przekroczenie prędkości przesuwu</​message_pl>​ 
 +     <​message_ru>​Ручное/​Скорость</​message_ru>​ 
 +     <​message_vn>​Chạy bộ trên tốc độ</​message_vn>​ 
 +     <​message_es>​Jog over speed</​message_es>​ 
 +  </​gitem>​ 
 +</​code>​
  
 +  * **fgColor** specifies the foreground colour, **bgColor** specifies the background colour of the on-screen element
 +  * **position** specifies where in the window the element will be inserted, **height** and **width** specify the size of the element
 +  * **where** designates the window tab into which the element is inserted (in this case, main). The position which was previously specified is noted in relation to this window tab, not the entire myCNC window.
 +  * **format** describes how the value will be presented to the user. %d stands for integer while %f stands for float. **K** specifies the coefficient by which the value will be multiplied by before displaying it to the user. Here, the coefficient is set to 1 to display the actual value. ​
 +  * **action** lists the two actions which take place when the left arrow and the right arrow buttons are pressed respectively. Here, jog-overspeed-dec is assigned to the left arrow button, and jog-overspeed-inc is assigned to the right button. ​
 +  * **type** is set to kspinbox2
 +  * **name** points to the value that will be displayed. This can be a global variable, as seen in the KDisplay and Radio2Display examples above, or it can be an item, as described in the [[mycnc:​item_list|Common Item List]]. In this example, the value displayed will be the jog-overspeed item.
 +  * **fontStyle** is set to bold, **labelFontSize** is set separately, as is **displayWidth** and **labelWidth**
 +  * **orientation** can be set to be horizontal or vertical
 +  * the message can be listed in different languages, the system will automatically display the correct message depending on the user language settings for myCNC
  
-=== CNC Variables manupulation Actions ​===+=== LED Display ​===
  
-^ Action Name ^ Description ^ +LED Display allows the user to display an LED element on the screen. This light can be on or offand each LED element can have a different colour ​set for its ON configuration. This is useful to show the state of system items which have a binary state (on or off)such as input ports which can be viewed from the Diagnostics page:
-| direct-set-cnc-var | | +
-| cnc-variable:​ | | +
-| cnc-gvariable-deccnc-gvariable-inc ​ | | +
-| cnc-variable-dec,​ cnc-variable-inc,​ \\ cnc-variable-change,​ cnc-variable-toggle,​ cnc-variable-set, cnc-variable-clear,​ \\ cnc-variable-vset,​ cnc-variable-switch ​ | | +
-| cnc-vm-variable-dec,​ cnc-vm-variable-inc | | +
-| device-variable-dec,​ device-variable-inc | |+
  
-| item-switch| | +{{:mycnc:screen-config-012-led.png}}
-| run-numpad| | +
-| item: | | +
-| load-item: | | +
-| cnc-nvariable| | +
-| cnc-nvariable:​ | |+
  
-| fake | Empty Handler Action. Nothing happpens if run this action |+Below is an example of LED display code for an LED element which will display the state of Input #0 (on or off):
  
-| myitem-value-inc, myitem-value-dec | Increement/Decrement XML Item value by name |+<code c><​gitem inversion="​no"​  
 +  labelFgColor="##​f-label" labelAlignment="​right;​vcenter"​  
 +  where="​inputs-0" height="​20"​ address="​inputs"​  
 +  shape="​round"​ number="​0"​ type="​led">​ 
 +    <​message>​IN00</​message>​ 
 +    <​message_es>​IN00</​message_es>​ 
 +</​gitem><​/code>
  
-=== HMI  Actions ===+  * **inversion** indicates whether the LED behaviour will be "​inverted"​ - if ON is set to be registered as OFF for visual purposes, and vice versa.  
 +  * **where** specifies the section of the window where the LED element will be located (inputs-0 in this case) 
 +  * **address** specifies the physical controller hardware that the element will receive its information from ("​inputs"​ in this example) 
 +  * **shape** can be set to be round, or left at square by default (if no shape has been specified). An example of a square LED can be seen at the bottom right of the Diagnostics page, to display whether recent changes have been saved to flash memory: 
 +{{:​mycnc:​screen-config-013-square-led.png}} 
 +  * **number** specifies the particular hardware port in the specified hardware section (inputs in this example) that will be monitored. Here, the state of port 0 will be monitored.  
 +  * **type** is set to "​led"​
  
 +=== SVG Display ===
  
-^ Action Name ^ Description ^ +SVG Display allows ​to display a set of images that will be changing depending on the user input (cycling through the available images). This allows for more granular control than an LED Display element which can only show two states of a system.
-| search-nc-position | Open dialog ​to define line number for **Run From Here** command | +
-| file-refresh | | +
-| row-n-column | Open **Row And Column Multiplication/​Nesting** Dialog | +
-| dialog-rotate | Open Dialog for NC-program rotation | +
-| mypopup-show:​ | Show custom defined Popup widget | +
-| mypopup-toggle:​ | Toggle custom defined Popup widget | +
-| mode-jog-unlimited | Switch to Unlimited Jog Mode | +
-| show-simple-edit | Show simple text editor window  ​(Ver #1+
-show-simple2-edit | Show simple text editor window ​ (Ver #2) | +
-| rotate-nc-last | Rotage NC program to previously defined angle | +
-| cnc-cutchart-save | Save current cutting data to Cutchart | +
-| cnc-cutchart-load | Load cutting data for selected Cutting Mode | +
-| run-from-here | **Run From Here** command - start job file from selected line |+
  
 +Example code:
  
 +<code c><​gitem where="​adc"​ format="​%d"​ displayWidth="​200"​
 + ​displayHeight="​30"​
 + ​name="​display-cnc-gvariable-7199"​
 + ​imagesfolder="​progress/"​ loop="​no"​ images="​vprogress*"​
 + ​type="​svgdisplay" ​ min="​0"​ max="​4096"​ K="​1"​ />
 +</​code>​
  
 +  * **where** describes the section in which the element will be inserted
 +  * **position** describes the location of the element within that section
 +  * **imagesfolder** specifies the folder from which the displayed images will be taken
 +  * **loop** allows to loop the value count. For example, if the range is specified from 0 to 100, and the loop is set to ="​yes",​ then the 101 value will cause the loop to cycle through again, and the system will display it at its lowest point (looping every 100 units). ​
 +  * **images** specifies the particular images which will be retrieved from the folder. In this case, any images that start with "​volume"​ are used and are cycled in order. ​
 +  * **type** is set to "​svgdisplay"​
 +  * **K** is the coefficient by which the value will be multiplied by before it is used by the element
 +  * **min** and **max** values specify the bounds for the values which are used. Anything lower than the min value is assumed to be equal to min (displays the first image on the list), everything higher than the max value is assumed to be equal to max (displays the last image on the list). ​
  
-==== MyCNC screen configuration examples ====+=== Myitems Widget ​===
  
-[[mycnc-screen:add rotation dialog|Add Rotation Dialog ​on Main Screen]]+The Myitems widget allows the user to create a section or a window within the main myCNC screen ​which can later be filled with buttons/​display elements/​etc. The Myitems widget will serve as a container which can easily be moved on the screen, opened and closed without having to write additional code for the buttons which are inside the widget if simple changes to the widget size/​location are required. Most window elements are done using a myitems widget, for example, the oil change section of the window in the User Settings: ​
  
 +{{:​mycnc:​screen-config-014-myitems-oil.png}}
  
-=== Add "Servo On" - "Servo Off" buttons ===+Example code:
  
-We need to add buttons for Servo On/Servo Off to **1280M5** profile+<code c><​gitem ​ where="​oil-change-frame"​ name="​oil-change"​ bgColor="##​b-widget" ​ type="​myitems"​ 
 + ​position="​10;​10"​ width="​490"​ height="​230" ​/>
  
-Original screen is shown below-+<​include>​oil-change.xml</​include></​code>​
  
-{{ mycnc-1280m5-001.png?500 }}+  * note that the window (oil-change) is itself inside another widget (oil-change-frame),​ specified in the **where** line. Myitem widgets can be inserted into other Myitem widgets, allowing the user to create windows within windows. 
 +  * **name** will specify the name of the myitems widget which can later be used to insert buttons and other display elements into it through the **where** line for each of these particular elements (therefore things like KDisplay, BDisplay, etc can be inserted into this new window). 
 +  * **type** is set as "​myitems"​ 
 +  * **position** is set in pixels within the window/​widget that this new myitems element will be. In this case, it will be 10 pixels lower and 10 pixels to the right from the frame (which is its own separate element in this case). This allows for easy alignment.  
 +  * it is necessary to **include** the actual code for the widget that will be inserted (oil-change.xml). That file contains all the necessary information about what's inside the widget, however it is not necessary to edit it if the entire widget needs to be moved or removed from the screen.
  
-Put our new buttons instead ​of **CV** button+Note that the widget within which the oil-change myitems window is embedded is its own separate widget (consisting ​of a frame with rounded borders). The example code for that will be as follows:
  
-1. Find **cnc-screen.xml** configuration file in **1280M5** profile folder+<code c>  <​gitem ​ where="​user-widget"​ name="​oil-change-frame"​ 
 +  bgColor="##​b-main"​ type="​frame"​ border-color="##​b-border"​  
 +  border-width="​2"​ border-radius="​10"​ 
 +  position="​450;​420"​ width="​510"​ height="​250"​ 
 +  basewidth="​510"​ baseheight="​250"/></​code>​
  
-2. Edit the file (in Midnight commander press F4 on the **cnc-screen.xml** file)+  * **where** specifies that the frame will be inserted into the user-widget ​(the User Settings window is itself a widget ​on the main screen).  
 +  ​* **bgColor** and **border-color** specify the background and border colours respectively 
 +  * ** border-width** and **border-radius** specify the border measurements  
 +  * **basewidth** and **baseheight** are specified to serve as reference width and height during the window resizing process. The system will look at the basewidth/​baseheight,​ and compare that with the actual current width and height of the on-screen widget element. This will allow to position other elements (which are inside the widgetcorrectly, according to the difference between the default (base) and the actual width and height of the program window. ​
  
-3. Find in the file section with **CV** button definition (F7, search "​CV"​)+=== Button ===
  
-Here it is- +A PushButton screen item can be used on myCNC screen to serve as as a button which will trigger some command when pressed. For example, the refresh button can be seen on the main screen of the myCNC software:
-<code xml> +
-<gitem where="​magic"​ position="​960;​0"​ width="​80"​ height="​80" ​  +
-image="​CV/​CV"​ action="​cnc-gvariable-toggle-5710"​  +
-xattr="​60;​4;​16;​16;​led;​red;​round"​ name="​display-gvariable-5710"​  +
-type="​xbutton"​ /> +
-</​code>​+
  
-4. Put under this button small popup window which will be a container for two buttons ​**Servo ON** & **Servo Off**. +{{:​mycnc:​screen-config-016-refresh.png}}
-Add **quick-popup-layout** section with popup window definition -  +
-<code xml> +
-<​quick-popup-layout>​ +
-  <​current>​popup-servo</​current>​ +
-  <layout stretch="​0"​ name="​popup-servo"​ wa="​80;​160;​right"​ orientation="​vertical"​ skin="​skin/​metal-01">​ +
-    <widget stretch="​1"​ spacing="​0"​ name="​toolbar-servo"​ orientation="​vertical">​myitems</​widget>​ +
-  </​layout>​ +
-</​quick-popup-layout> ​        +
-</​code>​ +
-  *  Layout for Servo buttons named "​popup-servo",​ size of layout is **80x160**, layout placed to the right side of the button that activates the popup (**wa** means "​Window Attributes"​). +
-  *  Layout contains a Window named "​toolbar-servo".+
  
-5. Fix **CV** ​button ​to show/hide **popup-servo** - +The code for such a button ​will look as follows:
  
-<​del>​image="​CV/​CV"​ action="​cnc-gvariable-toggle-5710"</​del>​  +<​code ​XML 
-image="​motor/​servo-driver-wide"​ action="​mypopup-toggle:​popup-servo"​ + <​gitem where="​main" ​ 
- + position="​160;0" width="​80"​ height="​80"​  
-<​code ​xml+ ​image="​button-refresh" action="​file-refresh" type="button" />
-<gitem where="​magic" position="​960;0" width="​80"​ height="​80" ​  +
-image="​motor/servo-driver-wide" action="​mypopup-toggle:​popup-servo" +
-xattr="​60;​4;​16;​16;​led;​red;​round"​ name="​display-gvariable-5710"​  +
-type="xbutton" />+
 </​code>​ </​code>​
  
-6. Save **cnc-screen.xml**,​ restart the software and press new button wit **Servo driver**. Small popup grey colour window will be shown on the right side of the button. 
  
-{{ mycnc-1280m5-002.png?700 }}+Attributes description  
 +  * **where** ​parent widget name that the button is placed into (in this example, it is placed in the main window) 
 +  * **position** ​X and Y position of the button inside a parent widget (inside "​main"​ in this case) 
 +  * **width** - button width in pixels 
 +  * **height** - button height in pixels 
 +  * **type** - type definition of the item (should be type="​button"​) 
 +  * **image** - a image (icon) file for the button in the SVG format  
 +  * **action** - action for the button (which procedure will be executed if the button is pressed) 
 +  * **event** - event type the button is sensitive to. Event can be: 
 +    * **pressed** - action is executed if the button is pressed 
 +    * **released** - action is executed if the button is released  
 +    * **both** - there are separate actions (";"​ semicolon separated) for **pressed** and **released** events 
 +  * **skinbase** - besides the Image file for each button there is a common **skin** SVG file for all the buttons. For selected buttons skin file can be redefined with **skinbase** attribute which specifies the border/mask which the button will be used with. This SVG file will be used as a bottom layer for the button image.
  
-7. Add two buttons definition in the popup window +=== XButton ​===
-<code xml> +
-<gitem where="​toolbar-servo"​ image="​motor/​motor-start"​ action="​plc-run:​M62/​3"​  +
-height="​80"​ event="​pressed-delay-1000"​ type="​button"/>​ +
-<gitem where="​toolbar-servo"​ image="​motor/​motor-stop"​ action="​plc-run:​M63/​3"​  +
-height="​80"​ type="​button"/>​ +
-</​code>​+
  
-to prevent accidental servo driver activation add 1 sec delay for start button -  +XButton is a Push button (similar ​to a typical ​button ​described above) with a built-in light indicator. The light is typically used to show the current state of some CNC controller input, output pin, or CNC global variable register value. Effectively,​ this combines the Button ​and LED Display elements, ​for example, in the M03 button ​in the 1366M4 profile.
-<​code>​event="​pressed-delay-1000"</​code>​ +
-action function will be started only if the button press and hold for 1 sec (1000 msec). +
-On button ​will ON relay #3 (M62.plc procedure) +
-Off button will Off relay #3 (M63.plc procedure)+
  
-For more complicated configurations special PLC procedure can be written to handle Servo ON/OFF (for example turn On servo power, wait some time and then check servo Fault/Alarm inputs before turn On **Servo On**)+{{:​mycnc:​screen-config-015-xbutton-m03.png}}
  
-Result should be like this -  +An XButton XML sample code is shown below:
-  +
-{{ mycnc-1280m5-003.png?​700 }}+
  
-== button & xbutton types == +<code XML> 
- +<gitem where="x-mill"  
-Difference between **button** and **xbutton** push-button types easy to see if compare ​"Servo" button that shows/hide popup window and "Servo-On"/"​Servo-Off"​ buttons. Main "​Servo"​ button contains **LED** display. + ​xattr="​3;3;​16;​16;​led;​red;​round" ​ 
-XButton is simple Push button with added LED display on the top. Led parameters are given in attribute **xattr**.  + ​address="outputs"​ number="#​OUTPUT_SPINDLE"​. 
- + ​position="​720;​10"​ width="​70"​ height="​70"​  
-<​code>​ + ​image="​M/​button-m03" action="​plc-run:​M03/#​5524"  
-xattr="​60;4;​16;​16;​led;​red;​round" ​name="display-gvariable-5710"  + ​type="​xbutton"​ />
-type="​xbutton"​ />+
 </​code>​ </​code>​
  
-In xattr programmed start x, y positions of Led inside the button, width and height of Led, defines **led** type, led colour (red, green, blue, yellow) and led shape (round, square). 
  
-Custome defines ​skin from SVG file is possible too and will be described ​in other examples.+Attributes description  
 +  * **where** - parent widget name the button placed to (in this case, the x-mill widget) 
 +  * **position** - X and Y position of the button inside a parent widget 
 +  * **width** - button width in pixels 
 +  * **height** - button height in pixels 
 +  * **type** - type definition of the item (should be type="​xbutton"​) 
 +  * **image** - a image (icon) file in SVG format for the button 
 +  * **action** - action for the button (which procedure will be executed if event triggered) 
 +  * **event** - event type the button is sensitive to. Event can be  
 +    * **pressed** - action is executed if the button has been pressed 
 +    * **released** - action is executed if the button released  
 +    * **both** - there are separate actions (";"​ semicolon separated) for **pressed** and **released** events 
 +  * **skinbase** - besides the Image file for each button there is a common **skin** SVG file for all the buttons. For selected buttons skin file can be redefined with **skinbase** attribute. This SVG file will be used as a bottom layer for the button image. 
 +  * **xattr** - defines light position size and attributes - semicolon separated 
 +      * X,Y position of the led/light inside the button 
 +      * width and height of the led 
 +      * type of light (actually this field is always "​led",​ reserved for future options) 
 +      * shape of the standard LED light. A standard shape can be "​round" ​and "​rect"​ 
 +  * **address** - defines CNC controller hardware the light attached to  
 +      * "​inputs"​ - the light is "​attached"​ to an input pin 
 +      * "​outputs"​ - the light is "​attached"​ to an output pin 
 +      * "​number"​ - defines the pin number than the light is attached to. A number can be assigned directly, for example \\ number="​0"​ for pin #0 \\ number="​15"​ for ipn #15 \\ or through pin definition file used in Hardware PLC - "​pins.h"​. In this case sign "#"​ and the pin name defined in "​pins.h"​ should be instead of pin number. For example \\ **number="#​OUTPUT_SPINDLE"​** \\ and "pins.h should contain this name definition, for example <code C>#​define OUTPUT_SPINDLE 7</​code>​
  
-Attribute **name="​display-gvariable-5710"​** setup LED display to show current state of CNC Global variable #5710 (0 - Led is OFF, 1 or more - LED is ON)+=== GLView ===
  
-Attributes **address="​outputs"​ number="​3"​** setup LED display ​to show current state of output pin #3+GLView allows ​to display a 3D visualization window which will show a visualization of the imported program (such as the window on the main screen ​of myCNC software'​s 1366M4 profile). ​
  
 +{{:​mycnc:​screen-config-017-3d.png}}
  
-To complete this example change led to show output pin #3 to show current servo state and resize the led - +Sample GLView code is shown below:
  
-<​code ​xml+<​code ​c
-<gitem where="​magic" position="​960;0" width="​80" height="​80" ​  + <​gitem where="​xp" name="​glview"​ type="​glview" position="​80;80" width="​910" height="​395"  
-image="motor/​servo-driver-wide" ​action="mypopup-toggle:popup-servo+ singlepath="no" ​bgColor="##b-ncview"​ 
-xattr="56;​4;​20;​20;​led;​green;​round" ​address="outputs" ​number="​3" ​type="xbutton" />+ ​ColorT0="​white:1" ColorT1="#​00DD00:​1"​ ColorT2="#​0000DD:​1"​ ColorT3="#​DDDD00:​1"  
 + ColorT4="#00DDDD:1" ​ColorT5="#00DD00:1" ​ColorT6="#​DD5500:​1"​ 
 + ​HColorT0="​transparent:​0"​ HColorT1="#​DD0000:​3" ​HColorT2="#0000DD:3" ​HColorT3="#​DDDD00:​3"​  
 + ​HColorT4="#​DD00DD:​3"​ HColorT5="#​00DD00:​3"​ HColorT6="#​DD5500:​3" ​ ></gitem>
 </​code>​ </​code>​
  
-{{ mycnc-1280m5-004.png?​700 }}+  * **type** is set to glview 
 +  * **name** is also set to glview in order to allow other widgets to reference this window 
 +  * **position**,​ **width** and **height** specify the location and dimensions of the visualization window (in pixels) 
 +  * **singlepath** can be set to //yes// or //no//. This is only useful on the NCView window (2D visualization program described below) 
 +  * **ColorT0, T1, etc** describe the visualization colours for different tools in the G-code 
 +  * **HColorT0, T1, etc** describes the highlight colour for the selected tool
  
 +=== NCView ===
  
-== Add "Servo On" ​"Servo Off" buttons ​(Version 2==+{{:​mycnc:​screen-config-018-2d.png}} 
 +NCView is the 2D visualization widget to display an image of the imported G-code file such as the main visualization window in the 1366P profile ​(as a 3D visualization is unnecessary for a plasma/gas profile which will be doing all the cutting in the XY plane only).
  
-Just another way to add 2 buttons widget containers with 2 buttons. +Below is the code used to display an NCView window in the 1366P plasma ​profile
-The same **1280M5** ​profile+
  
-Original screen is shown below-+<code XML> 
 +<gitem where="​xp"​ name="​ncview"​ type="​ncview"​ position="​5;​85"​ width="​1010"​ height="​390"​  
 + ​singlepath="​no"​ bgColor="##​b-ncview"​ 
 + ​ColorT0="​white:​1"​ ColorT1="#​00DD00:​1"​ ColorT2="#​0000DD:​1"​ ColorT3="#​DDDD00:​1"​  
 + ​ColorT4="#​00DDDD:​1"​ ColorT5="#​00DD00:​1"​ ColorT6="#​DD5500:​1"​ 
 + ​HColorT0="​transparent:​0"​ HColorT1="#​DD0000:​3"​ HColorT2="#​0000DD:​3"​ HColorT3="#​DDDD00:​3"​  
 + ​HColorT4="#​DD00DD:​3"​ HColorT5="#​00DD00:​3"​ HColorT6="#​DD5500:​3" ​ ></​gitem>​ 
 +</​code>​
  
-{{ mycnc-1280m5-001.png?700 }}+  * **type** is set to "​ncview"​  
 +  * **position**,​ **width** and **height** specify the location and dimensions of the visualization window (in pixels) 
 +  * **singlepath** can be set to //yes// or //no//. Typically, it is set to be off, so as to display kerf compensation (if there is any kerf compensation present). If set to on, kerf compensation will not be visible (similar to the window shown during file import when a 2D G-code file is being imported into myCNC). 
 +{{:mycnc:screen-config-019-kerf-compensation.png}} 
 +  * **ColorT0, T1, etc** signify the tool colours in the visualization (light blue in this case) 
 +  * **HColor** signifies the highlight colour for each tool (colour of the tool visualization when selected - yellow in this case)
  
-Put our new buttons instead of **CV** button+=== X-log and Logview ===
  
-1. Find **cnc-screen.xml** configuration file in **1280M5** profile folder+Logview is the log window tab at the bottom of the main screen ​of myCNC software (within the x-log widget). It contains information on program start and end times, error messages, etc
  
-2. Edit the file (in Midnight commander press F4 on the **cnc-screen.xml** file)+{{:mycnc:screen-config-020-logview.png}}
  
-3. Find in the file section with **CV** button definition (F7, search "​CV"​)+Example code code to insert the log window as it is displayed ​in the 1366M4 profile is the following:
  
-Here it is- +<​code ​XML
-<​code ​xml+<gitem where="​x-log" position="​10;10" ​ 
-<gitem where="​magic" position="​960;0" width="​80" height="​80"  ​ + width="​930" height="​160" ​ name="logview" type="logview"></gitem>
-image="​CV/​CV"​ action="​cnc-gvariable-toggle-5710"​  +
-xattr="​60;​4;​16;​16;​led;​red;​round" ​name="display-gvariable-5710" ​ +
-type="xbutton" />+
 </​code>​ </​code>​
  
-4. Put under this button small popup window which will be a container for two buttons ​- **Servo ON** **Servo Off**+  * **position** describes the location of the logview element withing the x-log widget 
-Add **mywidget** item custom small widget ​with given attributes -  +  ​* **position****width** and **height** specify the parameters of the window within the x-log widget. 
-<code xml> +  * **name** ​and **type** are set to "​logview"​
-<gitem where="​magic"​ position="​1120;​80"​ height="​160"​ width="​80"​  +
-type="​myitems" ​name="​toolbar-servo"​  +
-bgColor="#​d0d0d0"​ hidden="​1"​ /> +
-</​code>​ +
-widget name: **toolbar-servo**+
  
-widget ​size: 80x160 exactly to fit 2 80x80 buttons in+This will insert the Logview element into the x-log MyItems ​widget
  
-built-in led to show **output#​0** state+Below the logview window, a status bar can be seen:
  
-5. Fix **CV** button to show/hide **popup-servo** ​+{{:​mycnc:​screen-config-021-statusbar.png}}
  
-<​del>​image="​CV/​CV"​ action="​cnc-gvariable-toggle-5710"</​del>​  +This is inserted into the x-log widget separately from logview, through the following code
-image="​motor/​servo-driver"​ action="​mywidget-toggle:toolbar-servo"​+
  
-<​code ​xml+<​code ​XML
-<gitem where="​magic" width="​80"​ height="​80" position="​1120;0" ​ +<gitem where="​x-log" position="​10;140" ​width="930" ​height="30" ​fontSize="16" 
-image="motor/​servo-driver" ​action="mywidget-toggle:​toolbar-servo" + ​fontStyle="normal" ​name="statusbar" type="statusbar" />
-xattr="56;​4;​20;​20;​led;​green;​round" ​address="outputs" ​number="0" ​ +
-type="xbutton" ​></gitem>+
 </​code>​ </​code>​
  
-6. Save **cnc-screen.xml**, restart ​the software ​and press the new button with **Servo driver**. Small popup grey colour window will be shown on the right side of the button.+  ​* **where** points out that the status bar is inserted into the x-log widgetsame as the Logview element. 
 +  * **name** ​and **type** are set to "​statusbar"​
  
-{{ mycnc-1280m5-002.png?​700 }}+=== NCList ===
  
-7. Add two buttons definition in the popup window. Definition ​is very similar ​to previous example but need to add button position attribute inside widget and button width/​height attributes. +The NCList widget ​is used to display the G-code commands window ​to the user, as can be seen in the G-code tab on the main screen ​of the 1366M4 ​profile, as well as the nesting, rotation and Run From Here buttons: ​
-<code xml> +
-<gitem where="​toolbar-servo"​ position="​0;​0" ​ width="​80"​ height="​80"​  +
-image="​motor/​motor-start"​ action="​servo-pid-on" ​ event="​pressed-delay-1000"​ type="​button"​ /> +
-<gitem where="​toolbar-servo"​ position="​0;​80"​ width="​80"​ height="​80"​  +
-image="​motor/​motor-stop" ​ action="​servo-pid-off" type="​button"​ /> +
-</code+
- +
-to prevent accidental servo driver activation add 1 sec delay for start button -  +
-<​code>​event="​pressed-delay-1000"</​code>​ +
-action function will be started only if the button press and hold for 1 sec (1000 msec). +
-On button will run Servo-Pid-ON procedure +
-Off button will run Servo-Pid-Off procedure +
- +
-Result should be like this -  +
-  +
-{{ mycnc-1280m5-003.png?​700 }} +
- +
- +
- +
- +
-== Add Window with some LEDs display == +
- +
-We need to add to the main screen ​a window with 8 led displays and some text labels to show the current state of inputs & outputs. +
-We take **1280M5** ​profile as a base +
- +
-Original screen is -+
  
-{{ mycnc-1280m5-002-1.png?700 }}+{{:mycnc:screen-config-023-nclist-full.png}}
  
-Make the visualisation widget a little narrow and put the new window ​to the left side from visualization. +Example code to insert ​the NCList ​window:
-Find "​glview"​ section in cnc-screen.xml and fix from:+
  
-<​code ​xml+<​code ​XML>  
-<gitem where="​magic" position="​0;80" width="​880" height="​340"  +<gitem where="​xp" name="​x-nclist" position="​330;581" ​ 
-bgColor="​0xff353535" ​name="glview" ​type="glview" />+ width="​950" height="​180" basewidth="​950"​ baseheight="​180"​  
 + ​type="​frame"​ border-color="##​b-border"​ border-width="​2"​ border-radius="​10"  
 + ​bgColor="​##b-main" ​hide-list="x-log;​x-mill" ​exclusive="yes" />
 </​code>​ </​code>​
  
-to: +  * **type="frame"** allows to draw a frame border around the NCList window. ​ 
-<code xml> +  * **hide-list** serves as an option to hide the x-log and x-mill windows when the NCList window is active (as they are all situated in the same area). The **exclusive** flag signifies that only the NCList widget will be up on the screen if it is selected, thus allowing to not interfere with x-log and x-mill windows (the same setting is present in both other respective windows).
-<gitem where="​magic"​ position="​160;​80"​ width="​820"​ height="​340"​  +
-bgColor="#​ff353535"​ name="​glview" ​type="glview" ​/> +
-<gitem where="​magic"​ position="​0;​80"​ width="​160"​ height="​340"​  +
-bgColor="#​ffbbbbbb"​ name="​led-panel" type="​myitems"​ /> +
-</​code>​+
  
-Result is -+=== CentringView ===
  
-{{ mycnc-1280m5-002-2.png?700 }}+CentringView consists of the probe tools which allow to center the machine tool with regards to some obstaclesThe window is brought up by clicking the Probe Sensor Window button:
  
-Add 1st line label and leds from laft and right sides:+{{:mycnc:​screen-config-024-centring.png}}
  
-<code xml> +The code to insert such a window into the 1366M4 profile, the following ​code is used:
-<gitem inversion="​no"​ where="​led-panel"​ position="​5;​5"​ width="​20"​ displayWidth="​20"​ height="​20"​  +
-address="​outputs"​ number="​11"​ shape="​round"​ color="​green"​ type="​led"​ /> +
-<gitem inversion="​no"​ where="​led-panel"​ position="​25;​5"​ width="​130"​ labelWidth="​110"​  +
-displayWidth="​20"​ height="​20"​ labelAlignment="​hcenter"​ labelFontSize="​14"​  +
-address="​outputs"​ number="​14"​ shape="​round"​ color="​green"​ type="​led">​ +
-  <​message>​Side pillar</​message>​ +
-  <​message_ru>​Боковой упор</​message_ru>​ +
-</​gitem>​ +
-</code>+
  
-**where="​led-panel"​** - LEDs will be added to window named "​led-panel"​ which was added before +<​code ​XML
- +  <gitem where="​x-reserv"  
-**address="​outputs"​** - Leds will show state of **Outputs** +  position="​8;5" width="​80" height="​80" ​image="probing/centring-unit"  
- +  ​action="mywidget-toggle:x-centring" type="button"/>
-**<gitem inversion="​no"​ where="​led-panel"​ position="​5;​5"​ width="​20"​ displayWidth="​20"​ height="​20"​  +
-address="​outputs"​ number="​11"​ shape="​round"​ color="​green"​ type="​led"​ />** +
- - fisrt (left) led is single, no text label assigned +
-   +
-**<​message_ru>​Боковой упор</​message_ru>​** - second (right) led assosiated with text label +
- +
-**position="​5;​5"​** - led is placed to position inside parent widget +
-   +
-Result is - +
-{{ mycnc-1280m5-002-3.png?​700 }} +
- +
-Add some more LEDs to the widget. Complete code for the widget is  -  +
- +
-<​code ​xml+
-  <gitem where="​magic" position="​0;​80"​ width="​160"​ height="​340"​ bgColor="#​ffbbbbbb"​  +
-  name="​led-panel" type="​myitems"​ /> +
- +
-<gitem inversion="​no"​ where="​led-panel"​ position="​5;​5"​ width="​20"​ displayWidth="​20"  +
-  ​height="​20"​ address="​outputs"​ number="​11"​ shape="​round"​ color="​green"​ type="​led"​ /> +
- +
-<gitem inversion="​no"​ where="​led-panel" ​position="​25;5" width="​130" labelWidth="​110"​  +
-  displayWidth="​20" height="​20" ​address="outputs"​ number="​14"​ labelAlignment="​hcenter"​  +
-  labelFontSize="​14"​ shape="​round"​ color="​green"​ type="​led">​ +
-  <​message>​Side pillar</message>​ +
-  <​message_ru>​Боковой упор</​message_ru>​ +
-</​gitem>​ +
- +
-<gitem inversion="​no"​ where="​led-panel" position="​5;​25"​ width="​20"​ displayWidth="​20"  +
-  ​height="20" address="​outputs"​ number="​22"​ shape="​round"​ color="​green"​ type="​led"​ /> +
- +
-<gitem inversion="​no"​ where="​led-panel" position="​25;​25"​ width="​130"​ labelWidth="​110"​  +
-  displayWidth="​20"​ height="​20"​ address="​outputs"​ number="​23"​ labelAlignment="​hcenter"​  +
-  labelFontSize="​14"​ shape="​round"​ color="​green"​ type="​led">​ +
-  <​message>​Rear pillar</​message>​ +
-  <​message_ru>​Задний упор</​message_ru>​ +
-</​gitem>​ +
- +
-<gitem inversion="​no"​ where="​led-panel" position="​5;​45"​ width="​20"​ displayWidth="​20"​  +
-  height="​20"​ address="​inputs"​ number="​13"​ shape="​round"​ color="​green" type="led" /+
- +
-<gitem inversion="​no"​ where="​led-panel"​ position="​25;​45"​ width="​130"​ labelWidth="​110"​  +
-  displayWidth="​20"​ height="​20"​ address="​inputs"​ number="​14"​ labelAlignment="​hcenter"​  +
-  labelFontSize="​14"​shape="​round"​ color="​green"​ type="​led">​ +
-  <​message>​Pedal</​message>​ +
-  <​message_ru>​Педаль</​message_ru>​ +
-</​gitem>​ +
- +
-<gitem inversion="​no"​ where="​led-panel"​ position="​5;​65"​ width="​20"​ displayWidth="​20"​  +
-  height="​20"​ address="​outputs"​ number="​10" ​  ​shape="​round"​ color="​green"​ type="​led"​ /> +
- +
-<gitem inversion="​no"​ where="​led-panel"​ position="​25;​65"​ width="​130"​ labelWidth="​110"​  +
-displayWidth="​20"​ height="​20" ​  ​address="​outputs"​ number="​15"​ labelAlignment="​hcenter"​  +
-labelFontSize="​14"​ shape="​round"​ color="​green"​ type="​led">​ +
-  <​message>​Vacuum</​message>​ +
-  <​message_ru>​Присоски</​message_ru>​ +
-</gitem>+
 </​code>​ </​code>​
  
-Result is  ​+Note that this will bring up the x-centring.xml file which describes what is actually inside the CentringView widget. This code merely indicates that the Probe Sensor Window button is to be placed on the main screen, pressing which will, in turn, bring up the CentringView widget screen.
  
-{{ mycnc-1280m5-002-4.png?700 }}+  * **where** is set to "x-reserv"​ 
 +  * **image** is used for the button to indicate what the button action will be to the user 
 +  * **action** specifies the command which will be perform when the button is pressed (in this case, the button toggles the visibility of the x-centring widget (found in the x-centring.xml file) 
 +  * type is set to "​button"​
  
-== Add Button with led display, that toggles Global Variable value and shows the current state ==+=== Rotation2View ===
  
-For described example machine runs the same g-code on left and right sides of the machine table. To increase a performance operator remove ready parts and install a new blank on one side of the table while the machine cuts new parts on another side.+Rotation2View is the window which allows to rotate the program part by some degree. It is brought up by clicking the Rotate button in the G-code tab on the main screen ​of myCNC software:
  
-Global variable #500 contains Current active side machine works (or going to work) with. +{{:​mycnc:​screen-config-026-rotate-button.png}}
-Variable value+
  
-0 - means machine works (or will start to work) with the left side, +The following window is brought up when clicking ​the button: ​
  
-means machine works on the right side. +{{:​mycnc:​screen-config-025-rotation2view.png}}
-   +
-We add a button to toggle current side. We add on-button indication and add LED displays to show current working side.+
  
-Button definition is shown below - +This will bring up the x-rotate.xml file which further describes internals of the window. In order to simply add a button so that the overall window can be brought up, the following ​code can be used:
-<code xml> +
-  <gitem where="​led-panel"​ type="​xbutton"​ position="​50;​90"​ width="​60"​ height="​60"​ image="​left-right"​  +
-  action="​direct-run:G90 G10 L186 P500 Q1" /> +
-</code+
  
-Led displays to the left and right  sides from button -  +<​code ​XML
-<​code ​xml+  <gitem where="​x-nclist" position="​10;60" ​height="55" ​width="​60"​  
-<​gitem ​inversion="​no" ​where="​led-panel" position="​5;90" ​width="40" ​height="60" name="​display-cnc-gvariable-500"  +  image="tabs/rotate-r" ​action="mywidget-toggle:x-rotate" type="button"></gitem>
-shape="square"​ color="​red"​ type="​led" ​/+
-<gitem inversion="​yes"​ where="​led-panel" ​position="115;​90"​ width="​40"​ height="​60"​ name="​display-cnc-gvariable-500"​  +
-shape="​square"​ color="​red" type="led" />+
 </​code>​ </​code>​
  
-Result is +  * **where** points to the x-nclist widget (describe above) which inserts this button into it 
 +  * **position**,​ **height** and **width** describe the button parameters within the x-nclist widget 
 +  * **action** specifies that pressing this button will toggle the x-rotate window visibility 
 +  * **type** is set to "​button"​
  
-{{ mycnc-1280m5-001-9.png?​700 }}+==== MyCNC Actions ====
  
 +All button-like screen components (button, xbutton, bdisplay, kspinbox2) run a **Handler** procedure when pressed or released event is activated by a mouse click or a touch screen tap. The Handler is defined in the "​action"​ attribute of an XML configuration item. 
  
-To add "​Current Side" indication on the button -  +List of actions is presented below:
-  change type <​del>"​button"</​del>​ "​xbutton +
-  add xattr="​xattr="​0;​0;​60;​60;​led;​green;​round"​ +
-  add name="​display-cnc-gvariable-500"​ to show current state of Variable #500 +
-  add image files array - images="​--left;​--right"​+
  
-images to show Variable state have the same size as the button ​itself, so image **--left** ​or **--right** ​will be drawn on the top of the button ​image.+^ Action Name ^ Description ^ 
 +| advanced-config | Brings up the full configuration dialogs window (this is the window typically accessed through Settings > Config) | 
 +| basic-config | Obsolete, was used to bring up a basic config settings window on some systems | 
 +| toggle-button-coordinates | Special purpose actionused to toggle between displaying program and machine coordinates (only one set of coordinates would be shown at a time) | 
 +| toggle-button-jog-enable | This toggle allows to enable/​disable jog completely (typically done for safety reasons ​so that the machine cannot accidentally move) | 
 +| toggle-button-soft-limits | This action will toggle whether the soft limits for the machine will be ON or OFF. This can also be done by heading into Settings > Config > Inputs/​Outputs/​Sensors > Limits and setting the check mark for Soft Limits Enabled there. | 
 +| toggle-button-mist | Coolant mist is toggled ON/OFF | 
 +| toggle-button-flood | Coolant flood (liquid) is toggled ON/OFF | 
 +| toggle-button-spindle | The spindle configuration uses the toggle-button-spindle and the toggle-button-ccw-spindle commands. By default, there are two commands sent to the spindle - power and direction. The power will cause the spindle to turn in the clockwise direction, while the ccw-spindle command will reverse the spin direction ​of the spindle. | 
 +| toggle-button-ccw-spindle-spindle | Reverses the spin direction of the spindle (counter-clockwise instead of clockwise) | 
 +| toggle-item:​ | This is a general toggle action command for any item (item name is specified after the colon). Item list can be found [[mycnc:​item_list|here]]. | 
 +| laser-marker- | Special purpose action reserved for laser marker machines. This action perform a test run in anticipation of the actual cutting process|
  
-Images for button base, "the left state" and "the right state" are+===Items===
  
-{{left-right.png?80}} +Items are a subset of actions, and are written in the following form item:​item-name (such as //​item:​motion-rapid-speed-xy//​)Items are different from actions in that items effectively describe a value that can be changed by some input (similar to Global Variables which store a value)In this way, there can exist both an action with some name, and an item with that same name, which are separate from one another (one will describe an action that will be taken, and the other will describe a value that will be changed by that action)
-{{left.png?80}} +
-{{right.png?80}}+
  
-code for button definition is +Items are often presented to the user on the myCNC software screen to display relevant information which can then be edited (such as the jog overspeed, spindle speed, etc). The relevant actions ​for such items would be along the lines of motion-overspeed-inc or motion-overspeed-dec,​ describing a particular action to perform with this item (value). ​
  
 +Items are typically used in conjunction with some input, as outlined in the Connections configuration dialog which can be found [[mycnc:​mycnc_configuration_dialogs|here]]. ​
  
-<code xml> +A list of commonly used items can be found in the [[mycnc:item_list|Item List]]. ​
-<gitem where="​led-panel"​ position="​50;​90"​ width="​60"​ displayWidth="​60"​ height="​60"​ image="​left-right"​  +
-type="​xbutton"​ action="​direct-run:G90 G10 L186 P500 Q1" +
-images="​--left-right;​left--right"​ name="​display-cnc-gvariable-500"​ xattr="​0;​0;​60;​60;​led;​green;​round"/>​ +
-</​code>​+
  
-Result screen is -+=== Player actions ===
  
-{{ mycnc-1280m5-001-10.png?700 }}+^ Action Name ^ Description ^ 
 +| player-play | Begins running the program | 
 +| player-play-confirm | Begins running the program after a confirmation popup has been clicked, to confirm that the user indeed wants to start the program run | 
 +| player-play-edge | Begins running the program from the edge (done for plasma profiles on thick materials/​when initial pierce or ignition is not possible at some point). | 
 +| player-play-edge-confirm | Begins running the program from the edge after a confirmation popup to ensure that the user wants to start from the edge | 
 +| player-jump1 | Special purpose command, done to jump to the first cutting/​piercing point in the program. Used on select user profiles. | 
 +| player-pause | Pauses the program run | 
 +| player-stop | Stops the program run. In myCNC, player-pause and player-stop are equivalent, as the controller remembers the machine position as the program is stopped, thus allowing it to serve as a pause | 
 +| player-skip-forward | Skips to the next G-code command | 
 +| player-skip-forward-10 | Skips 10 commands (forward direction) | 
 +| player-skip-backward | Goes to the previous G-code command | 
 +| player-skip-backward-10 | Skips 10 commands (backwards direction) | 
 +| player-skip-part-f | Skips to the next part in the code | 
 +| player-skip-part-b | Skips to the previous part in the code | 
 +| player-nc-reset | Resets the program back to the beginning | 
 +| player-nc-reset-confirm | Resets the program back to the beginning after asking for a confirmation in the form of a popup window | 
 +| player-back-to-path | Goes back to path after a stop | 
 +| player-back-to-path-confirm | Goes back to path, requires confirmation before the machine goes back to path | 
 +| player-play-back | Runs the program backwards | 
 +| player-nc-tie | Allows to tie a certain position to the reference zero program coordinate positionThis allows to move the entire program around the cutting sheet. Useful when, for example, a single part needs to be cut out from a program made up from many different parts at a different location on the working material from that used originally (for example, if the first run was faulty). This calculates the difference of the current selected point and the zero program coordinate, and then interpolates the same difference between the new selected point and the new zero program coordinate, moving the whole program over.  | 
 +| player-play-step | Run through a single line of code (next line) | 
 +| player-play-step-backward | Run through a single line of code (previous line) | 
 +| mdi-play | If the Manual Data Input field is not presented as a separate window, it is possible to enter some MDI commands, and then keep them entered until they are required (no need to immediately execute them). This //mdi-play command// will execute the stored MDI process. NOTE: This is a special user case feature, typically //​mdi-open//​ is used instead. | 
 +| mdi-open | Opens the Manual Data Input window |
  
  
 +=== Jog actions ===
  
 +^ Action Name ^ Description ^
 +| jog-0-plus, jog-1-plus, \\ jog-2-plus, jog-3-plus, \\ jog-4-plus, jog-5-plus, \\ jog-6-plus, jog-7-plus \\ jog-8-plus | Positive direction jog in the in  the X, Y, Z, A, B, C, U, V, W axes |
 +| jog-0-minus,​ jog-1-minus,​ \\ jog-2-minus,​ jog-3-minus,​ \\ jog-4-minus,​ jog-5-minus,​ \\ jog-6-minus,​ jog-7-minus,​ \\ jog-8-minus ​  | Negative direction jog in the X,​Y,​Z,​A,​B,​C,​U,​V,​W axes |
 +| jog-0-plus-1-plus | Simultaneous two-axes Jog, X+ Y+ |
 +| jog-0-plus-1-minus | Simultaneous two-axes Jog, X+ Y- |
 +| jog-0-minus-1-plus | Simultaneous two-axes Jog, X- Y+ |
 +| jog-0-minus-1-minus | Simultaneous two-axes Jog, X- Y- |
 +| jog-overspeed-inc \\ jog-overspeed-dec | Increment/​Decrement Jog Overspeed value (%) - the default jog speed is set to be 100%. |
 +| jog-overspeed-set: ​ | Set given Jog Overspeed value (%). The bounds for overspeed can be set in Settings > Config > Motion |
  
-== Add Buttons with LED display that runs PLC procedures and shows Output pin state == 
  
-We need to add 2 buttons on GUI main screen to fill up and drain water from plasma cutting machine water table.+=== Motion Settings Actions===
  
-{{water-up.png}} +^ Action Name ^ Description ^ 
-{{water-down.png}}+| step-float-inc \\ step-float-dec ​ | Increase/​decrease Jog Step SizeReserved for an arbitrary step size change (instead of a 0.01, 0.1, etc) | 
 +| step-size-inc \\ step-size-dec ​ | Increase/​decrease Jog Step Size by a set value | 
 +| motion-linear-acceleration-inc \\ motion-linear-acceleration-dec ​ | Increase/​decrease Motion Linear Acceleration value | 
 +| motion-linear-jog-speed-inc \\ motion-linear-jog-speed-dec \\ motion-linear-jogspeed-inc \\ motion-linear-jogspeed-dec | Increase/​decrease Motion Linear Jog Speed value | 
 +| motion-jog-speed-x-inc,​ \\ motion-jog-speed-x-dec,​ \\ motion-jog-speed-y-inc,​ \\ motion-jog-speed-y-dec,​ \\ motion-jog-speed-z-inc,​ \\ motion-jog-speed-z-dec,​ \\ motion-jog-speed-a-inc,​ \\ motion-jog-speed-a-dec,​ \\ motion-jog-speed-b-inc,​ \\ motion-jog-speed-b-dec,​ \\ motion-jog-speed-c-inc,​ \\ motion-jog-speed-c-dec,​ \\ motion-jog-speed-u-inc,​ \\ motion-jog-speed-u-dec,​ \\ motion-jog-speed-v-inc,​ \\ motion-jog-speed-v-dec,​ \\ motion-jog-speed-w-inc,​ \\ motion-jog-speed-w-dec,​ \\ motion-jog-speed-xy-inc,​ \\ motion-jog-speed-xy-dec,​ \\ motion-jog-speed-xyz-inc,​ \\ motion-jog-speed-xyz-dec | Increase/​decrease Motion **Jog** Speed value for given Axis | 
 +| motion-rapid-speed-x-inc,​ motion-rapid-speed-x-dec,​ \\ motion-rapid-speed-y-inc,​ motion-rapid-speed-y-dec,​ \\ motion-rapid-speed-z-inc,​ motion-rapid-speed-z-dec,​ \\ motion-rapid-speed-a-inc,​ motion-rapid-speed-a-dec,​ \\ motion-rapid-speed-b-inc,​ motion-rapid-speed-b-dec,​ \\ motion-rapid-speed-c-inc,​ motion-rapid-speed-c-dec,​ \\ motion-rapid-speed-u-inc,​ motion-rapid-speed-u-dec,​ \\ motion-rapid-speed-v-inc,​ motion-rapid-speed-v-dec,​ \\ motion-rapid-speed-w-inc,​ motion-rapid-speed-w-dec,​ \\ motion-rapid-speed-xy-inc,​ motion-rapid-speed-xy-dec,​ \\ motion-rapid-speed-xyz-inc,​ motion-rapid-speed-xyz-dec | Increase/​decrease Motion **Rapid** Speed value for given Axis | 
 +| motion-feed-speed-x-inc,​ \\ motion-feed-speed-x-dec \\ motion-feed-speed-y-inc \\ motion-feed-speed-y-dec \\ motion-feed-speed-z-inc \\ motion-feed-speed-z-dec \\ motion-feed-speed-a-inc \\ motion-feed-speed-a-dec \\ motion-feed-speed-b-inc \\ motion-feed-speed-b-dec ​ \\ motion-rapid-speed-c-inc \\ motion-rapid-speed-c-dec \\ motion-rapid-speed-u-inc \\ motion-rapid-speed-u-dec \\ motion-rapid-speed-v-inc \\ motion-rapid-speed-v-dec \\ motion-rapid-speed-w-inc \\ motion-rapid-speed-w-dec \\ motion-rapid-speed-xy-inc \\ motion-rapid-speed-xy-dec \\ motion-rapid-speed-xyz-inc \\ motion-rapid-speed-xyz-dec | Increase/​decrease Motion **Rapid** Speed value for given Axis | 
 +| motion-overspeed-inc \\ motion-overspeed-dec \\ motion-overspeed | Increase/​decrease/​set Motion **Overspeed** value (%) |  
 +| spindle-speed-inc \\ spindle-speed-dec \\ spindle-speed | Increase/​decrease/​set Current Spindle Speed (S) for current operationNew "​S"​ value in running g-code will overwrite Current Spindle Speed | 
 +| spindle-speed-restore | **Restore Default** Spindle Speed (S) | 
 +| spindle-overspeed-inc \\ spindle-overspeed-dec \\ spindle-overspeed | Increase/​decrease/​set Spindle Speed (S) |
  
-Need to add the button to the right from **Palnik ON** button ​- +=== Built-in Editor Actions ===
-{{ eco-001.jpg }}+
  
 +^ Action Name ^ Description ^
 +| editor-arrow-up | Go one line up in the code |
 +| editor-arrow-down | Go one line down in the code |
 +| editor-ncline-edit | Edits the current selected line of G-code |
 +| editor-ncline-insert | Inserts a line of code |
 +| editor-ncline-remove | Deletes the current selected line |
 +| editor-font-inc | Increase the font size for the editor G-code text |
 +| editor-font-dec | Decrease the font size for the editor G-code text |
 +| editor-numbers-toggle | Toggle the line number display to insert the current line number indicators into G-code |
 +| editor-selection-begin | Begin selection |
 +| editor-selection-end | End selection (the lines between the editor-selection-begin and editor-selection-end will be selected) |
 +| editor-selection-remove | Remove the selected lines |
 +| editor-selection-insert | Insert selected lines |
 +| editor-new | Create a new program file in the editor |
 +| editor-save-as | Save File As |
 +| editor-save | Save the editor file |
  
-Goto cnc-screen.xml in profile folder, find "​Palnik ON" line. Here it is: definition of **Palnik ON** button and a a text label under it -  +=== File Manipulation Actions ​===
-<code xml> +
-<gitem where="​ecocut-coordinates"​ position="​80;​205"​ width="​60"​ height="​60"​  +
-image="​Ecocut/​2a;​Ecocut/​1a"​ action="​cnc-mode-cutting-ignore"​ type="​toggle-switch"​ />+
  
-<gitem where="​ecocut-coordinates"​ position="​80;​265"​ width="​60"​ height="​20"​ type="​label" ​ +^ Action Name ^ Description ^ 
-fgColor="​white"​ labelFgColor="​white"​ labelFontFamily="​sans-serif"​ labelFontSize="​12" ​ +| save | Saves the file | 
-fontSize="​12"​ fontStyle="​bold"​ labelAlignment="​vcenter;​hcenter">​ +| open | Open selected file | 
-  <​message>Test Plasma</​message+| load-file: | Load a file. This will load a file from the predefined folders which can be set in Config ​Preferences ​Common | 
-  <​message_ru>​Поджиг</​message_ru>​ +| load-macro: | A test debug feature. Allows to load the macros which are referenced in the imported G-code directly into the NCList window. In this way, instead of using a single macro number to refer to a specific macro, the full macros will be written out in the NCList.| 
-  <​message_pl>​Palnik ON</​message_pl>​ +| file-close | Close the program file | 
-</​gitem>​ +| dxf-import | Import a DXF file into myCNC | 
-</​code>​+| image-import | Import an image into myCNC |
  
-**where="​ecocut-coordinates"​** - widget where button & label are placed 
  
-**position="​80;​205"​ width="​60"​ height="​60"​** - position, width and height of the button+=== Visualization Actions ===
  
-We need to add 2 buttons just after it +^ Action Name ^ Description ^ 
 +| zoom-in | Zoom in on the visualization | 
 +| zoom-out | Zoom out on the visualization | 
 +| fit-to-view | Fit the visualization into the screen | 
 +| 3dview-xy | 3D Visualization:​ show XY view | 
 +| 3dview-xz | 3D Visualization:​ show XZ view  | 
 +| 3dview-yz | 3D Visualization:​ show YZ view  | 
 +| 3dview-iso | 3D Visualization:​ show ISO view (isometric view with no vanishing point) | 
 +| 3dview-custom:​ | 3D Visualization:​ show Custom view, defined by Alpha, Beta, and Gamma angles for the rotation matrix ​ |
  
-<code xml> 
-<gitem where="​ecocut-coordinates"​ position="​150;​205"​ width="​60"​ height="​60"​ image="​Ecocut/​water-up" ​ 
-action="​direct-plc:​M240/​1"​ type="​button"​ /> 
-<gitem where="​ecocut-coordinates"​ position="​145;​265"​ width="​70"​ height="​20"​ type="​label"​ fgColor="​white" ​ 
-labelFgColor="​white"​ labelFontFamily="​sans-serif"​ labelFontSize="​12"​ fontSize="​12" ​ 
-fontStyle="​bold"​ labelAlignment="​vcenter;​hcenter"​ > 
-  <​message>​Water Fill</​message>​ 
-  <​message_pl>​Water Fill</​message_pl>​ 
-</​gitem>​ 
  
-<gitem where="​ecocut-coordinates"​ position="​220;​205"​ width="​60"​ height="​60"​ image="​Ecocut/​water-down"​  +=== Widget Manipulations Actions ​=== 
-action="​direct-plc:​M240/​0"​ type="​button"​ /> +These actions allow to display widgets on the screen which are then used to change certain machine values/navigate to different menus/etc. They are displayed either as popup windows on the main screen, or full windows which require navigation to return back to the main screen.
-<gitem where="​ecocut-coordinates"​ position="​215;​265"​ width="​70"​ height="​20"​ type="​label"​ fgColor="​white"​  +
-labelFgColor="​white"​ labelFontFamily="​sans-serif"​ labelFontSize="​12"​ fontSize="​12"​ fontStyle="​bold"​  +
-labelAlignment="​vcenter;​hcenter"​ > +
-  <​message>​Water Drain</message>​ +
-  <​message_pl>​Water Drain</​message_pl>​ +
-</​gitem>​ +
-</code>+
  
 +^ Action Name ^ Description ^
 +| show-inputbox | Obsolete version of the Manual Data Input |
 +| show-widget-centring | Shows the Centring widget (consists of probe widget command buttons to centre the tool with regard to some obstacles/​constraints) |
 +| show-widget-rotation | Brings up the rotation2view window (typically the Rotate button is located in the G-code tab on the main screen) |
 +| show-widget-sawcutting | Brings up the sawcutting widget (obsolete on newer software) |
 +| show-widget-diagnose | Brings up the Diagnostics window |
 +| show-widget-config | Brings up the Config (full settings) window |
 +| show-widget-edit | Brings up the Edit widget screen, which allows to alter a G-code file before importing it into myCNC |
 +| show-widget-lib | Brings up the library window |
 +| show-widget-tools | Brings up the tools window/tab |
 +| show-widget-log | Brings up the log window (typically found in Settings > Log) |
 +| show-widget-report | Shows the report window (typically Settings > Report) |
 +| show-widget-support | Shows the support widget, which contains update options for the firmware, application and the profile used |
 +| show-widget-user | Shows the user settings window for that particular profile |
 +| show-widget-work | Brings up the work area (useful to return from a window like the Diagnostics window back to the main screen) |
 +| mywidget-show:​ | Shows a widget (widget name specified after the colon) |
 +| mywidget-hide:​ | Hides a widget (widget name specified after the colon) |
 +| mywidget-toggle:​ | A command (such as a button pressed can either show, hide, or toggle a widget'​s visibility. It is sometimes preferable to have separate buttons for opening and closing a widget (so that it isn't closed accidentally),​ but mywidget-toggle allows to toggle the visibility of a widget with a single button |
 +| pendant-widget-open | Shows the pendant widget. This is typically used in older versions of the software (not on the 1366-series profile) to display a virtual pendant. |
 +| measure-surface | Obsolete. Reserved for surface measure commands on older versions of the software, newer versions have since switched to macros. |
 +| toggle-virtual-keyboard | Toggles the visibility of the virtual keyboard |
 +| mywidget: | Older version of the syntax for mywidget commands (still functional, but no longer developed further). The name of the widget would be set after the colon, and then, after a doubleslash,​ the show/​hide/​toggle command would be inserted. This has been largely replaced by the mywidget-toggle,​ mywidget-show and mywidget-hide syntax. |
  
-Result is - 
  
-{{ mycnc-1280m5-001-7.png?​700 }} 
  
-  Out pin #13 controls Water Fill,  +=== Application Actions ===
-  Out pin #12 controls Water Drain +
-   +
-Add LEDs display to the buttons - +
  
-1. Change type from "​button"​ to "​xbutton"​ +^ Action Name ^ Description ^ 
-2. Add **xatrr** attribute to buttons definition with LEDs position, width, height, colour and shape +| close-application | Close myCNC control software | 
-3. Add to button definition attribute address="​outputs"​ and number="​12"​ (or number="​13"​) ​to show output pin state+| cnc-config-save | Save myCNC configuration files to disk |
  
-<code xml> 
-<gitem where="​ecocut-coordinates"​ position="​150;​205"​ width="​60"​ height="​60"​ image="​Ecocut/​water-up" ​ 
-action="​direct-plc:​M240/​1" ​ 
-type="​xbutton"​ xattr="​4;​4;​16;​16;​led;​green;​round"​ address="​outputs"​ number="​13"/>​ 
-<gitem where="​ecocut-coordinates"​ position="​220;​205"​ width="​60"​ height="​60"​ image="​Ecocut/​water-down" ​ 
-action="​direct-plc:​M240/​0" ​ 
-type="​xbutton"​ xattr="​4;​4;​16;​16;​led;​green;​round"​ address="​outputs"​ number="​12"​ /> 
-</​code>​ 
  
-Result is - +=== Hardware Manipulation actions ===
  
-{{ mycnc-1280m5-001-8.png?700 }}+^ Action Name ^ Description ^ 
 +| servo-pid-on | Turns ON the Servo PIDs | 
 +| servo-pid-off | Turns OFF the Servo PIDs | 
 +| hw-pwm-inc | Increases the PWM value in preset increments (currently, these increments are set to 20) | 
 +| hw-pwm-dec | Decreases the PWM value in preset increments | 
 +| hw-dac-inc | Increases the DAC value in preset increments | 
 +| hw-dac-dec | Decreases the DAC value in preset increments | 
 +| hw-direct-binary-set- | Directly sets an output value (for example, //​hw-direct-binary-set-5//​ to turn on output 5Using direct hardware commands instead of Hardware PLC procedures allows to free up the Hardware PLC process and to prevent situations where long PLC commands would be interrupted by a port set / port clear due to a new input sent to the controller | 
 +| hw-direct-binary-clear- | Directly clears an output value (for example, //​hw-direct-binary-clear-5//​ to clear output 5 | 
 +| thc-arc-voltage-ref-inc | Increases the reference arc voltage value | 
 +| thc-arc-voltage-ref-dec | Decreases the reference arc voltage value | 
 +| thc-jog-speed-dec | Decreases the THC jog speed | 
 +| thc-jog-speed-inc | Increases the THC jog speed | 
 +| <​del>​thc-jog-pos</​del>​ | Obsolete. Used to jog the machine in a positive direction during Torch Height Control, has since been rendered obsolete due to the Settings > Config > Technology > THC > Accept Jog while job is running setting. This setting allows the machine to automatically distinguish whether the input to move vertically is done during THC or not, and to account for such movement | 
 +| <​del>​thc-jog-neg</​del>​ | Obsolete, similar to thc-jog-pos - was used to jog machine in a negative direction during THC. | 
 +| dev-thc-jog-pos | Multidevice positive direction Torch Height Control jog | 
 +| dev-thc-jog-neg | Multidevice negative direction Torch Height Control jog |
  
-To control Water Fill/Drain PLC procedure M240 with parameter "​1" ​(to Fillor "​0" ​(to Drainis used. +| toggle-widget-centring | Toggles the centring widget visibility on/off (centring widget code can be found in x-centring.xml
-PLC procedure M240 is described [[plc:​plc_examples#​Water_Fill_and_Drain_control|Here]]+| toggle-widget-rotation | Toggles the rotation widget visibility on/off | 
 +| toggle-widget-sawcutting | Toggles the sawcutting widget visibility on/​off ​(obsolete on newer software versions| 
 +toggle-widget-user | Toggles the user settings widget visibility on/off |
  
 +| toggle-button-flood | Toggles the flood state on/off (liquid) |
 +| toggle-button-coolant | Toggles the coolant state on/off |
 +| toggle-button-spindle | Toggles the spindle on/off state. This will cause the spindle to either not spin, or spin in the clockwise direction. |
 +| toggle-button-ccw-spindle | Toggles the reversal of spindle direction from clockwise to counterclockwise |
 +| toggle-button-mist | Toggles the mist state on/off |
 +| <​del>​toggle-button-cv-mode</​del>​ | Obsolete. Used for constant velocity mode toggle. |
  
-== Add display to show current ​PLC status for Gas Cutting ​==+==PLC Actions ===
  
-We will fix **1024G** profile. The main screen of the profile is shown below. 
  
-{{ mycnc-1024g-001.png?700 }}+^ Action Name ^ Description ^ 
 +| soft-plc-run: | Runs software PLC commands | 
 +| soft-plc-stop:​ | Stops a software PLC process | 
 +| *soft-plc-stop:​ | Stops both a software PLC process and the program itself from running | 
 +| plc-run: | Runs a Hardware PLC process | 
 +| direct-plc: | Same as plc-run (either of these commands can be used) - runs Hardware PLC | 
 +| multidev-plc-run:​ | Runs PLC in a multidevice configuration | 
 +| switch-cnc-gvariable | Switches a gvariable value between some data on a loop (for example, on every button press a gvariable gets assigned the next value from the data list)This syntax is not used in the newer projects, cnc-gvariable-switch,​ cnc-gvariable-clear,​ etc are used instead. | 
 +| cnc-gvariable-switch | Newer syntax for a global variable switch between values from a data set. Data points will be written separated by a comma, and the next value in the list will be taken on every switch command | 
 +| cnc-gvariable-toggle | Toggles a global variable (writes 0 or 1 into the global variable, depending on the previous value) | 
 +| cnc-gvariable-clear | Clears the value of a global variable |
  
-Put PLC process display to the top of the empty area next to "THC Speed" display.+=== Job Actions ===
  
-To add the display -  +^ Action Name ^ Description ^ 
-  * find and open to edit "cnc-screen.xml" file in profile folder +| direct-run: | Allows for a direct run of a command from a BDisplay elementThis will allow for a direct command which will be executed when a BDisplay element is clicked/​pressed| 
-  * find reference "THC Speed" display - <code xml> +| direct-run-confirm: | Will execute a command directly after a BDisplay element has been clicked AND after the user has confirmed that they want to proceed with the action via a confirmation dialog| 
-<gitem fgColor="​cyan"​ where="​w-operate"​ labelFontStyle="​bold"​ format="​%5.1f" K="​1."​ height="​30"​ +| radio-confirm | Used for RadioDisplay elements ​to bring up a popup to ask the user to confirm whether the value should be changed before taking action | 
-type="​display"​ deviation="​0.01"​ name="​display-gvariable-5493" bgColor="​transparent"​  +| mode-cutting-ignore | Ignores cutting commands to simply move over the material to check the machine movement path. Replaced by global variable #7530 in the more recent profiles (1366 series) | 
-displayWidth="​140"​ labelWidth="​100"​ fontStyle="​bold"​ fontSize="​20"​ orientation="​horizontal">​ +| mode-cutting-accept | Accepts cutting commands from the control program |
-  <​message>​THC Speed</​message>​ +
-  <​message_ru>​Z Слежение</​message_ru>​ +
-</​gitem></​code +
-  * Add new display (easy way to copy-paste "THC Speed" display and edit it+
-  * Remove "​name",​ "​K"​ attributes +
-  * Add "​address"​ attribute ​to organize process display - <​code>​address="​plc-proc"</​code>​ +
-  * Change type <​code>​type="​radio-display"</​code>​ +
-  * Edit "​format"​ attribute ​<​code>​format="​No Cutting=0;​Ignition=50;​PreHeat=51;​Cutting=60"</​code>​ +
-  * Translate text inside format attribute if need local language messages ​<​code>​format="​Ожиидание=0;​Поджиг=50;​Подогрев=51;​Резка=60</​code>​ +
-  * Edit bgColor, fgColor, fontSize attributes to get nice looking display+
  
-A complete code  +| mdi-save-list | Reserved for a procedure in which a series of commands are entered through the Manual Data Input process, and which are then saved as a command list in a file. Contact myCNC Support for more information on this action. |
-<code xml> +
-<gitem fgColor="​cyan"​ where="​w-operate"​ labelFontStyle="​bold"​  +
-type="​radio-display"​ address="​plc-proc"​ format="​Ожидание=0;​Поджиг=50;​Подогрев=51;​Резка=60"​  +
-height="​30"​ displayWidth="​140"​ labelWidth="​100"​ bgColor="​black"​ +
-fontStyle="​bold"​ fontSize="​16"​ orientation="​horizontal">​ +
-  <​message>​Proc</​message>​ +
-  <​message_ru>​Процесс</​message_ru>​ +
-</​gitem></​code>​+
  
-Screen result is -+| mode-show-ruler | Shows a ruler in the visualization window which indicates the 2D part's dimensions (width/​length) |
  
-{{ mycnc-1024g-001-1.png?​700 }}+| mode-show-dimension | Shows the overall dimensions of the part on the program visualization screen (width/​length) |
  
 +| mode-show-workarea | Shows a box around the program visualization which will denote the work area (useful to see the minimum material dimensions necessary to fit the entire program file in) |
  
-== Add "Move A to 0" button to run macro with confirmation == 
  
-{{ mycnc:​mycnc-move-to-a-0.png?​700 }} For 3 axes machine we have a button **>​0<​** to moves machine to work 0 position. +=== OS/System Actions ===
-For machines with rotational axes it is convenient to have similar button to move rotational axis **A** to work 0.+
  
-We add this button ​to the main screen on the left of **>​0<​** button. +^ Action Name ^ Description ^ 
-Here is **Move To 0** definition ​+| system-cmd | Run a system command | 
 +| application-close | Close MyCNC application | 
 +| application-close-confirm | Run confirmation dialog ​to Close MyCNC application (will ask the user to confirm via a popup window before closing ​the application) | 
 +| application-minimize | Minimize MyCNC Application |
  
-<code xml><​gitem type="​button"​ 
-where="​magic" ​ 
-image="​parking/​move-to-0" ​ 
-action="​direct-run-confirm:​M333"  ​ 
-position="​1200;​640"​ width="​80"​ height="​80">​ 
- <​message-confirm>​Move to Work (0,0,Tool Lift) position (macro M333). Are you sure?</​message-confirm>​ 
- <​message-confirm_ru>​Переместить в положение (0,0, Tool Lift) (макро M333)?</​message-confirm_ru>​ 
-</​gitem>​ 
-</​code>​ 
  
-Add on the left **Move To A** definition - +=== CNC Variables manupulation Actions ===
  
-<code xml><gitem type="​button"​  +^ Action Name ^ Description ^ 
-where="​magic"​  +<del>direct-set-cnc-var</​del>​ | Obsolete | 
-image="​parking/​move-to-A" ​ +| <​del>​cnc-variable:</del| Obsolete | 
-action="​direct-run-confirm:M335"  +<del>cnc-gvariable-dec,​ cnc-gvariable-inc</del | Obsolete | 
-position="​1120;​640"​ width="​80"​ height="​80"​+<del>cnc-variable-dec,​ cnc-variable-inc,​ \\ cnc-variable-change,​ cnc-variable-toggle,​ cnc-variable-set,​ cnc-variable-clear,​ \\ cnc-variable-vset,​ cnc-variable-switch</del | Obsolete | 
-   ​<message-confirm>Move to A=0 position (macro M335). Are you sure?</message-confirm+| <​del>​cnc-vm-variable-dec,​ cnc-vm-variable-inc</del| Obsolete | 
-   ​<message-confirm_ru>Вернуть в А=0 (макро M335)?</message-confirm_ru+| <​del>​device-variable-dec,​ device-variable-inc</del| Obsolete |
-</gitem+
-</code>+
  
-  * **type="​button"​** ​Button definition +| item-switch: | Used to switch between different values/labels for a certain item (allows ​to switch between options on a preset list| 
-  * **where="​magic"​** - Name of Parent Widget +run-numpad| Opens the numpad widget | 
-  * **image="​parking/move-to-A"​** - Button skin image filename ​(SVG format, folder relative ​to **/​myCNC/​art/​buttons-no-theme/​**+| item: | See [[mycnc:item_list|Common Item List]] for more information|
-  * **action="​direct-run-confirm:M335"​** - What to do if button pressed -  +
-    * **direct-run-confirm:** - Open Message box to confirm, then  +
-    * run G-code sequence (**";"​** is used as separator of g-code blocks) +
-  * **position="​1120;​640"​ width="​80"​ height="​80"​** - button position on Parent Widget, width and height of button +
-  * **<​message-confirm>​Move to A=0 position (macro M335)Are you sure?</​message-confirm>​** - message to show in Message Box +
-  * **<​message-confirm_ru>​Вернуть в А=0 (макро M335)?</​message-confirm_ru>​** - message to show for Russian language ​+
  
-{{ mycnc:​mycnc-move-to-a-0-1.png?700 }} +| fake | Empty Handler ActionNothing happens when you run this action |
-Screen with **Move To A** button+
  
-{{ mycnc:mycnc-move-to-a-0-2.png?700 }}Message Box when **Move To A** button pressed+| myitem-value-inc, myitem-value-dec | Increement/​Decrement XML item value by name |
  
-If button OK pressed on Message Box, g-code line **M335** (which is macro actually) will be executed to move A axs to zero.+=== HMI  Actions ===
  
-[[mycnc::move-a-to-0|M335 macro to move A to zero is described ​here]]+^ Action Name ^ Description ^ 
 +| search-nc-position | Opens a dialog window to locate the line for the **Run From Here** command | 
 +| file-refresh | Refresh the program file | 
 +| row-n-column | Open **Row And Column Multiplication/​Nesting** Dialog | 
 +| dialog-rotate | Open Dialog for the program rotation | 
 +| mypopup-show| Show custom defined Popup widget | 
 +| mypopup-toggle: | Toggle (show/​hide) ​custom popup widget | 
 +| mode-jog-unlimited | Switch ​to Unlimited Jog Mode | 
 +| show-simple-edit | Show simple text editor window ​ (Ver #1) | 
 +| show-simple2-edit | Show simple text editor window ​ (Ver #2) | 
 +| rotate-nc-last ​Rotage NC program ​to previously defined angle | 
 +| cnc-cutchart-save | Save the current cutting data to the Cutchart | 
 +| cnc-cutchart-load | Load cutting data for selected Cutting Mode | 
 +| run-from-here | **Run From Here** command - start job from the selected line |
  
  
- +==== MyCNC screen configuration ​examples ​==== 
-== Add Centring Widget on main GUI screen ​== +The examples for the screen ​configuration can be found here[[mycnc:mycnc_screen_configuration:​screen_configuration_examples|Screen configuration examples]]
- +
-myCNC software has Centring widget to work with probing sensor and find internal and external centers, edges, corners on parts. +
-{{ mycnc:​mycnc-probing-001.png?​500 }} +
-Fig. Centring Widget +
- +
-There is just 1 line to configure Centring Widget in cnc-screen.xml configuration ​file.  +
-<code xml><​gitem type="​centringview"​ where="​magic"​  +
-bsize="​80"​ +
-position="​0;​80"​ width="​880"​ height="​320" ​ +
-hidden="​1"​  +
-bgColor="#​c0c0c0">​centringview</​gitem></​code>​ +
- +
-  * **type="​centringview"​** - Centring Widget definition +
-  * **where="​magic"​** ​ - name of Parent Widget +
-  * **bsize="​80"​** - size of buttons +
-  * **position="​0;​80"​ width="​880"​ height="​320"​** - Position of Centring Widget on the Parent WIdget, width and height of Centring Widget +
-  * **hidden="​1"​** - Centring Widget is hidden on the start of GUI +
-  * **bgColor="#​c0c0c0"​** - Backgroundcolor of Centring Widget +
- +
-Centring Widget takes a lot of space on the GUI screen, so it's convenient to have it hidden while normal work and show the widget only when work with Probe sensor.  +
-To show/hide Centring Widget usually used on-screen button.  +
-<code xml><​gitem type="​button"​ +
-image="​probing/​centring-unit"​ action="​toggle-widget-centring"​ +
-where="​magic"​  +
-position="​1120;​0"​ width="​80"​ height="​80"​ /></​code>​ +
-  * **type="​button"​** - Button definition +
-  * **image="​probing/​centring-unit"​** - image for the button skin (in SVG format, relative to images folder "/​myCNC/​art/​buttons-no-theme/​ +
-  * **action="​toggle-widget-centring"​** - Action definition for pressing the button - Show/Hide Centring Widget +
-  * **where="​magic"​** - name of Parent Widget +
-  * **position="​1120;​0"​ width="​80"​ height="​80"​** - Button position on the Parent Widget, width and height on the button in pixels +
- +
-{{ mycnc:mycnc-centring-01.png?​700 }} +
-{{ mycnc:mycnc-centring-01-1.png?​700 }}+
  
mycnc/mycnc_screen_configuration.1538405179.txt.gz · Last modified: 2018/10/01 10:46 by skirillov