Print Page - events and malloc in QB64?

Title: events and malloc in QB64?
Post by: madscijr on March 30, 2021, 12:30:04 pm

Hi everyone.

I'm attempting to convert this manymouse library to QB64:
https://github.com/NoobsArePeople2/manymouse (https://github.com/NoobsArePeople2/manymouse)

TempodiBasic pointed out how the API declarations can be done in QB64.
It might help if I knew C, but I figure I'll try slogging through it.
Now I am seeing other stuff that I'm not so sure about.
I'm running into are these references to files that aren't on the github, that I assume are basic C libraries for Windows?

Code: C: [Select]

#define WIN32_LEAN_AND_MEAN 1
#include <windows.h>
#include <setupapi.h>
#include <malloc.h>  /* needed for alloca(). */
 

malloc
I am not finding anything on "malloc" in QB64.
Is there an equivalent or some workaround in QB64 for code like this?

Code: C: [Select]

    lpb = (LPBYTE) alloca(dwSize);
    if (lpb == NULL)
        return;
 

events
There is also some event handling:

Code: C: [Select]

#define MAX_EVENTS 1024
static ManyMouseEvent input_events[MAX_EVENTS];
static volatile int input_events_read = 0;
static volatile int input_events_write = 0;
 

I am not finding anything related to events in QB64.
What would you do to get that functionality to work?

Code: C: [Select]

