art

Hi 👋👋👋

We are using this issue to focus on documentation! Documentation is essential for new learners and experienced programmers alike. It helps make our community inclusive by extending a friendly hand to those that are less familiar with p5.js. It also helps us find the bugs and issues with the code itself, because we test and try things out as we document.

[There are several ways to con

There are some elements on the documentation page for midi_mode that are not rendered correctly.

The fix would involve editing some of the lines of the following code section:
https://github.com/sonic-pi-net/sonic-pi/blob/81291453cddd52035817dfe2cb

I'm currently using LIEF in a project that uses mypy for Python type-checking. We use an ignore directive on our import lief #type:ignore statements, as type stubs for lief are not currently available. I've been considering generating and contributing stubs to https://github.com/python/typeshed, so that we can remove the ignores, and maybe others will find them useful. H

I have such strange saves (duplicates) - ora~, jpg~, png~. I can rename them and they will work normally.
Save as - fine save without duplicates.
Export - fine save without duplicates.
Only 'Save' have such problem.
Krita have same problem, only 'File - Save'. I thought that i have some problems with my computer, but Paint.NET saves normally without duplicates. GIMP - i dont know where are there '

In the viewport, the top right number inputs display the current precise values of the ongoing zoom/rotation, but they should show the snapped value which is what the viewport is rendering.

It doesn't look like there's any straightforward way to input exact values for plugin sliders in the inspector. I can type a precise tempo by clicking on the tempo value slider at the bottom of the screen, but this behaviour doesn't seem to be replicated for sliders in the inspector. If I change, say, the output gain of a plugin from 1 to something other than one it's effectively impossible for me