Download the bilingual offline manual (ZIP, 8.7 MB; original-resolution screenshots included)

Contents · 中文版

The preceding chapter introduced a configuration menu by moving Deployment. This chapter follows the menu itself: where its labels come from, how submenu arrows appear, why some items are unavailable or absent, and how a selection passes its result to a script.

We continue with existing standard functions. The example selects InnerHole Probe from the right-hand control area's menu and assigns it to an existing empty position. It checks the assignment without clicking the probing button.

1. Start with the preceding single-level menu

Click the screenshot to enlarge it. Full-resolution screenshots are included in the offline package.

Figure 1. Function Key Configuration Menu, opened by right-clicking the original F5 Deployment button on Parameter. Its selectable functions are listed directly, without another level.

The important statement in the original entry script is:

widgetFunc["PopMenu","","",915]

The last argument, 915, asks the application to build a menu from parameter #915. Menu entries primarily come from parameter items; a separate .ui file does not draw each of these rows.

In the previous lesson, selecting Empty or Deployment called the existing selmenufunc to change a button assignment. We now follow the same approach into submenus. This lesson leaves the original F5 assignment intact.

2. Open the right-hand control area's menu

Click the screenshot to enlarge it. Full-resolution screenshots are included in the offline package.

Figure 2. Start at the familiar Program → Toolpath Preview page. The left side shows an offline preview of the existing program; this lesson concerns the controls on the right. Their first row reads MPG Guide, A+, Y+, Z+, blank, blank. We use the fifth position.

In a practice copy, log in using the existing developer account so the top-right identity reads Super Administrator. Right-click the fifth blank position in the first row:

Click the screenshot to enlarge it. Full-resolution screenshots are included in the offline package.

Figure 3. The actual heading is Manual Controls Function Key Configuration Menu. The check beside Empty indicates the position's current assignment. Arrows beside entries such as Manual control and Tool setting/probing lead to another level.

Expand Tool setting/probing:

Click the screenshot to enlarge it. Full-resolution screenshots are included in the offline package.

Figure 4. A direct native submenu capture. It displays InnerHole Probe on one line. The stored name contains a line break, which appears as two lines on the button.

Select InnerHole Probe to obtain this result:

Click the screenshot to enlarge it. Full-resolution screenshots are included in the offline package.

Figure 5. The fifth position in the first row now displays InnerHole / Probe. This assigns an existing function; it neither defines a new probing method nor executes probing.

Stop at the result in Figure 5. Left-clicking the assigned button would enter the actual probing function. We do not perform that action here; the input window was explained in the parameter-window chapter. To restore the original layout, right-click this button and select Empty in the first-level menu.

The screenshots show the standard interface. Coordinates, filenames, and parameter values are examples; use the values appropriate to your configuration.

3. Find the entry script, then the menu parameters

Paths are relative to the runtime directory.

The fifth position is numbered 4. Its original position attributes are:

