Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- BradSiemens December 2017
- GoToLoop December 2017
How do I get a less sensitive drag angle?
I'm using the difference between pmouseX/Y and mouseX/Y to determine the initial drag angle. I'm getting a lot of false drag angles because of a high(ish) frame rate (60fps) and the vagaries of mousing (?). Any idea how I can make it more reliable?
Tagged:
Answers
I've got this online example which uses pmouseX + mouseMoved():
http://Bl.ocks.org/GoSubRoutine/a117ecb16a8b0f939a190f87d3a13267
However, it also uses noLoop(). And when it's commented out, the 3D cube stops working. :-S
I solved this by increasing the interval between recording the mouse position and the dragging threshold. Seems kind of obvious now... oops!
Sorry GoToLoop, I didn't see your response before I commented. Thanks for taking the time!