I raised an issue about a fault the Arduino Documentation and a moderator has moved it into the discussion section of a third party web site. Without any explanation as to why this was done.
Am I to take it that Arduino do not give a flying fig about there own documentation? That is what it looks like to me.
The documentations riddled with errors but apparently you don't want to know. Is it not worth trying to help anymore?
You created the issue in the issue tracker of the arduino/ArduinoCore-renesas repository. That repository contains the source code of the "Arduino UNO R4 Boards" platform. But your issue is not about the source code of the "Arduino UNO R4 Boards" platform. It is about the contents of this documentation page:
Issues must be submitted to the appropriate issue tracker in order to allow the task of resolving them to be effectively tracked. That means that if you want to report a problem with the content of a documentation page, you should submit that report to the repository where the content is developed. In this case that is the arduino/docs-content repository.
All that happened was that I transferred your issue from the inappropriate tracker you submitted it to (where only the platform developers would see it) over to the appropriate tracker where the people who maintain the documentation content will see it.
Not so. It was transferred from the issue tracker of one of Arduino's official repositories to the issue tracker of another one of Arduino's official repositories.
I recommend that in the future you take some time to carefully look instead of immediately jumping to making unfair and irresponsible accusations.
If anything, the fact that your issue report was triaged within less than an hour (on a weekend no less) by an Arduino employee should show that we do in fact "give a flying fig".
Did you bother to click on that link? If you did, you would see that GitHub automatically redirects URLs for transferred issues.
So if I have my logic backwards why did it not work when I tried it the other way round?
This is a UNO R4 I am working with. The UNO R3 can only support the MIDI library by the use of an intermediate helper device like hairless. So it makes sense, at least to me, to see if the same technique would work on the UNO R4. It worked on the Minima but not on the WIFI. So I set out to find why. And I succeeded in finding a solution that would work. And then I got all these comments about how I had it all wrong. But it actually worked, whit the broken shambles that is the current state of the U4 software. Look at other posts and beginners are still breaking there U4 boards and thinking they are permanently bricked.
I am very interested in MIDI and the MIDI library is the go to thing that beginners are drawn to, so I wanted to look at the examples needed to get an R3 to work and see if it could work on the R4.
I even wrote a whole book about using MIDI and sound on an R3. So I am not a beginner in these matters, but you treatment like I was.
Thanks @ptillisch for all of the stuff you do, including the triage of issues, PRs and forum posts, most every day of the week!
I am used to having some of my issues moved from one Arduino github database to another. Although more often in my case from the IDE2 to the CLI.
@Grumpy_Mike as was already mentioned, the original issue pointers will track to the new location.
I am guessing you probably already know this, but will mention it for others, who may not know this. When I am not sure of which issues, I still have pending and against which github project.
I typically then open up the github dashboard: GitHub
Then click on the three horizontal bar button:
and click on the issues menu item and other times the Pull Requests menu item, and it brings you to the page: Issues - Created (github.com)
