Jump to content
You must now use your email address to sign in [click for more info] ×

Chris B

Staff
  • Posts

    11,697
  • Joined

  • Last visited

Everything posted by Chris B

  1. I tried this intermittently yesterday however, I was not able to reproduce on Windows. I was using a similar recipe that I was using on macOS (dragging the window from screen to screen, min/maxing, etc.) I'm going to try today on a different setup and see what happens.
  2. I think just a brief run-through of your folder structure and the process of opening a file from its location will help. I can work on doing the other bits.
  3. @anto and @TomJr I believe I have reproduced this issue. I have to trigger it in a very specific way though. I also managed to get the new document into a state where I cannot even properly close it but I certainly get the display issue where the new canvas does not fully display and I get perhaps 1/4 of it showing white and the rest is black. I will do further poking and can finally get this logged with the developers.
  4. So I tried this when Nopemann provided a recipe - I could not reproduce it. I've just tried again this morning for a good 30 mins doing all sorts of combinations of loading, saving etc. from iCloud and I still cannot reproduce. I think a video recording of your workflow where you create a file, save it, attempt to open it and get the message might give us some clues. Other than that, I don't know what else I can suggest, sadly. It's certainly not from lack of trying.
  5. Have you raised this before in here? https://forum.affinity.serif.com/index.php?/forum/122-feedback-for-the-affinity-v2-suite-of-products/ I do think it's a good idea but like I said, just a bit beyond the current scope—that doesn't mean it would never be considered. Cheers
  6. @dcarvalho84 as the Serif Info Bot suggests, we believe we have successfully fixed this issue. We can see a clear difference between the previous betas that this was reported against and the internal 2165 build. I am really hoping that it has greatly improved for you as well. Again, thanks for your patience.
  7. Hey FDK, This change will not do what you are asking. It's simply to change the background colour to make assets with images more visible depending on their attribute. It sounds like your process is quite niche and beyond the scope of what the Asset Panel was intended for.
  8. Extending on what Dan said, if you move the app (or another app) around but click the same area on the screen, is that also a dead zone?
  9. Hi Sunshadow, Unfortunately, I have been unable to reproduce the issue. Any chance you could provide a screen recording? TinyTake by MangoApps-28-11-2023-07-20-12.mp4 Do you have another display connected? If so, does disconnecting it resolve the issue?
  10. I believe that was the calendar project and not the graphic on the jumpers. I just wanted a few examples but hopefully we can get this sorted. Thank you so much for your testing and your patience.
  11. Hey Sunshadow, I can check this when I get home. I've got a 49" 5120 x 1440p monitor and a 34" 3440 x 1440p monitor available to me so hopefully we can reproduce this and get it logged with the developers. I'll reply tonight once I've checked.
  12. Thanks for the video @dcarvalho84 Would you mind sharing that file (or a similar one) with the developers? I've made a private dropbox for them to access the file if you're happy to upload it here: https://www.dropbox.com/request/DGVkrVhFD4dUARpcQY4i Nobody outside of the Development team would be able to access this and the file(s) will be removed once we have investigated.
  13. Hey tzvi20, The Styles Panel is indeed wrong here. It should be Delete (as it is on macOS) so that's the bug. I'll get this logged. Thank you.
  14. Morning. I've just installed a free trial of the DxO FilmPack 7 and it seems to be working for me. Can you please review the recording and let me know if I'm doing something different please? DxO FilmPack 7.mp4 I am running a 2.3.0.2157 beta of Photo.
  15. Hey dcarvalho84, Sorry this hasn't been fixed yet. This would not be an easy fix as it would likely require a complete overhaul of the rendering engine. The issue is logged with the developers for their consideration. You will be notified when a fix is made and tested by QA via the Serif Info Bot. I would, for now, set the renderer to either Low Quality (Fastest) or High Quality (Slowest) until the developers get around to addressing this. For what it's worth, I always set my setting to High Quality as it gives the best user experience and if you've got a half-decent machine, you will likely never notice any extreme issues. May I ask what kind of performance hit you see?
  16. Hi anto, that looks like the same thing as in this thread. As you know, we've not been able to reproduce it
  17. Hi anto, Not sure I follow you exactly. Drag and drop from where? Finder? Stock Panel? Dragging an image to the UI will open a new window. Dragging an image to the canvas area will drop it on the canvas.
  18. Apologies this is taking so long. I have updated the bug report to remind the developers this is still an ongoing issue.
  19. Hey Jens Krebs, I do seem to get a warning. To clarify, are you setting the shortcut to Settings: Shortcuts: Publisher > Window > Text Styles? Is this macOS or Windows?
  20. Hey melonbird, Development has asked me to find out if you still get the crash if instead of Edit > Fill > Inpaint you go to Edit > Inpaint? We are struggling to find the cause of the crash report. Is there any chance you could share a document that you typically work on? I have made you a private Dropbox folder that only development and QA can see. Thanks! https://www.dropbox.com/request/6BanmT5FizhnpCxuAeQ8
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.