I just brought up Arduino 2 RC7. The first thing it told me was there was a newer release, RC8, did I want to download it? Yes. So it downloaded a second copy of RC7,
RC7 has a serious bug. I cannot drag it up onto my second screen. When it hits the top of the lower screen, it stops. This is clearly an error. No other app exhibits this behavior. I am running MacOS Mojave (10.14.6). The image attached shows my workstation setup. This message is being typed in the upper window and you can see the RC7 IDE on the laptop itself.
You must support multiple monitors in all configurations. If there is code in there to stop it from being dragged off the top of the screen, remove it, because it is flat-out wrong. The only time this would be valid is in a single-monitor environment, so you could check for that as a special case and use the code only if it is discovered that there is only one monitor. In Windows, I can ask for the coordinates of the virtual monitors, and if you feel you have to limit motion, you must use the virtual screen coordinates, which can have y going negative.
EDIT: I just verified that it works correctly if the second monitor is left, right, or below the main monitor, but fails if it is above.
And I did not forget to upload the image; I uploaded it successfully, but it did hot appear (I used the upload option in the menu). So I uploaded it a second time, and again, the upload completed successfully, but the image did not appear.
No, I did not. The upload worked, but the picture did not appear. I used the upload option in the menu. I have no idea why it told me it was 100% successful and then misplaced the image. It failed a second time.
I just tried it on Windows (I don't have access to a macOS machine) and it installed 2.0.0-rc8 as expected.
What exactly did you observe that makes you think it downloaded a second copy of 2.0.0-rc7?
Unfortunately, I don't have access to the hardware that would be needed for me to reproduce this bug and submit a report on your behalf. So the best way forward will be for you to report the issue to the developers directly.
I did already check to see whether there was an existing report of this issue in the tracker and there is none, so you can skip the usual duplicate search task this time if you like.
I will do a test of attaching a random image to see whether it is working:
