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
- CedricKiefer December 2013
- Piranesi January 2014
- REAS November 2013
strokeWeight are scaled in Processing 2.1
As you can see from the picture above, the box after the scale() operation has a scaled thickness. This never happened in previous versions as far as I can remember. Also, it does not apply to points. Anyone else experiencing this?
It happens both in Mac iOS 10.7.5 and Windows 7.
I have managed to maintain thicknesses by inverse-scaling them, but I hope display thickness will be scale-independent again in the next release. :)
Tagged:
Comments
It's intended for stroke weight to scale. As you discovered, the inverse technique is the way around: strokeWeight(1/scalar)
Good to know, just took me a while to figure it out looking at some of my old sketches. I most cases it feels like its complicating things. At least for me... having to change strokeWeight for every element. I understand the intention though. Might be good to be able to turn it on and off by setting a scaleMode() or something that let you decide if scaling is applied to visual styles like the strokeWeight as well...
It does apply to points, and is quite a nuisance.
I'm using Processing 2.1 and the Default Renderer to plot some graphs, using substantially different scaling factors in x and y.
Here is the matrix 054.2857 000.0000 410.0000 000.0000 -000.1667 700.0000
Under these conditions point() is plotting long horizontal lines, not points. There is no way of inverse scaling the strokeWeight to correct this.
A solution would be for strokeWeight to take into account the matrix applying at the time it is called, and apply the appropriate inverses automatically. At present it seems only to deliver the required thickness in pixels when a unit matrix is in force.