--- In [email protected], "forxtra" <forx...@...> wrote: > > I've been running 4.9d6 (Modified: 2009-03-16, 13:57:31) > > I don't know it's timely to post this kind of issues, but there're other > dbcs-related issues. > > > (1) InputDialog() with Autocompletion using the strings in the vector > ; ------------------------------------------- > Local mystrings[4;1] > > mystrings[0] = "var0" > mystrings[1] = "var1 __dbcs__" > mystrings[2] = "var2" > mystrings[3] = "var3 __dbcs__" > > InputDefault("default", "title", "=mystrings") > ; ------------------------------------------- > > If an element of the vector contains dbcs chars, some unexpected chars are > occasionally added at the end of corresponding item([1]/[3]) in the > dropdownlist of combobox. > > > > (2) Output of Existing Structures > ; ------------------------------------------- > Local str1 = Class.MakeStruct("var1 var2", "init1", "init2") > str1.var2 = "__dbcs__" ;; set var2 to DBCS char > > Local filepath = ScriptFolder ++ ?"\output.ini" > str1.write(filepath) ;; powerpro crashes > ; ------------------------------------------- > > When writing structure containg dbcs chars to ini-type files, > powerpro crashes.
FWIW I get similar results trying to use single byte high ascii values in your scriptlets where you have dbcs. e.g., copyright symbol © Don't know if these problem are somehow related to documented limitations on variable names (which can only have alphanumerics and underscores). Regards, Sheri
