ImageGear allows you to have different groups of settings for providing mechanisms for associating a thread with a particular group.

Declaration:

AT_ERRCOUNT ACCUAPI IG_thread_data_ID_associate(
        DWORD dwNewId,
        AT_BOOL bLeaveThreadStorage
);

Arguments:

Return Value:

Returns the number of ImageGear errors that occurred during this function call.

Supported Raster Image Formats:

This function does not process image pixels.

Example:

AT_ERRCOUNT nErrCount = 0;
nErrCount = IG_comm_comp_attach("ART");
. . .
AfxBeginThread( IGProcThread1, NULL );
AfxBeginThread( IGProcThread2 , NULL );
UINT IGProcThread1( LPVOID lpData )
{
        AT_ERRCOUNT nErrCnt;
        nErrCnt = IG_thread_data_ID_associate( 1, TRUE );
        nErrCnt = IG_load_file( "picture1.bmp", &hIGear);
        . . .
        return 0;
}
UINT IGProcThread2( LPVOID lpData )
{
        AT_ERRCOUNT nErrCnt;
        nErrCnt = IG_thread_data_ID_associate( 2, TRUE );
        nErrCnt = IG_load_file( "picture2.bmp", &hIGear);
        . . .
        return 0;
}:

Remarks:

By default, each thread uses the global copy. Such a mechanism allows you to have ImageGear settings ("groups" that are identified by specific IDs) that are customized for each thread. This API allows you to associate a thread with different ImageGear settings. Allocation of new settings will result in the use of that group's default values if it doesn't exist prior to the call. The old copy of the settings will be deleted unless it's (a) a global copy used by other threads, or (b) bLeaveThreadStorage is TRUE.

The global group of ART settings cannot be used in multi-threaded application. You have to use this function to associate a new local group of settings for each new thread.

The access to the same PDF document from multiple threads is not permitted because the multiple threads cannot share Adobe PDF Library data types. PDF doc created/opened in the main thread can be only used from the main thread.