.
>
> Because they use different messages, I think.
Yes, I think he looks at the type of control (listbox, combo, etc) of
the target window and determines what message to send based on that.
>
> I presumed I could achieve them by using Win.SendMessage(), with
> getvaraddr if needed, or Win.SendMessageStr(). However, sometimes it
> hangs PP, so I had to kill the target process via task manager, e.g.,
>
> local sText
> Win.SendMessageStr(hWnd, SB_GETTEXT, n, sText)
>
> It seems to need a special care, maybe due to a security reason?
How long is the target string and how big is sText. sText can hold up
to about 270 chars nless you take special care by first allocating
sText with
sText=repeat(" ", buffersize)
There is also the issue of moving data across process boundaries but I
think Window takes care of that internally. At least it does for
Gettext and I hope it does for the others; otherwise, this is a lot
more complicated to implement.
Attention: PowerPro's Web site has moved: http://www.ppro.org
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/power-pro/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
