left click interrupt proc or macro

[dedndave]

it has been a long time since i played with 16-bit mouse stuff and INT 33h
but, as i remember, it allows you to install your own interrupt handler
let me review the documentation and get back to you...

[bcddd214]

Thank you!
I got all the pieces parts now, but making them all fit together neatly and functionally is my last leg of this madness.
She is coming together slowly though...

[bcddd214]

code update.
http://pastebin.com/vm3n1LuP

[dedndave]

here is a little test program
see if it works for you...

looking at your code, maybe there is something wrong with the IF/ELSE stuff
as you can see, i don't generally use those   :P

[bcddd214]

Does the replace my text input?
Just dump in main like the code, what do I delete?

[dedndave]

hang on - my code seems to have a bug - lol
it worked ok until i put the left-button stuff in there
let me play with it....

[dedndave]

strange behaviour
it works ok if i run the program by clicking on it in explorer
but, if i type the name at the prompt, it exits immediately

[bcddd214]

Is that just using your code exclusively or are you trying to run it from within mine?
Mine is pretty buggy too. That is the stage I am at, final debugging.   :(

[dedndave]

well - emulated 16-bit is not an ideal place to develop "cool" applications - lol
but - this should work

i made several changes to mine to see if i could isolate it
try it both ways and let me know what happens....

i am using XP pro SP3

[bcddd214]

you code appears to be work, it compiles fine and runs error free.
I guess I am not following as to what I should replace this code with?
my ascii input or mouse drives?
It appears to be the replacement for ascii and that should fix my hang?

[dedndave]

wellllll
i wanted to test our interpretation of INT 33h function 3

your code looks like it ought to work ok, unless i am reading the IF/ELSE/ENDOF stuff wrong   :P
so - i wanted to verify that what i think should happen with the function is what is happening
once we verify that - we'll have a look at the IF/ELSE/ENDOF stuff
perhaps with DEBUG, or by looking at the listing

[dedndave]

let me get a nap in   :bg
i will play with yours afterwards to see what i can see

[bcddd214]

I am not the debug master of asm yet but I did figure out how to do a memory dump using debug. I am not sure what this all means, but it's a start.

-d 0 8f
17F2:0000  CD 20 FF 9F 00 9A EE FE-1D F0 4F 03 56 12 8A 03   . ........O.V...
17F2:0010  56 12 17 03 56 12 2C 07-01 01 01 00 02 FF FF FF   V...V.,.........
17F2:0020  FF FF FF FF FF FF FF FF-FF FF FF FF DA 11 4E 01   ..............N.
17F2:0030  16 17 14 00 18 00 F2 17-FF FF FF FF 00 00 00 00   ................
17F2:0040  05 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   ................
17F2:0050  CD 21 CB 00 00 00 00 00-00 00 00 00 00 20 20 20   .!...........
17F2:0060  20 20 20 20 20 20 20 20-00 00 00 00 00 20 20 20           .....
17F2:0070  20 20 20 20 20 20 20 20-00 00 00 00 00 00 00 00           ........
17F2:0080  00 0D 6E 65 77 44 4F 53-32 0D 41 32 32 30 20 49   ..newDOS2.A220 I

[bcddd214]

It is definitely the mouse driver creating the hang, if I rem out the calling in main for the mouse driver, it does not hang anymore.

[dedndave]

ok - i had my power-nap   :bg

let's have a look
i will use SYMDEB - it's DEBUG on steroids
the biggest improvement is that with SYMDEB - you can set breakpoints and execute code til it hits one