
Michael A. Lowry
Members-
Posts
39 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
I like your idea. However, it would not be straightforward to implement. When you change the constituent shapes, this can dramatically impact the resultant shape. How would the Shape Builder know which parts should be included in the resultant shape, when regions can disappear, come into existence, move, combine, or split based on the geometry, size, position, and orientation of the constituent shapes? There would have to be a way for the user to specify rules for inclusion & exclusion of regions. It could get complicated, and would likely resemble programming more than drawing. If Serif could come up with a solution to this challenge, I would be happy. But it is not as simple as you might at first think!
-
I made the following changes, and now SVG exports work as expected. Changed the shield gradient to four distinct filled rectangles. Joined all the curves for the oars, and eliminated the cut-out layer in Erase blend mode. Changed the outline curve from Erase blend mode to a solid stroke of the background color. Changed layers in Passthrough mode to Normal mode. The solid color outline will work fine as long as the background color is solid. If I need a transparent background, I'll have to subtract the outline curve from the oars. Does Serif plan to add support for vector exports of gradients and Erase layers? Nordiska Logo.afdesign
-
Michael A. Lowry reacted to a post in a topic: Curves rasterized on SVG export
-
Michael A. Lowry started following Artboard export leads to blank (white) file and Curves rasterized on SVG export
-
Artboard export leads to blank (white) file
Michael A. Lowry replied to Michael A. Lowry's topic in V2 Bugs found on iPad
That was indeed the problem. The layer was marked invisible even though the buttons indicated that it should be visible. In the Layers panel of the Export persona, I tapped on the layer visibility button next to the layer that was not showing up in the export. Even though nothing changed in the Layers panel, once I switched to the Slices panel, I could see that the layer had been enabled. Then, exporting worked as expected. I look forward to the fix for this bug. Thanks for your help. -
Artboard export leads to blank (white) file
Michael A. Lowry replied to Michael A. Lowry's topic in V2 Bugs found on iPad
The visibility of the layers makes no difference. I’ll contact you directly to send the file. -
Artboard export leads to blank (white) file
Michael A. Lowry posted a topic in V2 Bugs found on iPad
I have a document with two almost identical artboards. In the Export persona, I created a slice for each artboard. When I export the slices, one of them is exported correctly, but the other one results in a blank (white) file. The Layers view of the Export persona shows the content as it should be. However, the thumbnails in the Slices view reveal what will actually be exported: a blank white slice instead of the expected content. This is Affinity Designer v2.4.2.2371 on iPad OS 17.4.1 running on an 11-inch iPad Pro (model A1980). -
Shape Builder crashes Affinity Designer on Mac
Michael A. Lowry replied to Michael A. Lowry's topic in V2 Bugs found on macOS
@Ben: Is it fair to say that bugs specific to Symbols are not the top priority? (I recall that it took years to fix the Copy-and-Paste Symbols bug.) -
Shape Builder crashes Affinity Designer on Mac
Michael A. Lowry replied to Michael A. Lowry's topic in V2 Bugs found on macOS
Any news on this topic? Has this problem been accepted as a bug? Is there a public bug tracker somewhere? -
Shape Builder crashes Affinity Designer on Mac
Michael A. Lowry replied to Michael A. Lowry's topic in V2 Bugs found on macOS
The same problem happens in the iOS version. -
Michael A. Lowry reacted to a post in a topic: Shape Builder crashes Affinity Designer on Mac
-
Shape Builder crashes Affinity Designer on Mac
Michael A. Lowry replied to Michael A. Lowry's topic in V2 Bugs found on macOS
As you can see in the file, I used symbols to keep the shape bilaterally symmetrical. Detaching all of the symbols appears to have to resolved the problem. So perhaps Shape Builder has a problem with constituent shapes based on symbols. -
Shape Builder crashes Affinity Designer on Mac
Michael A. Lowry replied to Michael A. Lowry's topic in V2 Bugs found on macOS
-
This morning I tried to use the new Shape Builder tool for the first time. After several attempts, I gave up. I have not been able to create a shape yet. The app has crashed several times — once when I accidentally typed Command-Delete while selecting areas, and every time I tried to commit the selection and create the shape. I’m using Affinity Designer 2.0.0 on macOS 13.0.1.
-
Winsome reacted to a post in a topic: Nordic Rowing Club of Zurich coat of arms
-
On my iPad, iCloud backup has not been working for a long time. I opened a ticket with Apple Support several months ago. This past week, Apple developers finally narrowed the problem to a file or files created by Affinity Designer. According to Apple, there’s at least one file over 100 GB on the iPad that belongs to Affinity Designer. And because iCloud Backup does not support backing up files larger than 100 GB, this large file is preventing backups from completing. (iCloud Backup misleading reports that there is “not enough storage available” even though there is plenty of space available in my storage plan.) If I disable backing up files from Affinity Designer, iCloud Backup works fine. I was unable to find any such large files on my iPad by using the Files app or by browsing the iPad’s content from the Finder on my Mac. However, using a third-party file system browser, I was able to see some additional details, such as file creation/modification dates and folder sizes. Based on this information, it seems the Designer folder on the iPad is taking up more than 300 GB even though the files under the folder add up to just 228.81 MB. Evidently Affinity Designer is using more than a thousand times more storage than can be explained by the listed files. Apple developers were able to read some metadata about the >100 GB file that is preventing the iCloud Backup from working correctly. In these metadata, they found what looks like a date & time stamp: 20190516103049. (It might be part of a file name, but I’m not certain.) I have read several older threads about similar problems. It seems a work-around might be to move all Affinity Designer files to other locations (e.g., iCloud Drive or a computer), and then remove & reinstall the app. I would prefer not to do this unless absolutely necessary. I would also like Serif to help investigate this problem so that a permanent fix can be found.
- 8 replies
-
- affinity designer
- affinity designer 1.10
- (and 5 more)