IMDTouchKnowledge BaseShop main store

Troubleshooting

C-more Micro Alarm Control Setup Ignores Double-Clicks

HMI and touchscreens Published 5 min read

Short answer

C-more Micro binds the double-click that launches a Navigation window item to its text label, so a double-click on the icon does nothing. Aim at the words 'Alarm Control Setup' in the Function tab, or use the Setup menu's Alarm Control Setup command; reinstalling will not change anything.

On this page
  1. Why the tree ignores the click
  2. The fix: aim at the text
  3. Every path to the same dialog
  4. Working the case: V4.51.0 on Windows 10 64-bit
  5. When the text label also fails
  6. Prove the alarm setup stuck
  7. Questions asked

Double-click the text of the item, not its icon. In the C-more Micro programming software, the Navigation window binds the double-click that launches a Function tab item to the item's text label, so a double-click that lands on the icon does nothing: no dialog, no error, no change to the project. The Setup menu's Alarm Control Setup command opens the same dialog every time. This is a hit-target convention, not a corrupted project, a damaged install, or a version defect, so reinstalling the software will not change it.

Why the tree ignores the click #

Each item in the Navigation window's Function tab has two regions: the icon glyph on the left and the text label beside it. The double-click command is bound to the label region only, and a double-click on the icon never raises the configuration dialog. The C-more documentation for the Navigation window's Function tab describes the same gesture: select the tab, then double-click on the item by its name. The dialog is a standard stop on this path — the vendor's online tutorial series gives Alarm Control Setup its own segment, part 2 of 6 — so nothing about the destination is broken.

The diagnostic split matters more than the click itself. A menu command that opens the same dialog proves three things at once: the dialog code loads, the project database reads and writes, and the panel and protocol configuration are intact. One failing launch path plus one working launch path points at input handling — where the click landed — not at the software or the project. The same editor family has other behaviors that read as faults until you find the convention behind them, such as why C-more Micro preview screens show out of order, which is a sort convention rather than corruption.

The fix: aim at the text #

  1. Open the project and select the Function tab in the Navigation window.
  2. If the branch is collapsed, single-click the expand arrow to open it.
  3. Move the cursor over the words Alarm Control Setup, the text itself and not the icon to its left.
  4. Double-click. The Alarm Control Setup dialog opens.
  5. Run the round-trip checks at the end of this article before you trust the alarm configuration.

Keep the menu command as the everyday fallback: it opens the dialog no matter where the tree focus sits.

Every path to the same dialog #

Path Behavior
Function tab, double-click on the text label Primary route; opens the dialog
Function tab, double-click on the icon Does not launch; see the icon question in the FAQ
Setup menu, then Alarm Control Setup Menu bar; opens regardless of tree state
Right-click the tree item Opens through the context-menu command where your build shows one

Working the case: V4.51.0 on Windows 10 64-bit #

Inputs, each with its source:

  • Software: C-more Micro programming software V4.51.0, from the report.
  • Host: Windows 10, 64-bit, from the report.
  • Failing action: a double-click on the icon beside Alarm Control Setup in the Function tab.
  • Working action: the Setup menu's Alarm Control Setup command.
  • Control machines: Windows 7 and other Windows 10 64-bit machines, where the same double-click opened the dialog — those operators clicked the label.
  • One uninstall and reinstall attempted; the behavior did not change.

Rule in words: count the launch paths that reach one dialog. One path failing out of two means the dialog and the project are intact and the fault sits in the failed path's input handling. Two paths failing means a project or software fault.

The arithmetic written out: launch paths to this dialog = 2 (tree label, menu). Paths that work = 1. Paths that fail = 1. Failing paths = 1 of 2, below the 2-of-2 threshold that would move this case to the project-or-software branch.

Result: the label double-click opens the dialog on the reporting machine, on the same project and the same installation, while the icon double-click still does not. The control machines match once the click lands on the text, and the reinstall produced zero change.

Decision: with one failing path of two, keep the installation, aim the double-click at the label, and route through the Setup menu whenever the tree does not respond. Only when both paths fail do you move to the escalation list below.

