| |
| |
|
| - Page 1 - |
|
Christian
Schneider | Hi,
there irgendeine Possibility The Minimierung the Mainwindow (by System Menu) abzufangen and the whole self into hand To take (so How with close by User Messages 16)? |
|
| |
| |
| |
|
|
| |
| |
| - Page 1 - |
|
 | RGH
m erstgenannten drop we The Original Fensterprozedur not any more called and the ggf. with Return angegebene worth becomes the Aufrufer zurückgeliefert. in the second drop becomes subsequently The ursprüngliche Fensterprozedur called.
Jau!   |
|
| |
| |
| |
|
|
Frank
Abbing | just as meant I it...  |
|
| |
| |
| |
|
|
| short ask to, if I in the Minibrowser these 2 Lines hinzufüge:
CompileMarkSeparation
might the hWnd still not aktivierbar his, correctly?
we means withal return 0 to original wndproc weitergeleitet? |
|
| |
| |
| |
|
|
RGH | iF
short ask to, if I in the Minibrowser these 2 Lines hinzufüge: CompileMarkSeparationmight the hWnd still not aktivierbar his, correctly?
the return 0 You do not need once. by the SubClassMessage() have You The Message treats and the ursprüngliche Fensterprozedur becomes none More called. in the example, I in the Thread about Subclassing posted have, comes ~wm_close indeed not any more on.
BTW: Why in the Minibrowser? Verwechselst You The Examples?
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 | 01/22/08 ▲ |
|
| |
|
|
| I faith I verwechsle The Examples, correctly!
but What is with my question? the hWnd is nevertheless aktivierbar what imho not correctly is. (I hope I verwechsle now not too yet The Message) |
|
| |
| |
| |
|
| |
| |
| - Page 2 - |
|
|
RGH | I see: so How I the understand, divides these essage the Window only with, DASS it activate (or. deaktiviert, according to WPARAM) watts and of course exakt after this happen is. The Message veranlaßt not the enable or Deaktivieren. moreover is the API activateWindow zuständig ... if I me right entsinne. (I Have The API not complete in the head.)
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 | 01/22/08 ▲ |
|
| |
|
|
| Hm, there be I me strain not sure - I mean me To remind that I on this ways already the enable prevent could - too the Deaktivieren. i'll well within a dll the XProfan hwnd gesubclasst having. The GUI has the window obviously not activate or deaktiviert with Anwahl by mouse or keyboard. I hope I verwechsle The Message not!
unfortunately here (yet) no Tools to hand...
@Frank: can You strain time NEN InlineASM provide which the XProfan-hWnd subclasst and wm_activate abfängt?  |
|
| |
| |
| |
|
|
RGH | and circa to that Threadthema zurückzukommen:
it should The Message wm_syscommand quizzed go. In wParam is then, which Systemkommando abgesetz watts. The Verkleinerungsbutton has the value sc_minimize.
ACHTUNG: If to the as User Message declared or ex XProfan 11 in the Subclassing abfängt, must one hereon respect, on The others Systemkommandos correctly To react, otherwise can the window z.B. not any more without employment the Taskmanagers closed go.
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 | 01/22/08 ▲ |
|
| |
|
|
Frank
Abbing |
@Frank: can You strain time NEN InlineASM provide which the XProfan-hWnd subclasst and wm_activate abfängt?
Yes. but a Fensteraktivierung can itself with WM_ACTIVATE so not prevent. is only a Message, that activate watts? |
|
| |
| |
| |
|
|
Christian
Schneider | RGH
it should The Message wm_syscommand quizzed go. In wParam is then, which Systemkommando abgesetz watts. The Verkleinerungsbutton has the value sc_minimize.
thanks, so funktionierts.
if it time someone need ought to, here The values of &Wparam for...
close: 20
minimize: 8
The normal display (to Minimierung): 61728
old+F4: 61536 |
|
| |
| |
| |
|
|
Jac
de
Lad | Poste please times one Minimalbeispiel.  |
|
| |
| Profan² 2.6 bis XProfan 11.1+XPSE+XPIA+XPRR (und irgendwann XIDE)
Core2Duo E8500/T2250, 8192/1024 MB, Radeon HD4850/Radeon XPress 1250, Vista64/XP | 01/23/08 ▲ |
|
| |
|
|
| back to that Sub-Topic:
CompileMarkSeparationnowmactivateproc proc hWnd:DWORD, uMsg:DWORD, wParam:DWORD, lParam:DWORD
pushall
.if uMsg==WM_NCACTIVATE
popall
mov eax,0
ret
.endif
popall
invoke CallWindowProc,oldproc,hWnd,uMsg,wParam,lParam
ret
nowmactivateproc CompileMarkSeparation {$cleq}
Set(FastMode,1)
Def Cwp(5) !user32,CallWindowProcA
Declare Ex%,_owp&,Sb&
DEF CreateStatusBar(6) @control(msctls_statusbar32,@$(2),add(000256,$50800040-16),@%(3),@%(4),@%(5),@%(6),@%(1),100, %HInstance)
windowstyle 512+8
window 100,100 - 640,480
_owp&:=External(user32,SetWindowLongA,%Hwnd,-4, Procaddr(_wproc,4))
Whilenot Ex%
Waitinput
Endwhile
End
Proc _wproc
Parameters Wnd&, Msg&, Wparam&, Lparam&
If (Msg&==16)// close
Ex%:=1
Elseif (Msg& == WM_NCACTIVATE)
return 0
endif
Return Cwp(_owp&,Wnd&, Msg&, Wparam&, Lparam&)
Endproc
unfortunately have I now here again strain not whom aktuellsten XProfan-Compiler to hand so I WM_NCACTIVATE not inside the SubClassProc testing can. might the someone try and here post?
CompileMarkSeparation
I mean me To remind it too allows to have the one Window not yet once reacted / into Vordergrund gotten becomes after one it anwählt - gleichwohl but any daraufliegenden Controls thoroughly empfangsfähig were. I empfand it as Manko not by windowStyle take on to.
its naturally correctly. that the intercepting the Minimierens so happen can:
CompileMarkSeparation
Since I How already erwähnt here strain no newest XProfan Compiler To hand have would so did i gladly know whether the MinMax-Geschenen with the SubClassProc To deal is. (faith the XProfan11 missing for another own Peek/Poke) |
 |
| |
| |
| |
|
(490)
Deutsch
English
Français
Español
Italia