static void queue_from_rawinput(const RAWINPUT *raw)
{
    int i;
    const RAWINPUTHEADER *header = &raw->header;
    const RAWMOUSE *mouse = &raw->data.mouse;
    ManyMouseEvent event;
etc.
 

Any advice or assistance would be much appreciated!

Title: Re: events and malloc in QB64?
Post by: bplus on March 30, 2021, 12:37:34 pm

Malloc = memory allocation see _Mem stuff @SMcNeill good with that, Steve also has worked with _DEVICE$

API see @SpriggsySpriggs
Here is ref link: https://www.qb64.org/forum/index.php?topic=2930.msg121883#msg121883

Title: Re: events and malloc in QB64?
Post by: madscijr on March 30, 2021, 12:48:26 pm

Quote from: bplus on March 30, 2021, 12:37:34 pm

Malloc = memory allocation see _Mem stuff @SMcNeill good with that, Steve also has worked with _DEVICE$

API see @SpriggsySpriggs

Thanks... Is it even possible to have event handlers in QB64?

Title: Re: events and malloc in QB64?
Post by: bplus on March 30, 2021, 12:52:17 pm

Quote from: madscijr on March 30, 2021, 12:48:26 pm

Thanks... Is it even possible to have event handlers in QB64?

I think so, see what @FellippeHeitor has done with InForm working Events driven model. Very much like VB.

Title: Re: events and malloc in QB64?
Post by: madscijr on March 30, 2021, 01:48:42 pm

Quote from: bplus on March 30, 2021, 12:52:17 pm

I think so, see what @FellippeHeitor has done with InForm working Events driven model. Very much like VB.

Thanks... maybe this?
https://www.qb64.org/forum/index.php?topic=2113.msg113549;topicseen#msg113549 (https://www.qb64.org/forum/index.php?topic=2113.msg113549;topicseen#msg113549)
or
https://www.qb64.org/forum/index.php?topic=524.msg3778;topicseen#msg3778 (https://www.qb64.org/forum/index.php?topic=524.msg3778;topicseen#msg3778)

Title: Re: events and malloc in QB64?
Post by: SpriggsySpriggs on March 30, 2021, 01:50:30 pm

@madscijr Hey! I've been super busy recently but I'm glad you have been looking through that manymouse repo. I'm going to try looking at it tonight and see how far I can start getting with QB64. Some portions should be relatively simple but others could be next to impossible.

Title: Re: events and malloc in QB64?
Post by: madscijr on March 30, 2021, 02:08:11 pm

Oy vey! LoL

Title: Re: events and malloc in QB64?
Post by: madscijr on March 30, 2021, 02:09:42 pm

Quote from: SpriggsySpriggs on March 30, 2021, 01:50:30 pm

@madscijr Hey! I've been super busy recently but I'm glad you have been looking through that manymouse repo. I'm going to try looking at it tonight and see how far I can start getting with QB64. Some portions should be relatively simple but others could be next to impossible.

That would be great.
I'm trying to stay positive about this, but looking at the C code:
https://github.com/NoobsArePeople2/manymouse/blob/master/windows_wminput.c (https://github.com/NoobsArePeople2/manymouse/blob/master/windows_wminput.c)
https://github.com/NoobsArePeople2/manymouse/blob/master/manymouse.c (https://github.com/NoobsArePeople2/manymouse/blob/master/manymouse.c)

TLDR: is it even possible to translate these to QB64?

I don't know C but I've been able to figure out logic from other languages in the past, enough to translate it to a language I do know. But this code has a ton of keywords, types, and syntax that I don't recognize at all:

HDEVINFO
ATOM
LRESULT
HMODULE
DWORD - I think I've seen this keyword in regedit?
CRITICAL_SECTION
HANDLE
HINSTANCE
WNDCLASSEX
SP_DEVINFO_DATA
size_t

and functions too like

GetProcAddress
FreeLibrary
LoadLibrary
LOOKUP (a bunch inside routine find_api_symbols)
sizeof
MSG

I'd have to google some C to understand alien syntax like

Code: C: [Select]

mouse->handle = dev->hDevice;
if (++i >= available_mice)
if (mouse->handle != NULL) 
 

Also, then there is OO looking stuff where they reference properties, like:

Code: C: [Select]

if (mice[i].handle == header->hDevice)
 

and

Code: C: [Select]

if (mouse->usFlags & MOUSE_MOVE_ABSOLUTE)
    {
        /* !!! FIXME: How do we get the min and max values for absmotion? */
        event.type = MANYMOUSE_EVENT_ABSMOTION;
        event.item = 0;
        event.value = mouse->lLastX;
        queue_event(&event);
        event.item = 1;
        event.value = mouse->lLastY;
        queue_event(&event);
    } /* if */
 

and

Code: C: [Select]

static const ManyMouseDriver ManyMouseDriver_interface =
{
    "Windows XP and later WM_INPUT interface",
    windows_wminput_init,
    windows_wminput_quit,
    windows_wminput_name,
    windows_wminput_poll
};
 

I'm very fuzzy on how interfaces work, I would expect that is outside the capability of QB64?

I found a couple of sites that look like they might have some info on some of the above keywords

https://www.angelfire.com/hi5/delphizeus/lifts.html (https://www.angelfire.com/hi5/delphizeus/lifts.html)
https://docs.microsoft.com/en-us/windows/win32/winprog/windows-data-types (https://docs.microsoft.com/en-us/windows/win32/winprog/windows-data-types)

Some things look familiar, but not sure if QB64 has an equivalent of, like

HWND (I remember that from VB6)
static
volatile

Some that are probably covered under the _MEM functions in QB64 like:

CopyMemory
ZeroMemory
alloca

Some familiar terms I would guess have a QB64 equivalent (I have to look up):

uint
static unsigned int - what's the difference between "uint" and "unsigned int"?

I guess what I'm asking now is, does this look like something that can be converted to QB64, or would I need to get a C compiler and somehow compile it into a DLL library that I would call from QB?

Despairingly yours,
Not a C programmer!

Title: Re: events and malloc in QB64?
Post by: bplus on March 30, 2021, 02:10:07 pm

Quote

Thanks... maybe this?

@madscijr

There is a whole board at this forum devoted to InForm, but for your needs, setting event driven app, you might have to dig into his source code. There is probably a github link in the InForm Board.

I have to admit, yours is first inquiry I've ever seen about multiple mice. I do know that with device you can pickup joystick input but more than one mouse...?

Title: Re: events and malloc in QB64?
Post by: SpriggsySpriggs on March 30, 2021, 02:45:06 pm

@madscijr

Quote from: madscijr on March 30, 2021, 02:09:42 pm

HDEVINFO
//a handle will always be _OFFSET
ATOM
//an INTEGER
LRESULT
//an _OFFSET
HMODULE
//a handle will always be _OFFSET
DWORD - I think I've seen this keyword in regedit?
//DWORD corresponds to LONG
CRITICAL_SECTION
//not sure, will have to look this up. From what I see, similar to a MUTEX object.
HANDLE
//a handle will always be _OFFSET
HINSTANCE
//handle, _OFFSET
WNDCLASSEX
//just a custom struct, https://docs.microsoft.com/en-us/windows/win32/api/winuser/ns-winuser-wndclassexa (https://docs.microsoft.com/en-us/windows/win32/api/winuser/ns-winuser-wndclassexa)
SP_DEVINFO_DATA
//custom struct, https://docs.microsoft.com/en-us/windows/win32/api/setupapi/ns-setupapi-sp_devinfo_data (https://docs.microsoft.com/en-us/windows/win32/api/setupapi/ns-setupapi-sp_devinfo_data)
size_t
//I believe that this is also an _OFFSET

and functions too like
GetProcAddress
//this function, along with FreeLibrary and LoadLibrary are some that I have used in a different topic about runtime calls here https://www.qb64.org/forum/index.php?topic=3756.0 (https://www.qb64.org/forum/index.php?topic=3756.0)
FreeLibrary
LoadLibrary
LOOKUP (a bunch inside routine find_api_symbols)
//this should be able to be done using the above functions in our own wrapper
sizeof
//this is just our LEN() keyword
MSG
//this is a struct. We'd have to rewrite it in QB64: https://docs.microsoft.com/en-us/windows/win32/api/winuser/ns-winuser-msg (https://docs.microsoft.com/en-us/windows/win32/api/winuser/ns-winuser-msg)
[/list][/list]
Code: C: [Select]
mouse->handle = dev->hDevice; //this is basically saying mouse.handle = dev.hDevice
if (++i >= available_mice)
if (mouse->handle != NULL) //if mouse.handle <> 0

Also, then there is OO looking stuff where they reference properties, like: //the stuff is really just using custom TYPEs, or structs. Like a UDT in QB64
Code: C: [Select]
if (mice[i].handle == header->hDevice) //if mice(i).handle = header.hDevice

and
Code: C: [Select]
if (mouse->usFlags & MOUSE_MOVE_ABSOLUTE) //if mouse.usFlags AND MOUSE_MOVE_ABSOLUTE
{
/* !!! FIXME: How do we get the min and max values for absmotion? */
event.type = MANYMOUSE_EVENT_ABSMOTION;
event.item = 0;
event.value = mouse->lLastX;
queue_event(&event);
event.item = 1;
event.value = mouse->lLastY;
queue_event(&event);
} /* if */

Some things look familiar, but not sure if QB64 has an equivalent of, like
HWND (I remember that from VB6)
//HWND is the Handle to the Window. For QB64, if referencing OUR program's window, it's
_WINDOWHANDLE
static
//we have STATIC as well
volatile
//I will have to look this one up
[/list]

Some that are probably covered under the _MEM functions in QB64 like:
CopyMemory
//we have this
ZeroMemory
//we also have this
alloca
//I will have to look this one up
[/list]

uint
//we have this as _UNSIGNED LONG
static unsigned int - what's the difference between "uint" and "unsigned int"?
//I think "UINT" is used in Win32 API and "unsigned int" is just the regular C++ definition, I believe
[/list]

I guess what I'm asking now is, does this look like something that can be converted to QB64, or would I need to get a C compiler and somehow compile it into a DLL library that I would call from QB? //probably, but looks difficult in some areas

I hope this helps to answer some of the questions, at least

Title: Re: events and malloc in QB64?
Post by: madscijr on March 30, 2021, 02:53:55 pm

Quote from: bplus on March 30, 2021, 02:10:07 pm

@madscijr
I have to admit, yours is first inquiry I've ever seen about multiple mice. I do know that with device you can pickup joystick input but more than one mouse...?

Thank you for your reply.
I did try using _DEVICE, but it didn't seem to work.
Maybe I'm doing something wrong?
Here is my test code:

Code: QB64: [Select]

' #############################################################################
' MULTIMOUSE
' ----------
' A proof of concept / experiment to try to get the computer to read
' 2 or mice plugged into the computer, as separate devices,
' to control 2 or more cursors on the screen (for multiplayer games, etc.)
'
' #############################################################################
 
' =============================================================================
' GLOBAL DECLARATIONS a$=string, i%=integer, L&=long, s!=single, d#=double
CONST FALSE = 0
CONST TRUE = NOT FALSE
 
DIM ProgramPath$
DIM ProgramName$
 
' =============================================================================
' INITIALIZE
ProgramName$ = MID$(COMMAND$(0), _INSTRREV(COMMAND$(0), "\") + 1)
ProgramPath$ = LEFT$(COMMAND$(0), _INSTRREV(COMMAND$(0), "\"))
 
' =============================================================================
' TRY THE MOUSE
main ProgramName$
 
' =============================================================================
' FINISH
SYSTEM ' return control to the operating system
PRINT ProgramName$ + " finished."
END
 
' /////////////////////////////////////////////////////////////////////////////
 
SUB main (ProgName$)
    DIM in$: in$ = ""
    DO
        CLS
        PRINT ProgName$
        PRINT
        PRINT "How can we get separate input from 2 or more USB mice "
        PRINT "plugged into one computer?"
        PRINT
        PRINT "1. Test using _MOUSEX, _MOUSEY, etc."
        PRINT
        PRINT "2. Test using _DEVICE commands"
        PRINT
        PRINT "3. Enumerate devices with _DEVICES to try and detect >1 mouse"
        PRINT
        PRINT "What to do ('q' to exit)"
 
        INPUT in$: in$ = LCASE$(LEFT$(in$, 1))
        IF in$ = "1" THEN
            MouseInputTest in$
        ELSEIF in$ = "2" THEN
            MouseInputTest in$
        ELSEIF in$ = "3" THEN
            EnumerateDevices
        END IF
    LOOP UNTIL in$ = "q"
END SUB ' main
 
' /////////////////////////////////////////////////////////////////////////////
' Gets mouse input using _MOUSEX, _MOUSEY, _MOUSEBUTTON commands.
 
SUB MouseInputTest (in$)
    ' UDT TO HOLD THE INFO FOR EACH MOUSE
    TYPE InfoType
        c AS STRING ' cursor character
        x AS INTEGER ' screen x position
        y AS INTEGER ' screen y position
        wheel AS INTEGER ' mouse wheel value
        LeftDown AS INTEGER ' tracks left mouse button state, TRUE=down
        MiddleDown AS INTEGER ' tracks middle mouse button state, TRUE=down
        RightDown AS INTEGER ' tracks right mouse button state, TRUE=down
        LeftCount AS INTEGER ' counts left clicks
        MiddleCount AS INTEGER ' counts middle clicks
        RightCount AS INTEGER ' counts right clicks
    END TYPE ' InfoType
 
    ' MIN/MAX VALUES
    CONST cMinX = 2
    CONST cMaxX = 79
    CONST cMinY = 16
    CONST cMaxY = 24
    CONST cMinWheel = 0
    CONST cMaxWheel = 255
 
    ' MAIN VARIABLES
    DIM iCount AS INTEGER ' # OF MICE ATTACHED
    DIM arrMouseID(8) AS STRING ' device IDs for mice connected to system (guessing this would be a string, dunno)
    DIM arrInfo(8) AS InfoType ' STORES INFO FOR EACH MOUSE
    DIM left%, middle%, right% ' temp mouse variables
    DIM iLoop AS INTEGER
    DIM iIndex AS INTEGER
 
    ' TEMP VARIABLES FOR DISPLAYING FORMATTED VALUES TO SCREEN
    DIM iLen AS INTEGER
    DIM sCount AS STRING
    DIM sX AS STRING
    DIM sY AS STRING
    DIM sWheel AS STRING
    DIM sLeftDown AS STRING
    DIM sMiddleDown AS STRING
    DIM sRightDown AS STRING
    DIM sLeftCount AS STRING
    DIM sMiddleCount AS STRING
    DIM sRightCount AS STRING
 
    ' MOUSE CURSORS (JUST SOME LETTERS)
    CData:
    DATA A,b,C,D,E,f,G,H
 
    ' DEFAULT/INTIAL X COORDINATE OF EACH CURSOR ON SCREEN
    XData:
    DATA 5,15,25,35,45,55,65,75
 
    ' DEFAULT/INTIAL Y COORDINATE OF EACH CURSOR ON SCREEN
    YData:
    DATA 17,17,19,19,21,21,23,23
 
    ' DEFAULT/INITIAL VALUE OF EACH SCROLL WHEEL
    WData:
    DATA 224,192,160,128,96,64,32,0
 
    ' COUNT # OF MICE CONNECTED + GET DEVICE IDs
    iCount = GetMouseCount% ' THIS FUNCTION WOULD ENUMERATE MICE, SHOULD RETURN 1+
    IF (iCount > 8) THEN iCount = 8: ' FOR NOW ONLY SUPPORT UPTO 8 MICE
    GetMouseIDs arrMouseID() ' GET MOUSE IDs
 
    ' INITIALIZE CURSORS, MOUSE STATE, ETC.
    RESTORE CData
    iIndex = LBOUND(arrInfo) - 1
    FOR iLoop = 1 TO iCount
        iIndex = iIndex + 1
        READ arrInfo(iIndex).c
        ' INITIALIZED BELOW: arrInfo(iIndex).x = 0
        ' INITIALIZED BELOW: arrInfo(iIndex).y = 0
        ' INITIALIZED BELOW: arrInfo(iIndex).wheel = 127
        arrInfo(iIndex).LeftDown = FALSE
        arrInfo(iIndex).MiddleDown = FALSE
        arrInfo(iIndex).RightDown = FALSE
        arrInfo(iIndex).LeftCount = 0
        arrInfo(iIndex).MiddleCount = 0
        arrInfo(iIndex).RightCount = 0
    NEXT iLoop
 
    ' INITIALIZE X COORDINATES
    RESTORE XData
    iIndex = LBOUND(arrInfo) - 1
    FOR iLoop = 1 TO iCount
        iIndex = iIndex + 1
        READ arrInfo(iIndex).x
    NEXT iLoop
 
    ' INITIALIZE Y COORDINATES
    RESTORE YData
    iIndex = LBOUND(arrInfo) - 1
    FOR iLoop = 1 TO iCount
        iIndex = iIndex + 1
        READ arrInfo(iIndex).y
    NEXT iLoop
 
    ' INITIALIZE SCROLL WHEEL
    RESTORE WData
    iIndex = LBOUND(arrInfo) - 1
    FOR iLoop = 1 TO iCount
        iIndex = iIndex + 1
        READ arrInfo(iIndex).wheel
    NEXT iLoop
 
    ' DRAW PLAYING FIELD
    _SCREENMOVE _MIDDLE
    CLS ' clear screen
    LOCATE 1, 1: PRINT "1. PLUG 1-8 MICE INTO THE COMPUTER"
    LOCATE 2, 1: PRINT "2. USE MICE TO POSITION LETTERS ON SCREEN"
    LOCATE 3, 1: PRINT "3. PRESS <ESC> TO QUIT"
    LOCATE 4, 1: PRINT "--------------------------------------------------------------------------------";
    LOCATE 5, 1: PRINT "#  X  Y  Wheel LeftDown MiddleDown RightDown LeftCount MiddleCount RightCount   "
    LOCATE 6, 1: PRINT "--------------------------------------------------------------------------------";
 
    ' NOTE: LEAVE THE NEXT 8 LINES FREE (ROWS 8-15)
    '       TO DISPLAY TEST VALUES FOR UPTO 8 MICE
 
    ' DRAW BORDER AROUND PLAYING FIELD
    DrawTextLine cMinX - 1, cMinY - 1, cMinX - 1, cMaxY + 1, "#"
    DrawTextLine cMinX - 1, cMinY - 1, cMaxX + 1, cMinY - 1, "#"
    DrawTextLine cMaxX + 1, cMaxY + 1, cMaxX + 1, cMinY - 1, "#"
    DrawTextLine cMaxX + 1, cMaxY + 1, cMinX - 1, cMaxY + 1, "#"
 
    ' GET INPUT AND MOVE PLAYERS
    DO
        iIndex = LBOUND(arrInfo) - 1
        FOR iLoop = 1 TO iCount
            iIndex = iIndex + 1
 
            ' ERASE CURSORS AT CURRENT POSITION
            LOCATE arrInfo(iIndex).y, arrInfo(iIndex).x: PRINT " ";
 
            ' GET NEXT MOUSE INPUT
            IF in$ = "1" THEN
                ReadMouse1 arrMouseID(iIndex), arrInfo(iIndex).x, arrInfo(iIndex).y, left%, middle%, right%, arrInfo(iIndex).wheel, cMinWheel, cMaxWheel
            ELSEIF in$ = "2" THEN
                ReadMouse2 arrMouseID(iIndex), arrInfo(iIndex).x, arrInfo(iIndex).y, left%, middle%, right%, arrInfo(iIndex).wheel, cMinWheel, cMaxWheel
            END IF
 
            ' HANDLE LEFT MOUSE BUTTON
            IF left% THEN
                IF arrInfo(iIndex).LeftDown = FALSE THEN
                    ' BUTTON DOWN EVENT
                    arrInfo(iIndex).LeftDown = TRUE
                    arrInfo(iIndex).LeftCount = arrInfo(iIndex).LeftCount + 1
                END IF
            ELSE
                IF arrInfo(iIndex).LeftDown = TRUE THEN
                    ' BUTTON UP EVENT
                    arrInfo(iIndex).LeftDown = FALSE
                END IF
            END IF
 
            ' HANDLE MIDDLE MOUSE BUTTON (SCROLL WHEEL BUTTON)
            IF middle% THEN
                IF arrInfo(iIndex).MiddleDown = FALSE THEN
                    ' BUTTON DOWN EVENT
                    arrInfo(iIndex).MiddleDown = TRUE
                    arrInfo(iIndex).MiddleCount = arrInfo(iIndex).MiddleCount + 1
                END IF
            ELSE
                IF arrInfo(iIndex).MiddleDown = TRUE THEN
                    ' BUTTON UP EVENT
                    arrInfo(iIndex).MiddleDown = FALSE
                END IF
            END IF
 
            ' HANDLE RIGHT MOUSE BUTTON
            IF right% THEN
                IF arrInfo(iIndex).RightDown = FALSE THEN
                    ' BUTTON DOWN EVENT
                    arrInfo(iIndex).RightDown = TRUE
                    arrInfo(iIndex).RightCount = arrInfo(iIndex).RightCount + 1
                END IF
            ELSE
                IF arrInfo(iIndex).RightDown = TRUE THEN
                    ' BUTTON UP EVENT
                    arrInfo(iIndex).RightDown = FALSE
                END IF
            END IF
 
            ' CHECK BOUNDARIES
            IF arrInfo(iIndex).x < cMinX THEN arrInfo(iIndex).x = cMinX
            IF arrInfo(iIndex).x > cMaxX THEN arrInfo(iIndex).x = cMaxX
            IF arrInfo(iIndex).y < cMinY THEN arrInfo(iIndex).y = cMinY
            IF arrInfo(iIndex).y > cMaxY THEN arrInfo(iIndex).y = cMaxY
 
            ' PLOT CURSOR
            LOCATE arrInfo(iIndex).y, arrInfo(iIndex).x: PRINT arrInfo(iIndex).c;
 
            ' DISPLAY VARIABLES
            iLen = 3: sCount = LEFT$(LTRIM$(RTRIM$(STR$(iLoop))) + STRING$(iLen, " "), iLen)
            iLen = 3: sX = LEFT$(LTRIM$(RTRIM$(STR$(arrInfo(iIndex).x))) + STRING$(iLen, " "), iLen)
            iLen = 3: sY = LEFT$(LTRIM$(RTRIM$(STR$(arrInfo(iIndex).y))) + STRING$(iLen, " "), iLen)
            iLen = 6: sWheel = LEFT$(LTRIM$(RTRIM$(STR$(arrInfo(iIndex).wheel))) + STRING$(iLen, " "), iLen)
            iLen = 9: sLeftDown = LEFT$(LTRIM$(RTRIM$(STR$(arrInfo(iIndex).LeftDown))) + STRING$(iLen, " "), iLen)
            iLen = 11: sMiddleDown = LEFT$(LTRIM$(RTRIM$(STR$(arrInfo(iIndex).MiddleDown))) + STRING$(iLen, " "), iLen)
            iLen = 10: sRightDown = LEFT$(LTRIM$(RTRIM$(STR$(arrInfo(iIndex).RightDown))) + STRING$(iLen, " "), iLen)
            iLen = 10: sLeftCount = LEFT$(LTRIM$(RTRIM$(STR$(arrInfo(iIndex).LeftCount))) + STRING$(iLen, " "), iLen)
            iLen = 12: sMiddleCount = LEFT$(LTRIM$(RTRIM$(STR$(arrInfo(iIndex).MiddleCount))) + STRING$(iLen, " "), iLen)
            iLen = 11: sRightCount = LEFT$(LTRIM$(RTRIM$(STR$(arrInfo(iIndex).RightCount))) + STRING$(iLen, " "), iLen)
 
            'LOCATE 5,       1: PRINT "#  X  Y  Wheel LeftDown MiddleDown RightDown LeftCount MiddleCount RightCount   "
            LOCATE 6 + iLoop, 1: PRINT sCount + sX + sY + sWheel + sLeftDown + sMiddleDown + sRightDown + sLeftCount + sMiddleCount + sRightCount
 
        NEXT iLoop
 
        _LIMIT 100 ' keep loop at 100 frames per second
    LOOP UNTIL _KEYDOWN(27) ' escape key exit
    _KEYCLEAR: '_DELAY 1
END SUB ' MouseInputTest
 
' /////////////////////////////////////////////////////////////////////////////
' Returns a count of # of mouse devices connected to the system
 
' *** Currently hardcoded to 1 until we figure out how to do this. ***
 
FUNCTION GetMouseCount% ()
    GetMouseCount% = 1
END FUNCTION ' GetMouseCount%
 
' /////////////////////////////////////////////////////////////////////////////
' Gets ID of each mouse device connected to the system (for now upto 8)
' and returns the IDs in an array of strings
' (assuming the ID is a string and not numeric?).
' If no mouse found, the ID will just be a blank string.
 
' *** Currently hardcoded to "1" until we figure out how to do this. ***
 
SUB GetMouseIDs (arrMouseID( 8) AS STRING)
    DIM iLoop AS INTEGER
 
    ' CLEAR OUT IDs
    FOR iLoop = 1 TO 8
        arrMouseID(iLoop) = ""
    NEXT iLoop
 
    ' GET IDs
    arrMouseID(1) = "1" ' for now just fudge it!
 
END SUB ' GetMouseCount%
 
' /////////////////////////////////////////////////////////////////////////////
' Read mouse method #1, using _MOUSEX, _MOUSEY, etc.
 
' Gets input from mouse identified by deviceid$
' (or does that needs to be an ordinal position?)
 
' For version 1 we only return the input from the one mouse
' regardless of deviceid$.
 
' NOTE: click events (mouse up/mouse down) are handled by the calling sub,
'       this routine just sends back
'       TRUE if the given button is currently down or FALSE if it is up.
 
' Parameters (values returned):
' x% = x position of mouse pointer
' y% = y position of mouse pointer
' left% = current state of left mouse button (up or down)
' middle% = current state of middle mouse button / scroll wheel button (up or down)
' right% = current state of right mouse button (up or down)
' wheel% = value of mouse scroll wheel (passed in and incremented/decremented by 1 if wheel move detected)
 
' Parameters (input only):
' wheelmin% = minimum value to allow wheel% to be decremented to
' wheelmax% = maximum value to allow wheel% to be incremened to
 
SUB ReadMouse1 (deviceid$, x%, y%, left%, middle%, right%, wheel%, wheelmin%, wheelmax%)
    DIM scrollAmount%
 
    ' read scroll wheel
    WHILE _MOUSEINPUT ' get latest mouse information
        scrollAmount% = _MOUSEWHEEL ' (Returns -1 when scrolling up and 1 when scrolling down with 0 indicating no movement since last read.)
        IF (scrollAmount% = -1) AND (wheel% > wheelmin%) THEN
            wheel% = wheel% + scrollAmount%
        ELSEIF (scrollAmount% = 1) AND (wheel% < wheelmax%) THEN
            wheel% = wheel% + scrollAmount%
        END IF
    WEND
 
    ' read x position
    x% = _MOUSEX
 
    ' read y position
    y% = _MOUSEY
 
    ' read mouse buttons
    left% = _MOUSEBUTTON(1)
    middle% = _MOUSEBUTTON(3)
    right% = _MOUSEBUTTON(2)
 
END SUB ' ReadMouse1
 
' /////////////////////////////////////////////////////////////////////////////
' Read mouse method #2, using _DEVICE commands.
 
' Gets input from mouse identified by deviceid$
' (or does that needs to be an ordinal position?)
 
' For version 1 we only return the input from the one mouse
' regardless of deviceid$.
 
' NOTE: click events (mouse up/mouse down) are handled by the calling sub,
'       this routine just sends back
'       TRUE if the given button is currently down or FALSE if it is up.
 
' Parameters (values returned):
' x% = x position of mouse pointer
' y% = y position of mouse pointer
' left% = current state of left mouse button (up or down)
' middle% = current state of middle mouse button / scroll wheel button (up or down)
' right% = current state of right mouse button (up or down)
' wheel% = value of mouse scroll wheel (passed in and incremented/decremented by 1 if wheel move detected)
 
' Parameters (input only):
' wheelmin% = minimum value to allow wheel% to be decremented to
' wheelmax% = maximum value to allow wheel% to be incremened to
 
SUB ReadMouse2 (deviceid$, x%, y%, left%, middle%, right%, wheel%, wheelmin%, wheelmax%)
    DIM scrollAmount%
    DIM ScreenWidth% ' screen width
    DIM ScreenHeight% ' screen height
 
    ' read scroll wheel
    WHILE _DEVICEINPUT(2) ' clear and update the mouse buffer
        scrollAmount% = _WHEEL(3)
        IF (scrollAmount% = -1) AND (wheel% > wheelmin%) THEN
            wheel% = wheel% + scrollAmount%
        ELSEIF (scrollAmount% = 1) AND (wheel% < wheelmax%) THEN
            wheel% = wheel% + scrollAmount%
        END IF
    WEND ' clear and update the mouse buffer
 
    ' read x position
    ScreenWidth% = _WIDTH \ 2
    x% = _AXIS(1) * ScreenWidth% + ScreenWidth%
 
    ' read y position
    ScreenHeight% = _HEIGHT \ 2
    y% = _AXIS(2) * ScreenHeight% + ScreenHeight%
 
    ' read mouse buttons
    left% = _BUTTON(1)
    middle% = _BUTTON(2)
    right% = _BUTTON(3)
 
END SUB ' ReadMouse2
 
' /////////////////////////////////////////////////////////////////////////////
' ORIGINAL VERSION OF FUNCTION FOR READING MOUSE WITH _DEVICE:
 
' Gets mouse input using _DEVICE commands (part 2 of 2, subroutine)
 
' SOURCE : https://www.qb64.org/forum/index.php?topic=1087.0
' Subject: Mouse demo using _DEVICE commands
' From   : SMcNeill
' Date   : February 21, 2019, 06:15:28 AM »
 
SUB UpdateMouseInfo (MouseX AS INTEGER, MouseY AS INTEGER, MOUSEWHEEL AS INTEGER, LeftMouse AS INTEGER, RightMouse AS INTEGER, MiddleMouse AS INTEGER, ClickThreshold AS SINGLE)
    DIM SW AS INTEGER, SH AS INTEGER
    DIM LM AS INTEGER, MM AS INTEGER, RM AS INTEGER
 
    STATIC leftdown AS SINGLE, middledown AS SINGLE, rightdown AS SINGLE
 
    WHILE _DEVICEINPUT(2): MOUSEWHEEL = MOUSEWHEEL + _WHEEL(3): WEND 'clear and update the mouse buffer
 
    SW = _WIDTH \ 2: SH = _HEIGHT \ 2
    MouseX = _AXIS(1) * SW + SW: MouseY = _AXIS(2) * SH + SH
 
 
 
    LM = _BUTTON(1): MM = _BUTTON(2): RM = _BUTTON(3)
 
    IF leftdown THEN 'if it was down
        IF LM = 0 THEN 'and is now up
            IF TIMER - leftdown < ClickThreshold THEN
                LeftMouse = 2 'clicked
            ELSE 'if it's still down
                LeftMouse = 0 'the mouse was just released
            END IF
            leftdown = 0 'timer is cleared either way
        ELSE
            LeftMouse = 1 'the left mouse is down , timer should have already been set
        END IF
    ELSE
        IF LM THEN
            leftdown = TIMER 'set the timer to see if we have click or hold events
            LeftMouse = 1 'the left mouse is down
        ELSE
            LeftMouse = 0
        END IF
    END IF
 
    IF middledown THEN 'if it was down
        IF MM = 0 THEN 'and is now up
            IF TIMER - middledown < ClickThreshold THEN
                MiddleMouse = 2 'clicked
            ELSE 'if it's still down
                MiddleMouse = 0 'the mouse was just released
            END IF
            middledown = 0 'timer is cleared either way
        ELSE
            MiddleMouse = 1 'the middle mouse is down , timer should have already been set
        END IF
    ELSE
        IF MM THEN
            middledown = TIMER 'set the timer to see if we have click or hold events
            MiddleMouse = 1 'the middle mouse is down
        ELSE
            MiddleMouse = 0
        END IF
    END IF
 
    IF rightdown THEN 'if it was down
        IF RM = 0 THEN 'and is now up
            IF TIMER - rightdown < ClickThreshold THEN
                RightMouse = 2 'clicked
            ELSE 'if it's still down
                RightMouse = 0 'the mouse was just released
            END IF
            rightdown = 0 'timer is cleared either way
        ELSE
            RightMouse = 1 'the right mouse is down , timer should have already been set
        END IF
    ELSE
        IF RM THEN
            rightdown = TIMER 'set the timer to see if we have click or hold events
            RightMouse = 1 'the right mouse is down
        ELSE
            RightMouse = 0
        END IF
    END IF
 
 
END SUB ' UpdateMouseInfo
 
' /////////////////////////////////////////////////////////////////////////////
' Example: Checking for the system's input devices.
 
' _DEVICES FUNCTION (QB64 REFERENCE)
' http://www.[abandoned, outdated and now likely malicious qb64 dot net website - don’t go there]/wiki/index_title_DEVICES/
'
' The _DEVICES function returns the number of INPUT devices on your computer
' including keyboard, mouse and game devices.
'
' Syntax:
'
' device_count% = _DEVICES
'
' Returns the number of devices that can be listed separately with the _DEVICE$
' function by the device number.
' Devices include keyboard, mouse, joysticks, game pads and multiple stick game
' controllers.
' Note: This function MUST be read before trying to use the _DEVICE$,
' _DEVICEINPUT or _LAST control functions!
 
' Note: The STRIG/STICK commands won't read from the keyboard
'       or mouse device the above example lists.
 
SUB EnumerateDevices
    DIM devices%
    DIM iLoop%
    DIM sCount$
    DIM iLen AS INTEGER
 
    devices% = _DEVICES ' MUST be read in order for other 2 device functions to work!
 
    CLS
    PRINT "Total devices found: "; STR$(devices%)
    FOR iLoop% = 1 TO devices%
        iLen = 4
        sCount$ = LEFT$(LTRIM$(RTRIM$(STR$(iLoop%))) + STRING$(iLen, " "), iLen)
        PRINT sCount$ + _DEVICE$(iLoop%) + " (" + LTRIM$(RTRIM$(STR$(_LASTBUTTON(iLoop%)))) + " buttons)"
    NEXT iLoop%
    PRINT
    PRINT "PRESS <ESC> TO CONTINUE"
    DO: LOOP UNTIL _KEYDOWN(27) ' leave loop when ESC key pressed
    _KEYCLEAR: '_DELAY 1
 
END SUB ' EnumerateDevices
 
' /////////////////////////////////////////////////////////////////////////////
' based on code from:
' Qbasic Programs - Download free bas source code
' http://www.thedubber.altervista.org/qbsrc.htm
 
SUB DrawTextLine (y%, x%, y2%, x2%, c$)
    'bError% = FALSE
    'LOCATE 2, 2: PRINT "(" + STR$(x%) + "," + STR$(y%) + ") to (" + STR$(x2%) + "," + STR$(y2%) + ") of " + CHR$(34) + c$ + CHR$(34);
 
    i% = 0: steep% = 0: e% = 0
    IF (x2% - x%) > 0 THEN sx% = 1: ELSE sx% = -1
    dx% = ABS(x2% - x%)
    IF (y2% - y%) > 0 THEN sy% = 1: ELSE sy% = -1
    dy% = ABS(y2% - y%)
    IF (dy% > dx%) THEN
        steep% = 1
        SWAP x%, y%
        SWAP dx%, dy%
        SWAP sx%, sy%
    END IF
    e% = 2 * dy% - dx%
    FOR i% = 0 TO dx% - 1
        IF steep% = 1 THEN
            'PSET (y%, x%), c%:
            LOCATE y%, x%
            PRINT c$;
        ELSE
            'PSET (x%, y%), c%
            LOCATE x%, y%
            PRINT c$;
        END IF
 
        WHILE e% >= 0
            y% = y% + sy%: e% = e% - 2 * dx%
        WEND
        x% = x% + sx%: e% = e% + 2 * dy%
    NEXT
    'PSET (x2%, y2%), c%
    LOCATE x2%, y2%
    PRINT c$;
 
END SUB ' DrawTextLine
 

^^^
From: Multiple mice therad #1:
https://www.qb64.org/forum/index.php?topic=3348.msg127110#msg127110 (https://www.qb64.org/forum/index.php?topic=3348.msg127110#msg127110)

Multiple mice thread #2:
https://www.qb64.org/forum/index.php?topic=3695.0 (https://www.qb64.org/forum/index.php?topic=3695.0)

Title: Re: events and malloc in QB64?
Post by: madscijr on March 30, 2021, 02:56:14 pm

Quote from: SpriggsySpriggs on March 30, 2021, 02:45:06 pm

I hope this helps to answer some of the questions, at least

I am a fish out of water in the world of C and low-level Windows programming, so any information helps.
Thank you!

Title: Re: events and malloc in QB64?
Post by: SpriggsySpriggs on March 30, 2021, 03:05:16 pm

@madscijr I will do my best to allocate some time tonight to work on this a bit. If you want, you can join our discord server using the link on the forum home. I'm very active there and can answer your questions quickly.

Title: Re: events and malloc in QB64?
Post by: SpriggsySpriggs on March 31, 2021, 12:36:56 am

@madscijr Just so you know that I didn't forget you, here is proof that I'm looking into this:
[ This attachment cannot be displayed inline in 'Print Page' view ]

Note: This isn't to say I've gotten anything to work yet. I'm still just trying to recreate some functions and declarations.

Title: Re: events and malloc in QB64?
Post by: FellippeHeitor on March 31, 2021, 08:40:06 am

@bplus instead of in-house event-based programming - which is what InForm offers - it seems from context that madscijr is looking to handle OS events - likely with callback functions.

Title: Re: events and malloc in QB64?
Post by: SpriggsySpriggs on March 31, 2021, 08:43:35 am

@FellippeHeitor Exactly. I'm actually using callback code shared by Petr here: https://www.qb64.org/forum/index.php?topic=3217.msg124966#msg124966 (https://www.qb64.org/forum/index.php?topic=3217.msg124966#msg124966)

Title: Re: events and malloc in QB64?
Post by: madscijr on March 31, 2021, 08:44:01 am

Quote from: SpriggsySpriggs on March 31, 2021, 12:36:56 am

@madscijr Just so you know that I didn't forget you, here is proof that I'm looking into this:
Note: This isn't to say I've gotten anything to work yet. I'm still just trying to recreate some functions and declarations.

Great - much appreciated!

PS Sorry I wasn't able to join on the discord server (what is a discord server?), I'm often pretty busy after hours on weekdays, this QB stuff is mainly a lunchtime activity for me!

Title: Re: events and malloc in QB64?
Post by: FellippeHeitor on March 31, 2021, 08:52:22 am

Discord is a fancy chatroom. Registration required. http://discord.qb64.org

Title: Re: events and malloc in QB64?
Post by: madscijr on March 31, 2021, 08:54:39 am

Quote from: FellippeHeitor on March 31, 2021, 08:52:22 am

Discord is a fancy chatroom. Registration required. http://discord.qb64.org

Cool, thanks for cluing me in.

Title: Re: events and malloc in QB64?
Post by: madscijr on March 31, 2021, 08:58:23 am

PPS Down the road (assuming this ever ends up working) it would be cool to also get this working for Linux / macOS.

I'm not sure if there are commands in QB64 code that can auto-detect the OS, and conditionally use Windows / Linux / Mac versions of a library, or if we would just need to have separate versions of the library for each OS.
But the ManyMouse library seems to be cross-platform, with separate versions of code for

Windows (windows_wminput.c)
Linux (linux_evdev.c)
macOS (macosx_hidmanager.c, macosx_hidutilities.c)

and common files for all platforms

manymouse.c
manymouse.h

I just thought I would mention this to gauge how people approach making a cross-platform library in QB64...

Title: Re: events and malloc in QB64?
Post by: SpriggsySpriggs on March 31, 2021, 09:04:47 am

Quote from: madscijr on March 31, 2021, 08:58:23 am

I'm not sure if there are commands in QB64 code that can auto-detect the OS, and conditionally use Windows / Linux / Mac versions of a library, or if we would just need to have separate versions of the library for each OS.

There are! Check out this Wiki page: https://www.qb64.org/wiki/$IF (https://www.qb64.org/wiki/$IF)

Title: Re: events and malloc in QB64?
Post by: madscijr on March 31, 2021, 09:28:57 am

Quote from: SpriggsySpriggs on March 31, 2021, 09:04:47 am

There are! Check out this Wiki page: https://www.qb64.org/wiki/$IF (https://www.qb64.org/wiki/$IF)

Aha, yes, that's the stuff!
Thanks!
(Now we would just need someone who can understand Mac "C" code and Linux "C" code to help convert the respective modules! I'm not going to worry about this until later...)

Title: Re: events and malloc in QB64?
Post by: SpriggsySpriggs on March 31, 2021, 09:34:07 am

Quote from: madscijr on March 31, 2021, 09:28:57 am

(Now we would just need someone who can understand Mac "C" code and Linux "C" code to help convert the respective modules! I'm not going to worry about this until later...)

Well, I have written code that is multiplatform before which required me to convert C code for Linux and Mac to QB64. Not too much of a challenge. I'll give that a go if I can get some functionality in Windows first.

Title: Re: events and malloc in QB64?
Post by: SpriggsySpriggs on April 01, 2021, 09:05:54 am

@madscijr Well, it turns out that this software you want to recreate or use in QB64 requires SDL. Our older versions of QB64 use SDL. I'm trying now to find a way to do what you want without SDL. May prove difficult

Title: Re: events and malloc in QB64?
Post by: madscijr on April 01, 2021, 10:04:13 am

Quote from: SpriggsySpriggs on April 01, 2021, 09:05:54 am

@madscijr Well, it turns out that this software you want to recreate or use in QB64 requires SDL. Our older versions of QB64 use SDL. I'm trying now to find a way to do what you want without SDL. May prove difficult

No kidding... So THAT's how they're doing it cross-platform?
I saw stuff in there about the Raw Input API, though.
I think that's a standard Microsoft API included in all Windows versions from XP on.
With that, we shouldn't need SDL for the Windows version, right?

PS Here are the MS RawInput API docs:
https://docs.microsoft.com/en-us/windows/win32/inputdev/raw-input?redirectedfrom=MSDN (https://docs.microsoft.com/en-us/windows/win32/inputdev/raw-input?redirectedfrom=MSDN)

PPS and here is some sample code to use the RawInput API (yet more C code I can flounder around with and try to convert to QB64! yay!):
https://jstookey.com/multiple-mice-raw-input/ (https://jstookey.com/multiple-mice-raw-input/)

Title: Re: events and malloc in QB64?
Post by: SpriggsySpriggs on April 01, 2021, 11:29:25 am

@madscijr Exactly. I've been looking at some raw input examples online.

https://asawicki.info/news_1533_handling_multiple_mice_with_raw_input (https://asawicki.info/news_1533_handling_multiple_mice_with_raw_input)

Title: Re: events and malloc in QB64?
Post by: madscijr on April 01, 2021, 11:48:44 pm

Quote from: SpriggsySpriggs on April 01, 2021, 11:29:25 am

@madscijr Exactly. I've been looking at some raw input examples online.
https://asawicki.info/news_1533_handling_multiple_mice_with_raw_input (https://asawicki.info/news_1533_handling_multiple_mice_with_raw_input)

From my end, I think starting off simple is probably the best way to get off the ground, so I started off by figuring out the minimal example from
https://jstookey.com/multiple-mice-raw-input/ (https://jstookey.com/multiple-mice-raw-input/)

Hopefully tomorrow I'll get something working...

Code: C: [Select]

/**********************************************************************************************
FROM: https://jstookey.com/arcade/rawmouse/HelloRawInput.c
 
testmouse.c: A demonstration of how to use Rawinput to access multiple mice in Windows XP.
 
------------------  COMPILING WITH GCC ------------------------------
 
This program was compiled using MinGW/GCC
 
In order to recreate the compile environment:
 
  1) Install the "Win32 compile utilities" (MinGW/GCC) for Mame from http://www.mame.net/downmain.html
  2) From the command line, run "gcc HelloRawInput.c"
 
-------------------  COMPILING WITH MS VISUAL C++ --------------------
 
This example can also be compiled with Microsoft Visual C++ version 6, but first you need to download
        and install the Microsoft Platform SDK.  In order to access the Microsoft Platform SDK from VStudio, 
        I had to go to tools->options->directories and add the SDK's bin, include, lib, and src folders.
        In the same window, I had drag each of the SDK's folders to the top of the respective list
        to give those folders priority over the others.
 
        To create your project for Visual Studio (after you prepare VStudio to work with the MS
             Platform SDK), do the following:
 
        1) Open Visual C++ and start a new Win32 Application as a "blank project"
           (This is necessary because if you simply open the .c file in VStudio
           VStudio will assume it's a "console application" and it won't compile properly.)
        2) Copy the .c file into the new project's root folder
        3) In the left pane, click "File View" and left click "Source Files" and select
             "add files to folder" from the popup menu, and add your file.
        4) You're all set!  Press f5 to build the program.
 
**********************************************************************************************/
#define _WIN32_WINNT 0x0501   // Identify this as a Windows XP application.  This is necessary
                                                          //    so we can access rawinput
#include <stdio.h>
#include <conio.h>                      //  Provides getch()
#include <windows.h>            //  Provides rawinput
 
main()
{
        UINT nInputDevices;
 
        // 1st call to GetRawInputDeviceList: Pass NULL to get the size of the list.
        if (GetRawInputDeviceList(NULL, &nInputDevices, sizeof(RAWINPUTDEVICELIST)) != 0) return 0; 
        printf("Number of raw input devices: %i\n\n", nInputDevices);
 
        printf("Press any key...");
        getch();
 
        return 1;
}
 
 
/*
 
-------------------------------------------------------------------------------
What is GetRawInputDeviceList?
        UINT GetRawInputDeviceList(
          PRAWINPUTDEVICELIST pRawInputDeviceList,
          PUINT               puiNumDevices,
          UINT                cbSize
        );
 
-------------------------------------------------------------------------------
What is PRAWINPUTDEVICELIST?
        PRAWINPUTDEVICELIST:
        typedef struct tagRAWINPUTDEVICELIST {
          HANDLE hDevice;
          DWORD  dwType;
        } RAWINPUTDEVICELIST, *PRAWINPUTDEVICELIST;
 
-------------------------------------------------------------------------------
What is getch?
        getch() is a nonstandard function and is present in conio.h header file 
        which is mostly used by MS-DOS compilers like Turbo C. It is not part of 
        the C standard library or ISO C, nor is it defined by POSIX.
        Like these functions, getch() also reads a single character from the 
        keyboard. But it does not use any buffer, so the entered character is 
        immediately returned without waiting for the enter key.
        Syntax: int getch(void);
        Parameters: This method does not accept any parameters.
        Return value: This method returns the ASCII value of the key pressed.
        
*/
 

Title: Re: events and malloc in QB64?
Post by: madscijr on April 02, 2021, 05:09:50 pm

Quote from: madscijr on April 01, 2021, 11:48:44 pm

From my end, I think starting off simple is probably the best way to get off the ground, so I started off by figuring out the minimal example from
https://jstookey.com/multiple-mice-raw-input/ (https://jstookey.com/multiple-mice-raw-input/)
Hopefully tomorrow I'll get something working...

I tried to convert the C code to QB64, using the QB64 equivalents of the C types that SpriggsySpriggs shared, and googling.
I'm currently stuck on line 55 of the below code, when I run the QB64 IDE says "Expected &H... or &O...".
When I try changing & to &H or &O, the QB64 IDE says a ")" is missing. No idea how to get this working!
Any help appreciated...

Code: QB64: [Select]

' ****************************************************************************************************************************************************************
' testmouse.c: A demonstration of how to use Rawinput to access multiple mice in Windows XP.
' https://jstookey.com/arcade/rawmouse/HelloRawInput.c
' ****************************************************************************************************************************************************************
 
' #define _WIN32_WINNT 0x0501   // Identify this as a Windows XP application.
'                               // This is necessary so we can access rawinput
' #include <stdio.h>            
' #include <conio.h>            //  Provides getch()
' #include <windows.h>          //  Provides rawinput
 
' =============================================================================
' GLOBAL DECLARATIONS a$=string, i%=integer, L&=long, s!=single, d#=double
 
' -----------------------------------------------------------------------------
' BOOLEAN CONSTANTS
CONST FALSE = 0
CONST TRUE = NOT FALSE
 
' -----------------------------------------------------------------------------
' USER DEFINED TYPES
 
' What is PRAWINPUTDEVICELIST?
'     PRAWINPUTDEVICELIST:
'     typedef struct tagRAWINPUTDEVICELIST {
'       HANDLE hDevice;
'       DWORD  dwType;
'     } RAWINPUTDEVICELIST, *PRAWINPUTDEVICELIST;
 
TYPE RAWINPUTDEVICELIST
    hDevice AS _OFFSET ' a handle will always be _OFFSET
    dwType AS LONG ' DWORD corresponds to LONG
END TYPE
 
' -----------------------------------------------------------------------------
' API FUNCTIONS
 
' What is GetRawInputDeviceList?
'     UINT GetRawInputDeviceList(
'       PRAWINPUTDEVICELIST pRawInputDeviceList,
'       PUINT               puiNumDevices,        <---- what is a aPUINT?
'       UINT                cbSize
'     );
 
' what is a aPUINT? According to 
'     WIN32 API Data Types
'     https://www.csie.ntu.edu.tw/~r92094/c++/w32api_data_type.html
' PUINT Pointer to a UINT.
' Q: What QB64 type is equivalent to a pointer? 
' A: is it _OFFSET ?
 
DECLARE DYNAMIC LIBRARY "kernel32"
    ' COMPILER ERROR HERE: Expected &H... or &O...
    ' THEN WHEN I TRY CHANGING & TO &H OR &O, COMPILER SAYS MISSING )
    FUNCTION GetRawInputDeviceList (pRawInputDeviceList AS RAWINPUTDEVICELIST, puiNumDevices AS _OFFSET, cbSize AS _UNSIGNED LONG)&
END DECLARE
 
' =============================================================================
' GLOBAL VARIABLES
DIM ProgramPath$
DIM ProgramName$
 
' =============================================================================
' INITIALIZE
ProgramName$ = MID$(COMMAND$(0), _INSTRREV(COMMAND$(0), "\") + 1)
ProgramPath$ = LEFT$(COMMAND$(0), _INSTRREV(COMMAND$(0), "\"))
 
' =============================================================================
' START
main ProgramName$
 
' =============================================================================
' FINISH
SYSTEM ' return control to the operating system
PRINT ProgramName$ + " finished."
END
 
' /////////////////////////////////////////////////////////////////////////////
 
SUB main
        PRINT "MinimalRawInputTest% RETURNS: " + cstr$( MinimalRawInputTest%() )
END SUB ' main
 
FUNCTION MinimalRawInputTest%
    DIM iResult%
        'UINT nInputDevices;
        DIM nInputDevices AS _UNSIGNED LONG
        DIM MEM AS _MEM
        
    ' 1st call to GetRawInputDeviceList: Pass NULL to get the size of the list.
    'if (GetRawInputDeviceList(NULL, &nInputDevices, sizeof(RAWINPUTDEVICELIST)) != 0) return 0; 
        
        ' **********
        ' UNKNOWNS:
        ' Q1: how do you pass NULL in QB64? 
        ' A1: ?
        
        ' Q2: what is &nInputDevices vs nInputDevices and what is the QB64 equivalent?
        ' A2: is it the pointer to the variable? in QB64, The _OFFSET function returns the memory offset of/within a given variable.
        
        ' Q3: what is the QB64 equivalent of sizeof?
        ' A3: maybe _MEM and _MEM.SIZE ?
        
        MEM = _MEM(RAWINPUTDEVICELIST)
        
        'IF (GetRawInputDeviceList(NULL, _OFFSET(nInputDevices), sizeof(RAWINPUTDEVICELIST)) <> 0) THEN
        IF (GetRawInputDeviceList(NULL, _OFFSET(nInputDevices), MEM.SIZE) <> 0) THEN
                iResult% = 0
    ELSE
                PRINT "Number of raw input devices: " + cstr$(nInputDevices)
                PRINT "Press any key..."
                SLEEP ' SLEEP without an argument waits until a keypress.)
                iResult% = 1
        END IF
    
        ' RETURN RESULT (ONE EXIT POINT!)
        MinimalRawInputTest% = iResult%
END FUNCTION ' MinimalRawInputTest%
 
' /////////////////////////////////////////////////////////////////////////////
' Equivalent to vbscript / VBA / VB6 cstr
 
FUNCTION cstr$ (myValue)
    'cstr$ = LTRIM$(RTRIM$(STR$(myValue)))
    cstr$ = _TRIM$(STR$(myValue))
END FUNCTION ' cstr$
 
' /////////////////////////////////////////////////////////////////////////////
' Equivalent to getch
 
' -----------------------------------------------------------------------------
' What is getch?
'     getch() is a nonstandard function and is present in conio.h header file 
'     which is mostly used by MS-DOS compilers like Turbo C. It is not part of 
'     the C standard library or ISO C, nor is it defined by POSIX.
'     Like these functions, getch() also reads a single character from the 
'     keyboard. But it does not use any buffer, so the entered character is 
'     immediately returned without waiting for the enter key.
'     Syntax: int getch(void);
'     Parameters: This method does not accept any parameters.
'     Return value: This method returns the ASCII value of the key pressed.
 
' -----------------------------------------------------------------------------
' QB64 alternate to getch
' 
' SLEEP ' SLEEP without an argument waits until a keypress.)
' 
' or
' 
' DO
'       x = _KEYHIT
'       IF x THEN
'               EXIT DO
'       END IF
' LOOP 
 

Title: Re: events and malloc in QB64?
Post by: SMcNeill on April 02, 2021, 06:35:14 pm

FUNCTION GetRawInputDeviceList& (pRawInputDeviceList AS RAWINPUTDEVICELIST, puiNumDevices AS _OFFSET, cbSize AS _UNSIGNED LONG)

& *after* the function name.

Title: Re: events and malloc in QB64?
Post by: madscijr on April 03, 2021, 11:13:42 am

Quote from: SMcNeill on April 02, 2021, 06:35:14 pm

FUNCTION GetRawInputDeviceList& (pRawInputDeviceList AS RAWINPUTDEVICELIST, puiNumDevices AS _OFFSET, cbSize AS _UNSIGNED LONG)

& *after* the function name.

Aha... DUH! LoL
Thank you.

Any idea how you would send a NULL value as one of the parameters?

Title: Re: events and malloc in QB64?
Post by: madscijr on April 05, 2021, 04:23:57 pm

I returned to this and made some minor changes, and am now stuck on this error:

Code: [Select]

Cannot convert _OFFSET type to other types on line 118.
Caused by (or after): IF ( GETRAWINPUTDEVICELIST ( MYLIST , MYADDR , MEM . SIZE ) <> 0 ) THEN

This is probably outside the scope of this thread, so I'll start a new one for this, related to type "_OFFSET".

Text Only | Text with Attachments

QB64.org Forum

Active Forums => QB64 Discussion => Topic started by: madscijr on March 30, 2021, 12:30:04 pm