XProfan

- Page 2 -

Dürfte the same trouble his.

Nico
Madysa

Suppi, means is that here the/The/the Walk-Around:
Compile Mark Separation

 $H windows.ph
 $H messages.ph

Proc XAddWindow

    Parameters C1$
    declare IPar1%, C2$
    C2$ = Space$(32767)
    IPar1% = ~GetWindow(~GetDesktopWindow(), ~GW_Child)
    IPar1% = ~GetWindow(IPar1%, ~GW_HWndFirst)
    SendMessage(IPar1%, ~wm_GetText, 32767, Addr(C2$))

    While (Left$(C2$, Len(C1$)) <> C1$) And (IPar1% <> 0)

        IPar1% = ~GetWindow(IPar1%, ~GW_HWndNext)
        SendMessage(IPar1%, ~wm_GetText, 32767, Addr(C2$))
        AddString C2$

    EndWhile

ENDPROC

or?

Nico Madysa

- Page 3 -

Hello Nico...

Nö, I faith not. The problem might with SendMessage(IPar1%, ~wm_GetText, 32767, Addr(C2$)) lying.

over again.. be there no expert, have but in the moment subesquent local:
some Window, u.a. unsichtbare and unlistbare Systemfenster XP (and well too under ME) process The Message WM_GETTEXT not correctly.. sends is a Message through Sendmessage, wait the program on a response from the WNDProc the angesprochenen Fensters. comes these not, wait @Sendmessage forever -> Program crashes. Verwedet one SendMessageTimeOut wait these API a gewisse Time and fractures then whom process ex => the should then weg and loudly my Tests XP does it too.

Greeting

Andreas

...The Window The I there XP my, are The Window with the lever directly over %Desktop. These Windows of Process CSRSS.EXE created, and of course of same Thread, the too %Desktop created.
The cover the a Fensters is Message, The . Develop are Kindfenster this Fensters.
As I said, there shining something with SendMessage schiefzulaufen, what against with SendMessageTimeOut functions - and there lying well too the Completed: FindWindow and AddWindows under ME - kanns unfortunately not testing, there me ME missing.

Therefore ought to Roland within of his FindWindow / addwindows rather SendMessageTimeOut use...!?

time try, whether the rather goes my I. by me works.

RGH

Therefore ought to Roland within of his FindWindow / addwindows rather SendMessageTimeOut use...!?

the would in the doing a Maßname for future XProfan-versions!

Greeting
Roland

Intel Duo E8400 3,0 GHz / 4 GB RAM / 1000 GB HDD - ATI Radeon HD 4770 512 MB - Windows 7 Home Premium 32Bit - XProfan X4

Sebastian
Sprenger

I personally find GetWindowText but sinnvoller as SendMessageTimeout.
GetWindowText has under windows ME always correctly. functions, too with Windows, The loudly Taskmanager none reacted having.
SendMessageTimeout with WM_GETTEXT has with reagierenden Windows of course functions, but with whom Nichtreagierenden should one still well sooner longer Waiting and bekäme evtl. not time one zuverlässiges Result... or übersehe I here what?
Greeting, Sebastian

Profan² 7.0e, XProfan 9, 11.2a, FreeProfan32

Windows Vista Home Premium 32-Bit, 2.8 Ghz, 4 GB RAM

Windows Me, 1.8 Ghz, 256 MB RAM

Hello Sebastian

No, correctly.. For this has GetWindowText others detriments. therefore

time try, whether the rather goes my I

- the GetWindowText always correctly. functions (in reference on Abstürze), can I confirm. GetWindowText supply but with manchen Windows no Result, though one Fenstertext present is.

unfortunately have I no ME and come too only sporadisch at times XP ran, can therefore this Error not complete understand and not testing, what there rather works.

Greeting

Andreas

Oha: GetWindowText cannot retrieve the Text of a control in another application [...]

...sends means too nurn SendMessage

and the here's neither badly: [...]

Erklärend? [...]

on edit control.

what To GetWindowText yet important would:

If the target window is owned by the current process, GetWindowText causes a WM_GETTEXT message to be sent to the specified window or control. If the target window is owned by another process and has a caption, GetWindowText retrieves the window caption Text. If the window does hardship have a caption, the return value is a zero string. Diese behavior is by solid. It allows applications to call GetWindowText without becoming unresponsive if the process that owns the target window is hardship responding. However, if the target window is hardship responding and it belongs to the calling application, GetWindowText wants cause the calling application to become unresponsive.

and that here ought to one there too rethinking:

To retrieve the Text of a control in another process, send a WM_GETTEXT message directly instead of calling GetWindowText.

there's a great many types, a Message To Send. Why should any SendMessage Call?
InSendMessage
PostMessage
SendMessageCallback
SendMessageTimeout
...