-A: (rightClickedEvent:/env/program/ctrlfuncmenu[0](#911=4<<#910=#911item4))
-C(#911item4!=0||#1026item0==2)
-V

Right-clicking records #911=4, copies the position's current function into #910, and runs ctrlfuncmenu. The last two lines keep assigned positions visible; an empty position is visible to the developer identity for configuration.

The complete ctrlfuncmenu script is:

IF#1026.item[0]!=2GOTO1
widgetFunc["PopMenu","","",910]
N1

Compared with the previous chapter, the menu number changes from 915 to 910. The entry script supplies the permission check. PopMenu does not automatically require developer identity for every menu.

4. What the menu parameter fields do

These are the main fields this system's PopMenu reads. Relate them to the example first; you do not need to memorize the whole table.

These fields follow the menu's rules here. itemmin is not an input minimum, itemunit is not a physical unit, and itemdesc is not help text. Read them according to their actual use.

An entry can override its displayed name using -T(...) inside item[i]. Otherwise, it uses itemtitle[i]. The example's function names come from itemtitle, so an extra -T definition is unnecessary.

5. How an entry becomes a submenu

The controlling field is itemmin:

The first-level menu contains these actual values:

#910.itemtitle[9] is currently empty, yet Figure 3 displays Tool setting/probing. A submenu entry takes its label from #924.title. Editing the empty parent-item name may therefore leave the visible label unchanged.

Also distinguish a menu title from a heading row. The unselectable Manual Controls Function Key Configuration Menu at the top of Figure 3 is item 0, with these attributes:

-C(1)
-E0

The condition is always true, so this row is disabled. Setting #910.title does not automatically create this extra row; the configuration explicitly defines item 0.

Menus can have further levels. In the existing configuration, item 11 of #910 refers to #926, and #926.itemmin[9] refers to #950. The latter retains a Chinese title for axis-mapping multi-face machining. Its parent entry requires #929item7==1; the loaded value here is 0, so this path is not expanded in the screenshots. We did not enable the feature for illustration. The current English language pack also does not assign English names to this #950 group, so a newly translated label must not be presented as existing English UI wording.

Each submenu should refer to the correct separate menu parameter. The current construction code does not detect circular references back to the same menu or an ancestor. Do not create such references.

6. Read the complete InnerHole Probe entry

This entry is item 6 in #924. Its existing definition is:

The original attribute text in #924.item[6] is:

-C(#910==50)
-R0
-C(#911item0==50||#911item1==50||#911item2==50||#911item3==50||#911item4==50||#911item5==50||#911item6==50||#911item7==50||#911item8==50||#911item9==50||#911item10==50||#911item11==50||#911item12==50||#911item13==50||#911item14==50||#911item15==50||#911item16==50||#911item17==50||#911item18==50||#911item19==50||#911item20==50||#911item21==50||#911item22==50||#911item23==50||#911item24==50||#911item25==50||#911item26==50||#911item27==50||#911item28==50||#911item29==50||#911item30==50||#911item31==50||#911item32==50||#911item33==50||#911item34==50||#911item35==50)
-E1

The long condition simply checks all 36 positions for function 50. Understand its first two comparisons, then follow the same pattern through the remaining positions:

• When the first condition is true, -R0 checks the entry: the position being configured currently uses this function.
• When the second condition is true, -E1 disables the entry: some position already uses this function.

After assignment, right-clicking the same button shows this function checked and unavailable for repeated selection. Right-clicking another empty position shows it unchecked but still unavailable because it is already assigned. Both cases were checked in the native menus.

There are three different numbers in this example:

They need not match. Use function 50 to find the action, menu item 6 to find the name, and position 4 to find the button to update.

7. Absent, unavailable, and checked mean different things

Click the screenshot to enlarge it. Full-resolution screenshots are included in the offline package.

Figure 6. Manual control opened from another empty position. The loaded configuration already places the relevant X/Y/Z/A functions on the panel, while the B/C entries are unassigned. This indicates function assignments, not axes currently moving.

The 1 in -E1 identifies a condition, not a function or menu row. -R controls menu checking here; an input widget's read-only interpretation does not apply. The original stylesheet may give disabled entries a bright background, so brightness alone is insufficient.

An existing creation condition is the full contents of #919.itemunit[0]:

<<#912itemmax0==1

The empty part before << means no icon. The condition after it determines whether X+ Manual Control is created. Item 1, X- Manual Control, uses the same condition.

In the isolated check, temporarily changing the value read by this condition from 1 to 0 and reopening the menu omitted both X entries. Restoring it to 1 and reopening restored them; other axes' entries remained. This is an in-memory verification comparison, not an instruction to alter machine-axis configuration for a menu exercise.

The first-level ATC branch is another example: #910.itemunit[12] contains <<#901item0!=0. The loaded tool-magazine type is 0, so Figure 3 omits this branch.

The submenu in Figure 4 defines 12 items but currently shows 10; two are filtered by their own conditions. Counting visible rows does not give the original parameter item number. Hidden entries do not renumber #924.itemdesc[6].

PopMenu constructs the menu and checks conditions each time it opens. Close and reopen after changing names or creation conditions. Do not interpret -D as continuously rebuilding every entry while a popup remains open.

8. Where icons, names, and appearance belong

The current example does not assign menu icons. The source supports these locations:

For a parent entry pointing to a submenu, the parent's itemunit can still control whether the branch is created, but its icon is read from the submenu's own unit. Changing only the parent's icon text does not follow the ordinary-action rule in this case.

Icon loading and text-override rules are confirmed from source; this lesson does not add icons or rename entries for its screenshots. Referenced files should accompany the configuration resources, with their actual existence checked.

9. How a selection passes a number to a script

The entry's original selection definition is:

/env/program/selctrlfuncmenu<<#910=50

Before << is the selection script path; after it is an assignment evaluated before that script is called. Right-clicking already recorded #911=4. Selecting the menu entry now sets #910=50. The complete original script then contains:

#911.item[#911]=#910
widgetFunc["setWidgetAttribute",#911.itemtitle[#911],"",#911.itemdesc[#911.item[#911]]+#911.itemunit[#911]]

Substituting the example values gives:

The new button therefore receives the existing function's name and actions while retaining right-click configuration. This script does not update the F1–F12 records in #9995, unlike the preceding chapter's four-line Parameter script.

The entry's itemversion[6]=1 is its Qt-script call setting. Do not confuse it with [1] in a button event path:

The actual Qt call also depends on the containing form and interpreter availability. Retain the existing 1 here; changing it to NC does not make it a faster configuration call. An ordinary menu action takes its call definition from itemdesc: construction clears events parsed from item before adopting this path.

PopMenu waits for menu interaction to end, but this branch queues the selection-script call. Menu closure alone does not establish that code immediately after PopMenu will run after the selection script finishes. The standard design puts the update inside selctrlfuncmenu, with the required numbers prepared before the call.

10. Separate assigning the probing button from executing probing

The menu selection is now complete. The actual probing entry is in the existing #911.itemdesc[50]:

-T(#924itemtitle6)
-D
-C(#319item3==1)
-E0
-A: (clickedEvent:customprobe/centerprobing.nc[2])

It displays the corresponding menu name and defines a click that calls the probing NC. Here, [2] in the button event path means the NC channel. It governs a different operation from the menu's itemversion=1.

Trace the two paths separately:

This connects chapter 4's input window, chapter 5's function panel, and this menu chapter: an existing probing function can be selected in the menu, assigned to a button, and later entered through that button for its inputs and actions.

center-install helps trace the original name and action definitions, but it is a leftover from an earlier component deployment and is no longer called. Current menus use loaded parameters and the active language pack. Editing that historical file does not automatically update the next menu opening.

11. How to inspect an existing menu before changing it

Follow this order before deciding what to edit:

1. Find the entry. Follow the button event to its script and identify the PopMenu parameter number. If nothing opens, check the entry permission first.
2. Follow submenu references. Read the parent's itemmin to locate the child parameter. Visible submenu names may not be stored in the parent table.
3. Identify the original item number. Match its name, conditions, and selection definition by that number, without renumbering visible rows.
4. Identify the intended change. Names involve title fields and language packs; availability involves conditions; selection results involve itemdesc; actual business actions require following the function definition further.
5. Check the related records. This example joins menu 924 item 6, function 50, and position 4. Changing one number does not automatically update the others correctly.
6. Reopen and inspect. Check names, levels, omitted entries, checks, and availability. Then check the changed parameter, button caption, and events. Verify saving and restarting separately as part of the delivery process.

Common symptoms point to these checks:

Next, follow main-screen axis configuration: selecting an axis changes a shared flag that also controls visibility of its coordinate row.

Previous: Function-key configuration · Next: Axis configuration · Reading guide