XProfan

English

Jörg
Sellmeyer

After my understanding should %umessage to the Reading reset go, so it meaningfully used go can.
at least with %umessage = 16 is the but not the case. self one delete the Message with User Messages -16 bring nothing, because %umessage furthermore the value 16 keeps.

Compile Mark Separation

User Messages 16
Cls

While 1

    WaitInput
    Print %umessage
    Case %mousepressed = 2:End
    User Messages -16
    SetTimer 1
    WaitInput
    KillTimer
    Print %umessage,"Hier should still at the latest 0 auftauchen"
    User Messages 16

Wend

Windows XP SP2 XProfan X4
... und hier mal was ganz anderes als Profan ...

08/18/08 ▲

Vollständiges Quote

Absatzweise Quote Zeilenweise Quote

Dieter
Zornow

the was always so and is a Manko the User Messages, but there's a Possibility tappt im dunkeln back zusetzen.

User Messages 16,5,$0044

and to the request the following Message Send, is a obsolete Windowsmessage

Sendmessage(%Hwnd,$0044,0,0)

with 16 is But Yes not so bad, but with 5, the window hears not any more on To flackern, therefore The Message Send and its lane.

Er ist ein Mann wie ein Baum. Sie nennen ihn Bonsai., Win 7 32 bit und Win 7 64 bit, mit XProfan X2

08/18/08 ▲

Vollständiges Quote

Absatzweise Quote Zeilenweise Quote

Jörg
Sellmeyer

thanks, the helps first moreover.

Windows XP SP2 XProfan X4
... und hier mal was ganz anderes als Profan ...

08/18/08 ▲

Vollständiges Quote

Absatzweise Quote Zeilenweise Quote

Jörg
Sellmeyer

Tja, How one hierdran sees, functions too not

Compile Mark Separation

Window Style 2 + 8 + 16 + 32 + 512
User Messages 16,$0044
Cls

While 1

    WaitInput
    Print %umessage
    Case %mousepressed = 2:End
    Case %umessage = 16:SendMessage(%hwnd,$0044,0,0)
    print %umessage
    Case %umessage = 16:Break

Wend

waitinput

Windows XP SP2 XProfan X4
... und hier mal was ganz anderes als Profan ...

08/18/08 ▲

Vollständiges Quote

Absatzweise Quote Zeilenweise Quote

Jörg
Sellmeyer

Edit: After something rumprobieren have I now edoch a Solution found (from the I really thought, I had tappt im dunkeln before already tested).

i want soetwas make - quasi the Closing-Cross as Stop-Button "misbrauchen". of my opinion to ought to the possible his:

Compile Mark Separation

Window Style 2 + 8 + 16 + 32 + 512
User Messages 16,$0044
Cls
neu################

Proc KillUMEssage

    SetTimer 1
    WaitInput
    KillTimer
    SendMessage(%hwnd,$0044,0,0)

ENDPROC

######################

Proc Test

    WhileLoop 10000

        Locate 1,1
        Print "Test " + Str $(&Loop)

        If %umessage = 16

            SendMessage(%hwnd,$0044,0,0)
            Break

        EndIf

    Wend

ENDPROC

While 1

    WaitInput
    Print %umessage,%key
    Case %mousepressed = 2:End

    If %umessage = 16

        new############
        KillUMEssage
        ###############
        Break

    ElseIf ScanKey(65) Button a

        Test

    EndIf

Wend

 $B "Ende?"

Windows XP SP2 XProfan X4
... und hier mal was ganz anderes als Profan ...

08/18/08 ▲

Vollständiges Quote

Absatzweise Quote Zeilenweise Quote

somewhere I had Schonmal

Compile Mark Separation

setTimer 10

while uMessage { waitInput }

killTimer

posted - but since missing imho yet something, be strain without computer on the I testing could...

08/19/08 ▲

Vollständiges Quote

Absatzweise Quote Zeilenweise Quote

Jörg
Sellmeyer

Yes - had so did i already so probiert (s.o.). first the hint of Dieter hats brought.

Windows XP SP2 XProfan X4
... und hier mal was ganz anderes als Profan ...

08/19/08 ▲

Vollständiges Quote

Absatzweise Quote Zeilenweise Quote

RGH

The Systemvariable %UMessage becomes in the didn't at Reading on 0 reset, separate at entering in that WaitInput.

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

08/19/08 ▲

Vollständiges Quote

Absatzweise Quote Zeilenweise Quote

Jörg
Sellmeyer

but then should in the first example still %umessage again 0 his, there Yes another WaitInput in the Loop is. With the User Messages -16 can too rauslassen, it bewirkt namely nothing.

Windows XP SP2 XProfan X4
... und hier mal was ganz anderes als Profan ...

08/19/08 ▲

Vollständiges Quote

Absatzweise Quote Zeilenweise Quote

RGH

separate at entering in that WaitInput

I faith this is not the case, I faith a uMessage becomes only überschrieben if a new eintrifft. (can it here ldr. not testing, my but me so therefore already herumgeprügelt having To must.)

08/19/08 ▲

Vollständiges Quote

Absatzweise Quote Zeilenweise Quote

Jörg
Sellmeyer

Sach I Yes!

Windows XP SP2 XProfan X4
... und hier mal was ganz anderes als Profan ...

08/19/08 ▲

Vollständiges Quote

Absatzweise Quote Zeilenweise Quote

Juhu XProfan becomes always rather - or. to each found "Fehler" too The programs stabiler.