The new implementation in 6.30 may be that custom pidcodes being unregistered are not accepted anymore.
So again content of my first post in this thread remains valid... nothing has changed in plugin interface.
TrueData plugin might just be poorly written if it is not recognized with correct runtime version and correct bitness.
Need to start collaborating with Amibroker and adjust to the changes required therein.
From ADK docs :
It is EXTREMELY IMPORTANT to use PLUGIN_ID to uniquely identifies your data source. AmiBroker
uses the plugin ID to distinguish between data sources. For testing purposes you may use PIDCODE( 'T', 'E',
'S', 'T'), but for release to the public you should contact us at [email protected] to receive unique plugin identifier for your data plugin. Already reserved plugin IDs are: QTRK, MSTK, eSIG, myTK, TC2K,
FTRK, CSI, QCOM, DTNI.
Right after than you should add (if it does not already exist) the following line:
// IMPORTANT: Define plugin type !!!
#define THIS_PLUGIN_TYPE PLUGIN_TYPE_DATA
This defines that the plugin you are writing is data plugin.
uses the plugin ID to distinguish between data sources. For testing purposes you may use PIDCODE( 'T', 'E',
'S', 'T'), but for release to the public you should contact us at [email protected] to receive unique plugin identifier for your data plugin. Already reserved plugin IDs are: QTRK, MSTK, eSIG, myTK, TC2K,
FTRK, CSI, QCOM, DTNI.
Right after than you should add (if it does not already exist) the following line:
// IMPORTANT: Define plugin type !!!
#define THIS_PLUGIN_TYPE PLUGIN_TYPE_DATA
This defines that the plugin you are writing is data plugin.