I want to start looking at Ver 2.0 but don't want to lose 1.8.19. Will 2.0 overwrite 1.8.19?
Download the zip version and unzip it in a folder of your choice and run it from there
Your topic has been moved to the dedicated IDE2.0 section of the forum. @ptillisch might be able to answer the actual question.
I use the same approach as @UKHeliBob.
Hi @richesonp installing Arduino IDE 2.x will not have any effect on the Arduino IDE 1.8.19 installation. They are treated as two separate applications so the installer makes a separate installation instead of the usual behavior of updating the existing installation.
If you ever want to have two versions of Arduino IDE 2.x installed at the same time, then you can use the "Windows ZIP file" version offered on the "Software" page as already recommended above.
I currently have 42 different versions of Arduino IDE 1.x and 203 versions of Arduino IDE 2.x on my Windows computer!
I bow to you, brave heart.
1 Like
So, why so many?
'tis the job...
One of the things I try to do while investigating a bug is a "bisection", where I determine the exact point in the development history the bug was introduced at. Typically the best way to do a bisection is using the git bisect command in the project's Git repository (which contains the entire revision history of the project). I also use that technique, but there are some problems with using the Git repository for this sort of work:
- The IDE has significantly worse performance when running from source (because you miss the optimizations done via the build process). The IDE's bugs are often timing sensitive, and those timings are significantly different when running from source, which can mean that you get different results while running from source than from a production build.
- The production build takes a long time. Starting from source is faster, but still slow. So having a pre-built IDE on hand is the quickest way to test a given version (and I must test many versions during this process).
I also regularly must check whether a bug reported some time ago still occurs, or whether it was fixed incidentally by some of the development done since that time. In order to do that, I must first verify that I can reproduce the bug in the first place. So it is useful to be able to start up the exact version that was in use at the time of the report. Since we request that the latest nightly build be checked when submitting a formal bug report, this means that just having each of the releases on hand is not sufficient. As with the bisection, I can always run or build any version of the IDE from source, but this takes more time. I also try to run a bisection to see which change actually fixed the issue.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.