Welcome to the SQLitening support forums!
Started by Bern Ertl, March 22, 2009, 03:52:41 PM
FUNCTION MyslSel( BYVAL sSelect AS STRING) AS LONG LOCAL lSetNum AS LONG 'Begin critical section (gCriticalSection is GLOBAL and initialized in PBMAIN) EnterCriticalSection gCriticalSection 'Call SQLitening lSetNum = slGetUnusedSetNumber slSel sSelect, lSetNum 'End critical section LeaveCriticalsection gCriticalSection 'Return set number FUNCTION = lSetNumEND FUNCTION
Quote from: Fred Meier on April 09, 2009, 09:55:58 AMSQLitening.Dll is not thread-safe so if you have a true multi tasking situation then it would be necessary to wrap the slGetUnusedSetNumber + slSel calls inside a critical section to ensure than the set number is properly used.
Quote from: Fred Meier on April 09, 2009, 09:55:58 AMCan't find any reference to a WM_INITIALIZE message -- do you mean WM_INITDIALOG?I'm not aware that the init messages cause multi tasking concerns.
QuoteWould it be feasible to add a modchar option to slSel to automatically use the next availble set number and return that set number (or to add a new function to effectively combine slGetUnusedSetNumber and slSel and return the set number)?
Quote from: Fred Meier on September 18, 2012, 10:10:18 PM... each thread has it's own array of set numbers so all threads can safely use the same set number ...
QuoteDo you already know when this is available?