Author Topic: new input devices: what do we?  (Read 3907 times)

0 Members and 1 Guest are viewing this topic.

Offline TempodiBasic

  • Forum Resident
  • Posts: 1792
    • View Profile
new input devices: what do we?
« on: August 20, 2020, 07:40:01 am »
Hi guys
I'm using a netbook that has like pad the ability to work like touchpad getting also the input with more than one finger .
This issue can be extended to the notebooks 2 in 1 that have the screen like touchscreen...
for these new devices of input what can we  use to manage the news?
In other words how can  we  to manage an input with two finger on these new pads of notebook (like we do on Smartphone)? And how  can we to manage the touchscreen when it is in the machine?

Thanks to read and for feedbacks
Programming isn't difficult, only it's  consuming time and coffee

FellippeHeitor

  • Guest
Re: new input devices: what do we?
« Reply #1 on: August 20, 2020, 09:03:36 am »
Run this code from the wiki:

Code: QB64: [Select]
  1. devices = _DEVICES  'MUST be read in order for other 2 device functions to work!
  2. PRINT "Number of input devices found ="; devices
  3. FOR i = 1 TO devices
  4.   PRINT "Buttons:"; _LASTBUTTON(i)
  5. NEXT  

If that displays your extra input device, you will use _DEVICEINPUT to read from it. If it doesn't show up in this list, you won't be able to read it without using some external library.

Let us know.

Offline johnno56

  • Forum Resident
  • Posts: 1270
  • Live long and prosper.
    • View Profile
Re: new input devices: what do we?
« Reply #2 on: August 20, 2020, 10:00:50 am »
I tried that on my machine... Curious... I didn't think my keyboard was so big... lol

  [ You are not allowed to view this attachment ]  
Logic is the beginning of wisdom.

FellippeHeitor

  • Guest
Re: new input devices: what do we?
« Reply #3 on: August 20, 2020, 10:11:13 am »

Offline TempodiBasic

  • Forum Resident
  • Posts: 1792
    • View Profile
Re: new input devices: what do we?
« Reply #4 on: August 21, 2020, 10:44:12 am »
@johnno56
but have you  made the test on a notebook with pad?

@FellippeHeitor
yes I can say you that
1. no different input device has been detected by snippet on my Aspire One netbook with pad_two_fingers_touch
Quote
[MOUSE][BUTTONS][AXIS][WHEEL]
button 3

2. the same result I have got  runing the snippet on my notebook Toshiba i3  with a classical pad with 2 buttons for mouse
But in this case the result shows no axis no wheel and 3 buttons... the left the right and the pad?


3. It is a pity that there is no QB64 for Android because I should be able to test the snippet into Android of Acer One. It is possible that  the different OS (Android in this case) can use all the functionality of the pad twofingertouch!

4. I'll watch into the web to find a DLL that manage this kind of touchpad and the screentouch.

Thanks for feedback
Programming isn't difficult, only it's  consuming time and coffee

Offline johnno56

  • Forum Resident
  • Posts: 1270
  • Live long and prosper.
    • View Profile
Re: new input devices: what do we?
« Reply #5 on: August 21, 2020, 11:18:16 am »
Sorry. Desktop only. No notebook.
Logic is the beginning of wisdom.

Offline TempodiBasic

  • Forum Resident
  • Posts: 1792
    • View Profile
Re: new input devices: what do we?
« Reply #6 on: August 21, 2020, 02:26:50 pm »
for now I find this article that seems very interesting about Windows  & touchpad & 2 finger scrolling
https://www.rlvision.com/blog/how-to-enable-or-improve-two-finger-scrolling-on-your-windows-laptop/
at a first glance it seems that the issue stands among hardware of touchpad, managing the drivers of touchpad (here in C/C++ or with inline ASM claimed by a group of coders you can front the issue) and Windows' conception of the use of touchpad.

Someone that knows well Windows' API could show a path already done.

Thanks  to read and feedbacks
Programming isn't difficult, only it's  consuming time and coffee