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

Patrick Connor

Staff
  • Posts

    9,750
  • Joined

Posts posted by Patrick Connor

  1. 7 hours ago, Hangman said:

    Hi @MikeTO, the main reason for highlighting the behaviour in this thread was simply because the Typography feature becoming a studio panel is new to the 2.5 Beta so it seemed (to me at least) to be the appropriate place to raise it…

    I appreciate this behaviour has been reported with other studio panels in the past so the behaviour itself isn’t new but that behaviour has been related to specific studio panels in previous Beta or Release versions. I’m sure if I’ve posted this incorrectly in the wrong forum someone in the Moderation team will move it to the correct forum… 

    I appreciate this is a grey/gray area but when a function has been refactored (like many existing publisher panels and this new panel) I think it's fair to assume that all old bugs might have been fixed as it's effectively new code. So if an existing bug does exist in an area where lots of changes have occurred and were specifically asking what you see, I'm ok with a bit of duplication. The reverse is true too. A long standing issue being tidied up in the refactoring may be worth mentioning too.

    The time not to mention existing bugs is when we haven't said there's been a refactoring or new functionality so nobody is surprised that nothing has changed

  2. 4 hours ago, William Overington said:

    So has my suggestion made in that thread now been rejected or is it still under consideration please?

    We do not comment on whether ideas are accepted or rejected, otherwise everyone else posting in the suggestion forum would demand to know if their suggestions were accepted or rejected also.

    No you cannot demand copies of what you wrote. Keep your own copies if that's important to you 

  3. On 4/13/2024 at 8:59 AM, AR44 said:

    With the .2371 Beta update, the artifacts/lines still exist with Hardware Acceleration turned on. With Hardware Acceleration deselected, the red and green artifacts are gone.

    Please could you try the new 2.5.0 beta with Hardware Acceleration ON (join our beta program) and see if the problem has been addressed for you? 

    Can you report your findings in this linked beta thread below made to share the results

     

  4. In another attempt to fix the artefacts that can appear on Windows when developing RAW files in 2.4.x (with hardware enabled), we have changed the RAW processing pipeline. 

    Please can you report in this thread any problems you continue to see with RAW processing when using the 2.5.0 beta builds.

    I will be asking users from some of these threads to come here and test the beta builds and post here (rather than their original 2.4.x thread)

  5. The file format is not designed to be small it is designed with fast drawing in mind and image previews of all files are saved. "Linked" in an affinity file mostly means "watch out for possible changes" so the internally saved previews (at a number of sizes/zoom levels) are still there in the saved file, just not the original source file. Without those previews it couldn't draw quickly as you change zoom level.

    Perhaps we could offer a slower loading smaller sized "save minimal" that always regenerates the previews of a linked file on each load but that's not what we have currently, sorry.

  6. 21 hours ago, bbrother said:

    So we will see what they will present in the upcoming beta version (2.5)

    What? This deal was done 3 weeks ago and you seriously think "noticeable progress" (by which I assume you mean new features) will be beta ready by the very next cycle, as a consequence of Canva influence or involvement? It's hopefully starting this week. The contents of 2.5 are no way to judge any influence in my opinion as it's really early days. But I do love your thread and the scope of it's ambition.

  7. 2 hours ago, tzvi20 said:

    What does the RMAP tag on the threads about this mean?

    These tags are simply used by our team to track certain conversations about features / feature requests - they do not indicate that a feature will be added to the apps, or indicate any specific timescale for features once added to a thread.
    They are purely an internal tool for our teams metrics and information gathering therefore I would not recommend paying them mind as a user.

    Once we have information to share about new and upcoming features, these will almost always be posted first in the New Features beta section of the Forums :)

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