-
Posts
2,496 -
Joined
Everything posted by ronnyb
-
Hmm, some filters have that "Preserve Alpha" checkbox... maybe that's the issue....
-
Is there a stroke on the source?
-
Because it's their app and they do as they see fit... 🤣
-
No Help > Search field in V2.5.x for Mac?
ronnyb replied to R C-R's topic in Other New Bugs and Issues in the Betas
Absolutely agreed. I rely on the Help >Search to quickly locate and execute commands instead of hunting around the main menu's hierarchical structure, like using macOS's built-in Spotlight Search to quickly execute open apps, do simple calculations on the built-in calculator, find contacts, etc. A quickly accessible CLI is invaluable. Please return this vital functionality. Thanks for all you do! -
I like punny yolks, keep 'em coming...
-
Thanks @GarryP I missed that!
-
Egg shape is an importan design primitive. Would be great to be able to modify the radii, the distance between the circles, and concavity or convexity of the curved sections between circles, for hourglass shapes, all interactively.
-
AD macOS Navigator Studio Redraw bug
ronnyb posted a topic in Other New Bugs and Issues in the Betas
On my external 4K display. I can send original file to private upload link if necessary.... Screen Recording 2024-04-22 at 7.11.09 PM.mov -
Designer (macOS) redraw is much slower
ronnyb replied to ronnyb's topic in Other New Bugs and Issues in the Betas
Thanks for checking @MikeTO. I have the same performance settings... However, I just rechecked the file on both beta and retail versions and the performance seems to have returned to normal... perhaps my system was low on memory or running something in the background, I forgot to check Activity Monitor to see what was going on... I guess I will keep an eye open and report back if the issue resurfaces.... -
While scrolling vertically thru a complex document (300% zoom), I can see the redraw struggle to keep up with panning, and Designer renders the document in low res/blurry for a few seconds before the final sharp view renders. This is not the case with retail v2.4.1. @Sean P I'm using the complex file I recently uploaded to you here: https://forum.affinity.serif.com/index.php?/topic/202459-designer-macos-beta-242-breaks-rendering-of-fx/
-
Variable Font Support Discussion (split)
ronnyb replied to fde101's topic in Beta Software Program Members Area
Thanks for replying @Ash Btw there is currently partial support for single stroke fonts, except some characters don’t render, so hopefully it wouldn’t be a huge deal for the devs to slip it into an upcoming beta… -
Variable Font Support Discussion (split)
ronnyb replied to fde101's topic in Beta Software Program Members Area
@Ash, it’s great to see support added for this format of fonts. Will this new font support upgrade also feature support for single stroke /centerline fonts used in CNC applications? Single stroke fonts do not define glyphs using a perimeter outline filled with color, but by a single path (just like handwriting) to define the centerline of the letterform, with no outlines around the glyph. PLEASE PLEASE PLEASE PLEASE include support for this font format. It dovetails perfectly with the new DXF support. I can’t use ANY affinity apps for typography bc support for single stroke fonts is missing…. -
Yes, it goes away when I delete the artboard and keep the objects! Correct, that was NOT an imported PDF. That's the native file that's misrendering. Yes I tried, it makes no difference whether or not an external monitor is connected, it still misrenders the file. Desktop Publisher renders the same file perfectly, just as Designer and Photo did up until the last beta 2.4.2, with or without external monitor. Designer on iPadOS (2.4.2) renders the file perfectly as well. @Sean P It seems like this is an Artboard issue on macOS for Designer and Photo..... Below are the remaining screenshots you requested. Designer Performance Settings Photo Performance Settings Navigator
-
@Sean P, i will re-upload the .package file in a bit… Sig is outdated, I’m on latest macOS Sonoma… I don’t think so, that doesn’t make any sense, otherwise why does Publisher render the file fine but Photo and Designer fail at rendering the same file on my computer with the same setup?? Also, why did it render fine before the last beta, now it’s broken (only in Designer and Photo)? Remember this bug started as a bug only on export, now it has crawled into the main rendering display… my setup has not changed at all, same monitors etc.
-
I agree this is definitely a pain point when using Affinity and converting text to outlines. An automatic hierarchical grouping of letters into words, and words into paragraphs would be ideal. An additional benefit would be to respect the Insertion Order functionality so that one can specify whether characters are converted to outlines in default or reverse order in the layer stack, so one can “read” the text vertically on the layer studio….
-
I need a private link to upload a file so you can see how it's misrendering, something it handles fine in the release version (2.4.1) I previously reported this as a bug on export, but it seems the bug has now infected the regular display rendering as well.... WRONG (latest beta 2.4.2) RIGHT (Retail 2.4.1)
-
Accessibility: Customising the UI font size
ronnyb replied to AllanP's topic in V2 Bugs found on Windows
Same here. We’ve been begging for an improved (larger) UI font for almost TEN years… hopefully this decade we can get the feature or at least a NeuraLink implant might be available faster, idk….. -
Congrats on the acquisition @Ash! Hopefully the hardworking devs who built this amazing platform will also benefit from the financial gains surely gained by the shareholders. Taking on Adobe certainly requires enormous resources, and I’m happy Serif found a synergistic partner and it wasn’t a competitor seeking to eliminate the competition as was Adobe’s modus operandi on its ruthless hijacking of the creative space with the purchase and elimination of so many superior competing products across many creative sectors in the 90s and since… I think a dual model makes sense on many levels. Maintain the current perpetual license for independents, small shops, and the introduction of a subscription license for larger corporate environments where it makes more sense and is necessary for collaborative/cloud services. The subscription model will generate the funds for continued development of cutting edge features which can be integrated into the perpetual license version… lots of positive possibilities…