--- In [email protected], "nospam0123456us" <nospam012345...@...> wrote:
>
> --- In [email protected], "brucexs" <bswitzer@> wrote:
> >
> >
> > http://powerpro.webeddie.com/download/win.dll
> >
>
> it is worse than before (win 1.6.8)
> --CODE--
> len = han.sendMessageStrRemote( SB_GETTEXT, 1000, astr)
> win.debug("["++ len ++"] "++astr)
> --CODE--
>
>
> I did not get the string back for unicode (notepad++ unicode applicaton), i
> did not get the string back for an ansi application (pfe or notepad++ ansi):((
>
> Unicode OUTPUT :
> [26]C
>
> ANSI Debug OUTPUT
> [26]?
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
