> If you are really using wm_gettext, that could be an issue as the system
> automatically handles unicode/normal translations in some circumstances which
> would conflict with the code now in win.dll. Try the normal sendmessagestr
> for wm_gettext. I can also hard code a check to avoid unicode in that case
> for sendmessageremotestr.
>
> I tested the new one on two XP machines with pproconf (not unicode), notepad,
> and explorer, (both unicode) and it works for me. This is the script I
> tested; I attached it to a hot key and put the mouse over the file dialog.
>
> local han = win.handle("under")
> if( win.match(han,"filedialog") == 1 || win.match(han,"c=bosa_sdm*") ==1 )do
>
> local myString = repeat("A",1025)
> local len = win.SendMessageStrRemote(han,0x0400+102,1000,myString)
> win.debug(len, "<"++myString++">")
>
> endif
>
This is probably a message similar to WM_GETTEXT as after some test i can
suspect that the second param is the buffer length and returned value the
length of the string like WM_GETTEXT expect that it is not the same message
number (0x0466 vs 0x000D )
Using the binary block as intermediate i can detect if the output is unicode or
not using the string length and the position of the first \x00... after i
decide if i convert to unicode or just dump the binary block at length.
IT is working now and almost finished.. the idea is to have an additional
script that allow dynamic regex search on file or folder or some favorite as
side menu of file dialog.
When it will works properly and after code cleaning/polishing i will share it.
