ntel MCA 3.1 Default Handler

ntel MCA 3.1 Default Handler

Per the release notes update
The MCA Configuration Editor has been enhanced to make the default
handler configuration section easier to use. Default handler settings
are now divided into two groups. Global settings apply to the global
default handler. Application Specific Settings allow a much easier
method for adding applications and assigning custom settings for them.
In addition support for medApp button default handlers has been added.
Using executable files for default handlers is also easier to do. Simply
assign an executable instead of a DLL as the button handler.

How can someone reassign the button functionality like with previous versions of MCA (prior to 3.1)?
/Intel/HealthcareSDK/ToolTray/DefaultHandler/BarcodeDefaultHandler.dll/BC-LaunchApp =
/Intel/HealthcareSDK/ToolTray/DefaultHandler/BarcodeDefaultHandler.dll/BC-LaunchAppCmdLine =
/Intel/HealthcareSDK/ToolTray/DefaultHandler/CameraDefaultHandler.dll/CA-LaunchApp =
/Intel/HealthcareSDK/ToolTray/DefaultHandler/CameraDefaultHandler.dll/CA-LaunchAppCmdLine =

Is there support for this in MCA 3.1?


2 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Hi rman11,

You can use the steps below to reassign an executable instead of a DLL:

Step 1: Open CFGeditor, go to MCA Application Default Handler Configuration Global Settings and select the required device type to which executable need to be assigned (Barcode for example).

Step 2: Click on the edit box and browse button will be enabled to select DLL or executable, now browse and select the required binary that need to be launched.

Step 3: If needed, update the command line field and click on Apply button, now the button handler is ready to launch an executable for the required button.

See attachment for an example. Let me know if you have questions.



Downloadapplication/zip mca-example-131.zip550.76 KB

Leave a Comment

Please sign in to add a comment. Not a member? Join today