PowerPro 5.3.35r (no unicode) and 5.3.37h (Unicode)

I've uploaded these updates to the PowerPro Installation File folder in Yahoo files.
 Version 5.3.37h/.35r (Aug 2017) 
 Eliminated  PowerPro aborts after reconfigure (in my stress tests) Fixed issue with positioning exec calccalendar on multi-monitor system PowerPro more responsive when other programs using high cpu. On Advanced setup, Limits tab, set "Time to wait before aborting call for icon/text" to small value like 2 or 1. Also gray check "Use Timer for Active Bars" on Command list setup, All Bars tab. Added toutf8 and toansi string functions. Mixing Unicode UTF8 and ANSI in 5.3.37hPowerPro uses UTF8 internally to represent Unicode. Under UTF8, the bytes with value >= 128 are used for encoding Unicode in a way that is incompatible with the ANSI coding for these values. So if you want to use ANSI characters >=128 in with Unicode support you have to take special steps. The general approach is as follows: If there are existing UTF8 strings to be used, convert them to ANSI using toansi function. Execute exec.unicode(0) to turn off unicode support. With Unicode support off, PowerPro and plugins will treat strings as ANSI, not UTF8. Perform desired operations on the ANSI strings and files. Turn Unicode support back on with exec.Unicode(1). Convert any required ANSI strings to UTF8 using toutf8 function.For example: // Goal is to write Unicode string str in ANSI format stransi = str.toansi exec.unicode(0) file.writeall( "c:/the/path/filename.txt", stransi,) exec.unicode(1) If you find a plugin does not perform as expected with Unicode support off, you can instead use the corresponding plugin from the non-Unicode version of PowerPro. Install that version in a separate exe folder, rename the plugin, eg file.dll to fileansi.dll, then copy to plugin folder of Unicode version of Powerpro. Use fileansi as plugin name, eg filenansi.writeall.
 

 Assigning value to variables, testing contents of variables using same encoding for equality, and the toansi/toutf8 functions will work regardless of whether Unicode support is on or off.   For other operations you have to ensure that exec.Unicode is set correctly for the type of string you want to process. 
 

 Exec Unicode does not refresh bars. If you want to make sure that any text on bars is redisplayed in correct format, then use exec.Unicode(0, 1) or exec.Unicode(1,1)