New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Touch and multi-touch support discussion #3

Open
pronvit opened this Issue May 20, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@pronvit

pronvit commented May 20, 2018

Comfortable touch operation is the first priority for miRack and obviously provides experience much closer to real hardware than mouse operation. This particular thread is for discussion of touch/multi-touch operation, originated from a similar issue in VCVRack repo by @alectron.

miRack is primarily supposed to be used on ARM boards likely with a touch screen, but can be used on desktops as well. Due to inability and unwilingness of the VCVRack author to work on touch support, I may implement it in miRack for desktops as well if there’s a demand.

Anyway, the suggestions from the original thread that are going to be implemented first are

  • larger hit zones for controls and ports. This is a simple change as long as larger zones of different controls don’t intersect.
  • module locking, so that accidentially dragging a module background doesn’t move the module. On touch screens this will probably be the default mode, with touch and hold to move modules.

Multi-touch is the next step once my multi-touch screen arrives and I learn how to work with multi-touch devices on Linux.

pronvit added a commit that referenced this issue May 21, 2018

Merge branch 'touch' for #3
* touch:
  touch and hold to move modules when the're locked
  touch support: option to enlarge hit boxes for small controls, option to lock module positions
  just in case
@alectron

This comment has been minimized.

alectron commented Jun 1, 2018

Hello @pronvit ,
since this has tick-boxes now - does this mean you have "larger hit zones for controls and ports" as well as "module locking" working ?
And if so - is there a way to use this with the official VCV Rack as well (as I am running on standard windows/PC desktop & laptops and not tinker/pi boards) ? Cheers.

@pronvit

This comment has been minimized.

pronvit commented Jun 4, 2018

Yes, it's done. I think you should be able to apply this patch to VCV code too if you're able/willing to compile yourself. I don't see another way as even if I eventually make my fork available for Windows, closed-source plugins won't work with it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment