Subj : Using Prf* routines in wi
To   : MIKE RUSKAI
From : Vitus Jensen
Date : Mon Jun 19 2000 07:05 pm

Moin MIKE,

17.06.00 19:22, MIKE RUSKAI wrote a message to VITUS JENSEN:

 MR> Some senseless babbling from Vitus Jensen to Coridon Henshaw
 MR> on 06-08-00  00:43 about Using Prf* routines in wi...

 MR> [snip]

 VJ>> But even if the user selected a network drive it would hang the
 VJ>> PM if the network fails and my program uses
 VJ>> PrfWriteProfileData() from WM_MOVE. 

 MR> In my book, any function which can potentially block for an
 MR> indefinite amount of time belongs in a second thread.

So is my coding style.  I just wanted to confirm that PrfRead/Write do access 
the file (and block).  This isn't obviously given the Prf* docu and looking at 
the strategy used by WPS to rewrite os2.ini.
I take it that you think about Prf* as /blocking/?

 MR> So, instead of calling the Prf*() functions from your window
 MR> procedure, create a wrapper for all the functions you need, which
 MR> call the API's on a second thread (I recommend a wrapper simply
 MR> to avoid clutter in the window procedure).

The design is up to me but using a second thread is a possibility.

Bye,
    Vitus

--- Sqed/rexx 436:
 * Origin: Remember, Speed kills! Try Windows to relax (2:2474/424.1)

.