XProfan

- Page 1 -

RGH

so far sogut, becomes it because with %ChildMessage

possible his a Double click abzufragen?

unfortunately No, since the Listbox not Double click reacted and this always as two Klicks auffaßt and over these well the Elternfenster informed.

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

RGH

with %ChildMessage sees the above-mentioned Program so from:
Compile Mark Separation

WM_RBUTTONDOWN = $204
TEST: Rechtscklick auf Listbox
declare msg&,lb&
cls 0
lb&=create(ListBox,%hwnd,,100,10,100,100)

whileloop 10:addstring(lb&,):wend

    while 1

        waitinput
        case %ChildMessage = $204 : end

    endwhile

    end

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

Ah understand! On The menace there that I you with the Double click nerve (Hey Double-click on Listbox - kanns still not his! power eachone User - wants eachone Proggen...) can it his the this with the Perhaps sometime in XProfan erscheinenden ON( - Funktionalität abprüfbar is?

RGH

i'll me bemühen ....

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

Sebastian
König

Hello iF,

let itself one Double-click on a ListBox not simply therefore intercepting, that one WM_COMMAND as UserMessage angibt and on LBN_DBLCLK wait?

MfG

Sebastian

Windows XP, XProfan/Profan² 4.5 bis 11
Profan2Cpp-Homepage: [...]

Alte Profan²-Seite: [...]

RGH

it has me still no silence let. ;) so becomes it in RC5 weg:
Compile Mark Separation

WM_RBUTTONDOWN = $204
TEST: Rechtscklick auf Listbox
declare lb&
cls 0
lb&=create(ListBox,%hwnd,,100,10,100,100)

whileloop 10:addstring(lb&,):wend

    while 1

        waitinput

        if getfocus(lb&)

            case %Key = 3 : end

        endif

    endwhile

    end

Double click in a list box results in %key

= 3!

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

Frank
Abbing

I kapsele such inquire still always as Assembler-Sublassing-code, me would it alike. but nimm still too same whom semidetached-right-Click with in that boat, evantuelle too a semidetached-middle-Click...

Double click in Listbox results in %key

= 3!

I stops these Kleinigkeit for a the most important extensions the XProfan10!

RGH

Sebastian king

Hello iF,

let itself one Double-click on a ListBox not simply therefore intercepting, that one WM_COMMAND as UserMessage angibt and on LBN_DBLCLK wait?

MfG

Sebastian

in the principle JA. If HiWord(&wParam) then LBN_DBLCLK (=2) is (and getFocus() The Listbox determined), there were whom Double click, but:
with wm_Command as User Message would I softly-softly, because then goes except the intercepting the Doppelklicks almost nothing more, except one evaluates &wParam and &lParam self from, circa Menüklicks, Toolbarklicks, Buttonklicks, Mausposition, pressed Mausknopf and like More in experience To bring.

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

- Page 2 -

Michael
Wodrich

%Key

3
→ $03
→ Strg-disruption
→ VK_CANCEL

One Double click resolve means always one VK_CANCEL from??

Best wishes
Michael Wodrich

Programmieren, das spannendste Detektivspiel der Welt.

09/14/06 ▲

Sebastian
König

in the principle JA. If HiWord(&wParam) then LBN_DBLCLK (=2) is (and getFocus() The Listbox determined), there were whom Double click, but:
with wm_Command as User Message would I softly-softly, because then goes except the intercepting the Doppelklicks almost nothing more, except one evaluates &wParam and &lParam self from, circa Menüklicks, Toolbarklicks, Buttonklicks, Mausposition, pressed Mausknopf and like More in experience To bring.

alas Yes, had I do not bedacht.... the new Variante with %key is naturally too plenty bequemer!

@Michael: i think, with the VK_CANCEL is no trouble, there %key in the drop not staid becomes (if at all, then %scankey, think I). otherwise had it indeed Schonmal conflicts with %key = 4 (Resize, but too VK_MBUTTON) given...

MfG

Sebastian

Windows XP, XProfan/Profan² 4.5 bis 11
Profan2Cpp-Homepage: [...]

Alte Profan²-Seite: [...]

09/14/06 ▲

RGH

Hello Michael,

%Key supply whom ANSI-code the lastly squeezed Button and not its Scancode. VK_CANCEL is a Scancode. ANSI-Codes and Scancodes are two couple shoes

In Dialogfenstern and Hauptfenstern with Dialogstil lead Strg-Untbr likewise How z.B. old-F4 or the Closing-area To %Key = 2, what according Help means, that the Anweder the window close wants.

though have You to that part right: in the Mainwindow without Dialogstil lead Strg-Untbr, if the Focus not on one Dialogelement sits, To %Key = 3, there it then with Strg-C identical is. If to the white, can so bypass. (the was too the reason, Why %Key = 3 yet no particular weight having: with previous Profan-versions led Strg-C according one under DOS geltenden standard to that sofortigen Programmabbruch. this standard was too the reason, The Button Strg-Untbr with the Code Strg-C To occupy.)

(BTW: The Keys Strg-A To Strg-Z lead in the Mainwindow without Dialogstil, if the Focus not one Dialogelement lying, To %Key=1 To %Key=26, tab has the value 9 (Strg-I), Enter the value 13 (=Strg-M) and Ctrl-Enter the value 10 (Strg-J).)

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

09/14/06 ▲