XProfan

The WindowProc the not-To-minimierenden Fensters must imho on wm_minimize only NULL give back and not on The defWindowProc weiterleiten. i'm I do not integrally sure whether XProfan11 this of House from can becomes, be there but guter items.

You can whom entry minimize too from the System Menu Remove, gwl_setStyle helps here Perhaps.

Christian
Schneider

Hmm, Remove wished I the Button ungern,there it Yes possible his should the window To minimize. from kosmetischen Found I will though to the Minimierung one other Window Remove.

XProfan 11| Vista(64) SP2

the can You How said in the wProc manage.

Frank
Abbing

Have momentarily little Time to that testing, therefore the question on Roland. can The Messages in the Subclassing aborted or umgebogen go? unless, is the still vorgesehen?

Since I it unfortunately not yet tested have can I only requests/hoping the the return the SubClassProc in the drop NULL too really NULL is. (I faith Roland has not yet berücksichtigt the one here herumbiegen would like...)

in the principle could so setUAnswer wegfallen! (If Rolands SubClassProc hopefully too gestackt operates - what unfortunately absolutely necessary would for korrektes works)

RGH

Frank Abbing

Have momentarily little Time to that testing, therefore the question on Roland. can The Messages in the Subclassing aborted or umgebogen go? unless, is the still vorgesehen?

what understand You under a Messsage Cancel or a Message umbiegen?

You entscheidest, whether The Message as machine counts (because You tappt im dunkeln by SubClassMessage() query), or as not machine (in the You tappt im dunkeln with the bislang usual functions under Use the System-Variables &Wnd and %sMessaage query.
in the 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.
I meant but, the at example erwähnt to have.

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

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:
Compile Mark Separation

ElseIf SubClassMessage(%hWnd, ~wm_activate)

return 0pre>

might the hWnd still not aktivierbar his, correctly?

we means withal return 0 to original wndproc weitergeleitet?

RGH

short ask to, if I in the Minibrowser these 2 Lines hinzufüge:
Compile Mark Separation

ElseIf SubClassMessage(%hWnd, ~wm_activate)

return 0pre>

might 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

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)