Click Action

Thomi

Hello team and community,

After a lot of testing on Mirabox N4 Pro, I’ve discovered a major limitation in how the software handles plugins.

The core issue is:Whenever you assign ANY plugin to an LCD key, that key completely loses its primary function - it stops registering physical clicks.

It doesn’t matter if it's a hardware monitor (CPU/RAM), a media widget, or any other plugin. No "Click Action".

Why this is a huge problem:A stream dock is supposed to be an interactive controller. If I put a plugin on a screen, I should still be able to click it to trigger an action (e.g., click a CPU graph to open Task Manager, click a weather widget to open a browser, etc.). Right now, plugins turn these expensive LCD keys into passive, unclickable mini-displays.

I have searched through the entire documentation and found nothing about this limitation.

Is there a hidden setting or a specific way to force a Click Action (like launching an .exe) on top of any active plugin?

Please look into this, as it severely limits the potential of the N4 Pro hardware.

Thank you.

dockkey2023

When we write plugins, sometimes they are only used to display relevant parameters. If you have development experience, you can refer to our development documentation and write the relevant plugins yourself。
  https://creator.key123.vip/en/

Thomi

First of all, thank you for developing this software and providing the JavaScript SDK. It gives the community great flexibility! However, we believe that adding a few quality-of-life features directly into the native interface would make the user experience much smoother:
  Native Window Focusing: When using media plugins, it would be amazing to have an option to bring the player window to the foreground on press. Right now, users have to manually modify the plugin code using Node.js to achieve this. A simple built-in checkbox like "Bring app to foreground" would be a wonderful addition.
Universal Click Triggers: It would be extremely helpful to be able to assign separate actions for Single Click and Double Click, regardless of which plugin is currently on the button. For example: a single click triggers the plugin's default function, while a double click triggers a system command or opens the app.
Without these native features, advanced users might feel compelled to switch to alternative ecosystems like Bitfocus Companion just to avoid manual coding for basic tasks. We really want to see the native Mirabox software thrive and grow.

dockkey2023

Thomi 发表于 2026-6-26 19:34
First of all, thank you for developing this software and providing the JavaScript SDK. It gives the  ...

First of all, thank you very much for your suggestion. We have already sent it to our project manager.

Heart

Thomi 发表于 2026-6-26 19:34
First of all, thank you for developing this software and providing the JavaScript SDK. It gives the  ...

Thank you for your suggestion. This is indeed a pain point, and we will work to implement it.

In the future, we may add a single-click/double-click action to the Action Flow.

Drag this feature onto a button to configure two actions: one triggered by a single click and the other by a double click.

Furthermore, you can set which action's icon to display, potentially offering three modes: always displaying the icon for action1, always displaying the icon for action2, and switching between the icons for action1 and action2 based on the button event (single click displays action1, double click displays action2).

I believe this feature should perfectly meet your requirements.