Hello!

Your library/framework is obviously amazing. I believe you are accidentally not exporting the controls folder right now with your NPM package.

It means that actually the only way to access commonly used library members such as TrackballControls is like so: vasturiano/three-render-objects#5

Perhaps intentional but wanted to point out just in case.

(he

Documentation Is:

• Missing or needed
• Confusing
• Not Sure?

Please Explain in Detail...

I needed to produce a number of charts with a consistent yAxes logarithmic scale so that users can compare between charts.

I tried setting the same yAxes config settings for each chart:

beginAtZero: true
ticks

Version

Last doc

Description

The documentation doesn't provide the good description for gameobject.body.drag.

URL: https://photonstorm.github.io/phaser3-docs/Phaser.Physics.Arcade.Body.html#useDamping__anchor

Example Test Code

gameobject.body.drag = 0.5; // doesn't work because `drag` is Vector2.
gameobject.body.setDrag(0.5); // works

Additional Infor

I think it's unexpected. I have to use Detector.canCollide on my own when I want to use Query.collides. I think it should be changed or at least mention in documentation.

This would be a nice little feature to have, Excel users are using this a lot.

The new (v5.8) Vega heatmap and isocontour transform requires "raster grids (matrices)"
input data format as seen in these Vega example data files:

 https://github.com/vega/vega/blob/master/docs/data/volcano.json
 https://github.com/vega/vega/blob/master/docs/data/annual-precip.json

It would be helpful to add explanation of this data format in the documentation:

  https://v

I was wondering if there is a comprehensive installation guide for people new to using code on GitHub. If not, could you walk me through the installation process step-by-step? I am practicing my technical writing skills by editing Readme documents and wanted to write a longer, more detailed Readme for Piskel. I would be happy to contribute my edits to the master project if you like them. I'm sure

I found the installation guidance of heatmap.js in different context, it's very useful because I am currently using Node.js as my developing back-end context, but the usage in how to include them into these kinds of context is rare. Because CommonJS/Node.js need to load variable from package, and heatmap.js' plugin has specific instance creation approach, I think it's good to include these content

Some people seem to read https://html.spec.whatwg.org/multipage/forms.html#dom-form-nameditem as implying that a new nodelist should be returned each time when there are multiple matching elements. That's not the intent, I assume, and it might be worth clarifying the spec to make it clear.

All browsers I tested (Firefox, Chrome, Safari) return the same nodelist on multiple accesses.