

The affinity thumbnail is the third past the folder in this case, and it wont budge when the app icon is clicked - all other apps shown behave the intended way, restoring on app icon click. I made a quick comparison montage of other related and non-related apps showing how a minimized screen should act on Mac OS when the app icon is clicked. No other app on Mac OS behaves like this when the app is minimized. If this is not a bug, it really feels like one. You should also be able to do that by right-clicking on the Dock icon & choosing the document's name in the popup. In V2, you can then open the Windows menu where you should see the minimized document listed so you can make its window reappear by choosing it. Try dragging out one of the Studio panels onto the desktop, say the Layers panel, & you should see it reappear whenever you click on the app's Dock icon, so you know the app has the focus. When you minimize the main app window, it is just hidden, so unless you have any floating Studio panels all you will see when you click on its Dock icon is that the Mac menu bar shows that app has the focus, so its menu items are displayed. If I understand what you mean correctly, I don't think it is a bug. It's made a huge difference, and we're very much looking forward to working with you all on the next beta! I want to take this opportunity to thank you all so much for being so actively involved with the testing of 2.1 - along with all the new features and improvements we have got through a huge number of fixes, and that's only been possible with having so many of you putting it through it's paces.

is in sync with the release build (when 2.1 is made public) it's up to you if you want to continue to report any bugs in the beta forums or the main bug reporting forums. At that point you will be able to update the beta versions you currently have installed for that latest update to test.ĭuring the period that 2.

That will remain the case until we begin a fresh beta which will either be a patch to 2.1 if we feel it's needed, or hopefully moving straight to the first beta of 2.2. We will therefore now have a period where the latest beta version is the same as the release version. An update to the beta has just been made available which we are expecting to be the build we release publicly very soon! This means you can update your beta version to be the same code as what we will be our initial public release of 2.1.
