AESDK Development UI Message response

UI creation:

Under the entrance

 Case Pf_cmd_params_setup:     // .... break;

You must specify the number of UI at the end, the number of UI is generally enumerated, and an error if the enumeration length is inconsistent. So it's best to modify the enumeration directly

3;

UI Action Response:

Entrance:

 Case Pf_cmd_user_changed_param:             = Userchangedparam (in_data,                out_data,                params,                reinterpret_cast<  Const Pf_userchangedparamextra *>(extra));             break;

The index of the UI gets here, and the index starts at 1.

Which_hitp->param_index

In short, compared to the original comparison of egg pain.

AESDK Development UI Message response