When the text label also fails #

If a double-click squarely on the words opens nothing, the hit-target explanation is exhausted and you have a real fault. Work in this order:

  1. Try the same command from the menu bar. If it also fails, the dialog or the project is at fault, not the tree.
  2. Create a blank project for the same panel model and PLC protocol. If the dialog opens there, the original project file is suspect — import or rebuild the screens into the fresh project.
  3. Record the panel model, PLC protocol driver, and landscape or portrait orientation before escalating; feature availability is filtered by model and driver, and these are the first questions that come back.
  4. Establish whether the function ever worked on this machine. Never worked points at configuration or model support; worked and then stopped points at a project change, a software update, or a Windows display change.
  5. Check display scaling. On Windows 10 with per-monitor scaling above 100 percent, legacy dialogs can open off-screen or behind the main window, so press Alt+Tab or scan the taskbar for a hidden modal window before declaring the dialog dead.
  6. Run the software as an administrator. Restricted write access to the install directory or the user profile can suppress a dialog that persists settings on open.

Reinstalling stays the last step, not the first response: it changed nothing in this case and costs a full cycle.

Prove the alarm setup stuck #

  1. Open Alarm Control Setup from the Function tab by double-clicking the label; the dialog should appear immediately.
  2. Change one alarm entry and click OK.
  3. Reopen through the menu path and confirm the change is present and that both paths show identical data.
  4. Save the project, close the software, reopen the project, and confirm the entry survived the round trip to disk.
  5. Transfer the project to the panel, force the tag condition, and confirm the alarm displays when the condition is true and clears when it clears.

Alarm setup is part of operator protection: prove each alarm on the panel with its real tag condition before the machine runs on it.

Questions asked

What does the double-click on the icon actually do?

It registers as a selection on the tree item and can expand a collapsed branch, which is why the project keeps responding normally everywhere else. The click is not dead, it simply never carries the launch command, so the editor gives you no error to chase.

Other programs launch from the icon or the text. Why treat this tree differently?

Hit targets are set per application. Many CAD packages and file explorers treat the icon and the label as one launch region; this Navigation window binds the double-click command to the label region only. There is no fault state to clear, so retrain the aim or use the menu path.

Do the tree path and the menu path edit the same alarm data?

Yes, both open the same Alarm Control Setup dialog over the same project database. If the two ever show different content, a second dialog instance is open. Close the project and reopen it before editing, so a stale window cannot overwrite your changes.

What should I record before escalating a C-more Micro editor issue?

The software version, panel model, PLC protocol driver, screen orientation, host operating system with bit depth, and whether the function ever worked on that machine. A missing one of these is the usual reason a support case stalls, and together they take about a minute to capture.

Keep reading

  • How-to

    Why C-more Micro Preview Screens Show Out of Order

    Preview thumbnails in C-more Micro follow the project's stored Screen Library list order, not the screen number, and Preview has no sort function. Fix the sequence by dragging entries in the Screen Library; never renumber screens, because every screen-change reference stores the number.

    HMI and touchscreens

  • Troubleshooting

    HMI Function Key Does the Wrong Action: Find the Hidden Object

    When an HMI function key performs an action you never assigned, the assignment exists in the project. On the affected screen, ungroup the visible artwork, move the static bitmap aside and inspect the concealed pushbutton: it carries its own function-key number and screen-change action. The simulator is reproducing the project faithfully; remove or reassign the hidden object, then put navigation on the function bar on a non-touch panel.

    HMI and touchscreens

  • Troubleshooting

    Fixing a Vijeo Designer Runtime Installer Target-Not-Found Error

    When ping succeeds and a standalone runtime install completes but the application download fails at the runtime-installation stage, the fault is the launch path: close the Vijeo Designer session started through SoMachine and launch Vijeo Designer directly, then download over the same Ethernet connection. That single change fixed the reported XBTGT6330 installation. Treat the USB flash-full message as a separate storage branch.

    HMI and touchscreens