XProfan

English

Jau, as UserMessage declared Messages go gestackt, only the Stapelabbau ought to still not wrong around happen.

(even if the with Stacks sooner normally is, but with Messages zerstörerisch)
Compile Mark Separation

cls
userMessages 12345

whileLoop 23

    sendMessage(%hWnd,12345,&loop,0)

wend

var myMsg&=0

while 1

    waitInput
    myMsg&=%uMessage
    case myMsg& : print &uwParam

wend

end

power P2C the too so?

Dokument1.exe	311 kB

Hochgeladen:	04/28/09

Downloadcounter:
		Download

04/28/09 ▲

Vollständiges Quote

Absatzweise Quote Zeilenweise Quote

RGH

I have it rasch time tested: Profan2Cpp power it in the doing differently around.

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

04/28/09 ▲

Vollständiges Quote

Absatzweise Quote Zeilenweise Quote

The Sebastian skin me always on The fingers if I CPP write instead of Cpp.

Yes, in the korrekten Order is here well unabdingbar because not reparabel or somehow by Workaround kompensierbar.

04/28/09 ▲

Vollständiges Quote

Absatzweise Quote Zeilenweise Quote

RGH

iF, Beitrag=52095, Zeitpunkt=28.04.2009

The Sebastian skin me always on The fingers if I CPP write instead of Cpp.

then ought to I it time rasch correct ...

iF, Beitrag=52095, Zeitpunkt=28.04.2009

Yes, in the korrekten Order is here well unabdingbar because not reparabel or somehow by Workaround kompensierbar.

Hm, I coming bislang too with the stack-usual Order zurecht. I can it naturally Change. One small Dreh on the UMessage-Objekt and the thing is for XProfan 12 geritzt.

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

04/28/09 ▲

Vollständiges Quote

Absatzweise Quote Zeilenweise Quote

thanks Roland, juhu!

Perhaps could You so the Müllspiel once kompilieren and the Runtime ääää The Exe post. ^^

04/28/09 ▲

Vollständiges Quote

Absatzweise Quote Zeilenweise Quote