--- In [email protected], "entropyreduction" <alancampbelllists+ya...@...> wrote: > > Thinking out possibilites: > > vars plugin uses pprofolder. > > When you're in Korean, does pprofolder come through okay, without any > gibberish characters, in debug window? How about validpath(pprofolder)? > > Have you uses the ini plugin? If so, does it work okay? > If you haven;t tried it, can you use it to read a key in > pprofolder ++ "plugins.ini"? > > If not, can you read a key from "C:\plugins.ini", first copying > plugins.ini to root of C:\ (or somewhere else easy to get at)?
As shown png below, my pprofolder is "d:\Program Files\DeskTop\PowerPro\" It consists of only alphabetic characters and space, and validpath(pprofolder) returns 1. I've been using the ini plugin v1.54. ; ------------------------ Ini.Get(PProFolder ++ "plugins.ini", "varsConfig", "varsBackupLocation") ; ------------------------ ini.get() successfully returns "scripts/data/allProcs.ini", and ini_status contains "OK" please see also - http://img15.imageshack.us/img15/8192/varsv084just2keys.png Message #34836 > > > - Unicode.InputDialog() > > Okay, I'll check that out. What's it do in your Korean environment? > If I run a sample script named encodeUnicode.powerpro, powerpro always crashes before the dialog box appears. ; ------------------------ local uResult local bRes = unicode.inputdialog("uResult=Enter the unicode string you want to encode:", "Encoder For Unicode Strings") ; ------------------------ So, when I need to use a uncode.encode(), I'm using encodeUnicode.exe included in the unicodePlugin0.30beta050712.zip > > > - Com.Unload > > What's it do wrong? > I'm aware that a similar issue was mentioned before by Sean. - http://tech.groups.yahoo.com/group/power-pro/messages/29940?threaded=1&m=e&var=1&tidx=1 If I excute a com.unload, powerpro crashes. If I comment out a com.unload, powerpro does not exit cleanly and powerpro.exe still remains in the Task Manager. So, there might be two (or more) instances of powerpo.exe, unless click the "End Process" button in the Task Manager. Thanks. > > --- In [email protected], "forxtra" <forxtra@> wrote: > > > > --- In [email protected], "entropyreduction" > > <alancampbelllists+yahoo@> wrote: > > > > > > I tried on my system with a vars.ini, with just > > > > > > [varsConfig] > > > varsBackupLocation=scripts/data/allProcs.ini > > > varsBackupGlobalsLocation=scripts/data/allProcs.ini > > > > > > And nothing else. > > > > > > Then a > > > > > > local i = 34 > > > vars.save_var("i") > > > > > > works fine after a vars.unload. > > > > > > Could you duplicate that exactly? Just the two keys in vars.ini file, > > > unload, run script? Ta. > > > > > > It seems to appear the same problem with just the two keys in vars.ini file. > > - http://img15.imageshack.us/img15/8192/varsv084just2keys.png > > > > > > I guess that if I use a vars.ini, vars.dll could not find "vars.ini" > > properly. > > so, the vars plugin initially just use the compiled-in, default values to > > configure itself. > > > > > > Although I'm not sure it's one of the reasons, I'm running a non-English > > version of WinXP(Korean / codepage 949 / dbcs). > > and unfortunately, there are some limitations that I could not use in my > > environment. > > e.g., > > - Unicode.InputDialog() > > - Com.Unload > > > > I monitored with FileMon v7.04 to see what happens when calling to > > vars.save_var() without any ini file. > > (FileMon v7.04: > > http://technet.microsoft.com/en-us/sysinternals/bb896642.aspx) > > > > ; ---------------------------- > > File.Delete("vars.ini") > > File.Delete("plugins.ini") > > Vars.Unload > > > > Local i = 34 > > MessageBox("TopMost", "", "Start Capture") > > Vars.Save_Var("i") > > MessageBox("TopMost", "", "Stop Capture") > > ; ---------------------------- > > > > Result: http://img15.imageshack.us/img15/4666/varsv084wihfilemon.png > > vars.dll did not attempt to find "vars.ini" and failed to read "plugins.ini" > > > > > > I also tried it under English WinXP with East Asian language package on > > Microsoft Virtual PC. > > > > Under the Default Regional and Language Options, it's working properly > > regardless of the name of ini file. > > > > However, if I change to Korean from English (United States), I could > > encounter the same problem. > > (Control Panel > Regional and Language Options > Advanced > Language for > > non-Unicode programs)
