If I navigate to an old project using win explorer, then click on the *.ino file, the IDE does not launch that file but the last project that was opened.
I could not find this topic in the minions, so I don't know if it's new.
Hello @iggnator. Which version of the Arduino IDE are you using?
This is 2.0.0 rc2.
I was always able to launch a sketch this way with the 1.x.x version, but just verified with 1.8.16.
I just tried this with the nightly version, but it did not launch the nightly version using the Open-with menu of win explorer, (after navigating to using it), it launched 2.0.0 rc2 again, and with the last used sketch being opened instead of the one I selected.
OK, this is a known deficiency in Arduino IDE 2.x, tracked by the developers here:
There is currently no mechanism for specifying a sketch to open from the command line when starting the IDE, so when you open a sketch file, it just starts the Arduino IDE as it would have if you had ran the IDE application itself.
The developer did do some work on it, but it seems it is unfinished:
For now, you will need to use File > Open, File > Sketchbook, etc. in the IDE itself when you need to open sketches.
You are welcome to change the .ino file association to point back to your classic Arduino IDE installation if you prefer that they do open in an IDE.
Thank you, I like using the new IDE. As a retired coder, I had difficulties in users reporting bugs. I even put notices in my code to "Report all bugs". Too big an organization, and if they found a work around or it was unimportant, they just ignored bugs.
I know the workaround......
I think there is a similar problem for Arduino. Many of the users are new to this field of endeavor. They might not be sure whether the problem they are experiencing is caused by something they did wrong or a bug on Arduino's end. If they do determine it is a bug, they might not know where to report it. If they find the correct repository on GitHub, they might not have an existing GitHub account.
I have found many useful reports here on the forum over the years, most of which were not formulated as a report, but rather revealed over the course of the discussions. I always try to act as a "bridge" of sorts between the user community and the developers.
I do think that high quality bug reports and feature requests are a very valuable contribution to an open source project. Beta testing and reporting bugs offers another opportunity to participate in the Arduino project for those who might not be in a position to directly contribute to the code itself.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.