| |
|
|
Nico Madysa | Hello Roland,
The XProfan-Help behauptet, The functions GetActiveWindow and SetActiveWindow seien solely Wrapper around the gleichnamigen windows-API-functions.
Own Experience make me but believe, that it itself here sooner around the functions GetForegroundWindow or. SetForegroundWindow deals.
The Difference is, that *ActiveWindow itself always on the own Process relating (and 0 zurückgibt, if another Process just the Fokus has), during *ForegroundWindow always the lever the straight active Fensters zurückgibt, even if it another Process heard.
the following Program, tested in the XProfan-X2.1a-Interpreter under windows 7 shows, that XProfans GetActiveWindow always the same Result has as windows-API GetForegroundWindow . CompileMarkSeparation
|
|
|
| |
|
|
|
RGH | Hi, you have naturally completely right. The Info on The gleichnamige API-function stammt yet from the 16-bit-Ära of XProfan (and was moreover not of me into Help eingefügt). there gift it yet no unterschiedlichen processes. under 32 bit were The functions then suddenly only yet on the own Process dull, what Yes not senses the Erfinders was. finally get tappt im dunkeln then to communication with others Programs introduced. therefore had I The API-Aufrufe properly Change, so The effect again How ehedem with 16 bit was. The Info in the Help is means wrong. (i'll it to remove.)
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 | 03/08/14 ▲ |
|
|
|
|
Nico Madysa | thanks for speedy response! |
|
|
| |
|
|