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
- GoToLoop March 2016
Mouse handling with matrix transformations
I'm looking to create a menu with different clickable buttons that will float on the right side of my window, sliding around nicely when it's resized.
Right now, I'm accomplishing this with a transformation matrix called before drawing all the buttons. However, this breaks all my mouse handling (as the buttons now don't know where they are located on the screen). What is the "right" way to deal with this? Should I just be updating each button's location internally every time the window is resized? Or is there some way to apply an inverse matrix transform to the mouse coordinates before passing them?
Tagged:
Answers
https://forum.Processing.org/two/discussions/tagged?Tag=screenx()