Win32Lib Update

new topic     » topic index » view thread      » older message » newer message

I've sent Robert the latest version of Win32Lib.

[The Good News]

The new code contains the bug fixes that should take care of the memory
leaks.

[The Bad News]

Prior code will *break* under the new version. In particular, I've created a
new event for handling the mouse:

        onMouse( iEvent, iXPosition, iYPosition )

The iEvent values can be:

        MOUSE_MOVE
        LEFT_UP
        LEFT_DOWN
        LEFT_DOUBLECLICK
        RIGHT_UP
        RIGHT_DOWN
        RIGHT_DOUBLECLICK

This makes the following routines obsolete:

        onRightClick
        onDoubleClick

With onMouse handling LEFT_DOWN, I can remove the {x,y} parameter from:

        onClick()

to make it match VB. I can also remove:

        onMenu()

since onClick() now handles that function - again, aligning it with VB.

[Feedback Time]

Instead of the onMouse routine, I could instead create:

        onMouseMouse( iXPosition, iYPosition )
        onMouseUp( iButton, iXPosition, iYPosition )
        onMouseDown( iButton, iXPosition, iYPosition )
        onMouseDoubleClick( iButton, iXPosition, iYPosition )

which is more in line with VB, or even:

        onMouseMove( iXPosition, iYPosition )
        onLeftUp( iXPosition, iYPosition )
        onLeftDown( iXPosition, iYPosition )
        onLeftDoubleClick( iXPosition, iYPosition )
        onRightUp( iXPosition, iYPosition )
        onRightDown( iXPosition, iYPosition )
        onRightDoubleClick( iXPosition, iYPosition )

There is an addition parameter that I'm not yet including, which holds the
state of the Ctrl and Shift keys. I could include those as parameters, or
place them in a global variable.

What would people prefer?

-- David Cuny

new topic     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu