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

transitdiagrams

Members
  • Posts

    405
  • Joined

  • Last visited

Posts posted by transitdiagrams

  1. 4 hours ago, Bit Disappointed said:

    Welcoming Gravit to the Corel "family"

    https://medium.com/gravitdesigner/welcoming-gravit-to-the-corel-family-9cd0c7f3a32c

    Does this press release and the promises sound familiar? What happened to Gravit? It was barely a year before Corel had new plans, their new "family members" were obviously dismissed, the support quietened, then the support forum disappeared, and Gravit Designer (now Corel Vector) has not been developed on since either.

    You have to be more than youthfully naive to take a business risk and base your work on software from companies that let themselves be adopted with crossed fingers and business promises of a bright future.

    Did Corel then lie at the acquisition? No, not at all. Reality just looked different inside the big cog at Corel just a year later, and there was nothing the formerly happy employees at Gravit could do about it. It was no longer their company, and thus they were powerless. And then they were no longer welcome in the family either.

    I was reminded of Gravit today, when I read a sad news about a company with quite a success here in the country. Last year, they made the same maneuver with big words and promises, they had built a quite solid, technologically strong, and popular online product over 15 years and now joined a FAMILY (again as the little brother), and yesterday all 95 employees suddenly were told that they no longer have a job. The plans in the family had changed. And how many times have I seen this happen now? I've lost count.

    I do not allow the subconscious to drive me towards optimistic bias - a well-known psychological phenomenon that I see plenty of around here.

    That is exactly what I was instantaneously thinking about when reading Serif has joined a family.

    Gravit was a good software with potential but after they had became a family member it got quickly quiet around it... and eventually will disappear. The difference to Affinity is that it was really basic and not a suite and Corel had already its very good counterpart. Taking over Gravit was merely to stop it becoming a dangerous competitor. 

  2. On 11/21/2022 at 5:20 PM, DR34MER said:

    It’s better than nothing, but I have to say the new swipe-up solution is not ideal. Why complicate things when you can just bring it back to its original place as a separate button. And on another note, I just wish the UI stayed the same. New UI is fine but what bothers me is that it’s not clearly defined and intuitive anymore. Like for example in the FX layers, I get that I can toggle the icons under the sliders to switch between types of FX settings but the lack of naming just stagnates my mind. While in the older version, sliders are named and are highly convenient to use. Highlighted in red rectangles to show the difference.

    D4196D58-BDE3-4F09-9854-A82913B56BD9.jpeg

     

    31BB5E11-C871-4B23-A9D0-F553EC3D9A1E.jpeg

    I also liked the older appearance and behaviour better. 

  3. 5 hours ago, Dan C said:

    Hi @transitdiagrams / Chris,

    Apologies for the delayed response - I've tried this here on my M1 iPad using both Horizontal Triangular & Isometric and the gris is stationary for me as I zoom around the document.

    Can you please confirm for me:

    • What iPad model are you using?
    • What version of iOS is installed?
    • Do you have any Display Zoom or Accessibility options enabled?

    Many thanks in advance!

    Hey Dan,

    thanks for the late reply. It is more or less solved for now - Display Zoom was causing the problem. I have an iPad 5th generation with iPadOS 16.2. I turned it off and it worked perfectly. It would be nice though to have grids working with Display Zoom on too.

    Chris

  4. 13 hours ago, Dan C said:

    In the meantime, I have found that when changing the Display option in Affinity Designer > Preferences > Performance from OpenGL to Metal, then restarting the app, the grids are displayed correctly.

    Hey @Dan C,

    thank you for the tip. Now it's working correctly. So I can confirm it. 😃

    image.thumb.png.7d7473a7810fe04590b6d86c331ef330.png

     

    PS: there is the same issue (even stranger behaviour) on my iPad - made a post for it:

     

  5. 2 hours ago, Dan C said:

    Many thanks for uploading that for me! I can confirm I've been able to replicate this issue both on Windows and Mac, therefore I'm getting it logged with our developers now :)

    In my testing, there was not much noticeable difference with the above options enabled/disabled, so I believe this to be a more computational issue, rather than rendering or compositing.

    I also tried different performance options and also without better results.

    Hope this gets fixed in the next version as this can be annoying to waiting just for minor changes of the corner. 🙂 

    Chris

  6. 21 hours ago, Dan C said:

    Firstly, please change the 'Darstellung' option to Metal, restart the app as prompted and then try editing once again.

    If this doesn't seem to change the behaviour, please try unticking Hardware-Beschleunigung at the bottom of the dialog, restart the app and try again once more. (Note the Darstellung should remain as Metal at this time.

    If there is still no improvement, please return the Darstellung option to OpenGL, whilst leaving Hardware-Beschleunigung unticked, and restart the app once more.

    Do you see any noticeable differences with these options enabled/disabled?

    I will try and see how the different options work.

     

    22 hours ago, Dan C said:

    Can you please upload this to the below link for me, then reply here to let me know once this has been uploaded?

    Uploaded. For example: Try to adjust the corners of the S1 stroke - this one always causes freezing of the app.

     

    Thanks again 😃 Chris

  7. 22 minutes ago, Dan C said:

    Hi @transitdiagrams/Chris,

    Sorry to hear you're having trouble!

    Are you able to provide a copy of a file where this issue occurs? If you'd like a private upload link for this, please let me know.

    Can you also provide a screenshot of your settings under Edit > Preferences > Performance for me?

    Many thanks in advance :)

    Hi Dan,

    thanks for the fest response.

    As it is an work in progress for a commission (not yet approved by the customer) I would only share it privately and only with the layers containing the multiple lines.

    Here is a screenshot of my preferences:

    105440136_Bildschirmfoto2022-09-12um12_58_24.thumb.png.9a1e29e093bc8431619a2f3b3591fb52.png

    Chris 😃

  8. 1 hour ago, Dan C said:

    Thanks for providing that for me! My apologies as your understanding is correct, for strokes in the 'middle' of the appearance stack, neither behind/in front options are required, therefore neither are selected and this is expected behaviour.

    Just to confirm, the file you have provided, does this show the same Stroke/Appearance error for you? As opening this file here shows the same values for me in both locations.

    That's how I see it:

    1859797049_Bildschirmfoto2022-09-12um12_53_24.thumb.png.95a92ab5289fe9eca899743aaecbe54e.png

  9. Hey there,

    sometimes when I want to adjust many node corners (the radius of curved corners in my cases) at the same time AD tends to freeze for a few minutes before it has been able to make all changes. Is this normal behaviour? The strange thing is that it only occurs sometimes in some files. It also seems to happen more likely the longer I am working continuously on a file.

    Anybody else having this sort of issues?

    Chris

×
×
  • 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.