Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.


  • Posts

  • Joined

Contact Methods

  • MSN
    had one, too
  • Website URL
  • Skype

Profile Information

  • Gender
  • Location
  • Interests
    Software Development, Fine Art & Travel Photography, Webdesign

Recent Profile Visitors

1,127 profile views
  1. Hello, I've finally installed the version 2 of all apps on a secondary computer to try them out. First thing I was missing is a drag tool. That device has a touch screen but it only accepts selection input, not drag the view. Touching and sliding with two fingers can only zoom (pinch gesture) but not drag. Two-finger-dragging only works either horizontally or vertically on the touchpad, not the screen. So I was looking for a drag tool that would allow me to drag and pan the viewport. In version 1 we had this hand icon in the toolbar: I can't find anything like it in version 2. Was it forgotten or is there now a secret hidden way to drag the view? Also, the toolbar's tooltips (the text labels that appear when hovering a button with the mouse cursor) are placed underneath the mouse cursor. That makes them unreadable (at least the first 2 letters) when moving the mouse pointer over them from top to bottom. When moving from bottom to top, the tooltips are often below the cursor, so they can be read. Tested with Affinity Designer 2.0.3 on Windows 10.
  2. Same result. I cannot reduce the file size by anything the application allows me to do. And I do think that removing old and unused junk is a defined behaviour of a file format. Would you like your master document file of a complex drawing to have an extra 100 MB size just because AD doesn't care to free old stuff? This file is indeed intended to be archived for a long time and used as basis for new developments. I already export parts of it to SVG for the final application, but this master file is also part of the source code and it just blows up the version control repository with every single modification. If that 1.5 MB file can also be 50 kB, I want it small, please. And not in 10 years. Recreating it is not an option because it contains dozens of layers and groups. All of them would be lost when exporting in a foreign format. As I see it, AD is just not reliable with its own file handling. You call it cleanup, I call it repair.
  3. I'm sorry I have no clue what you did there. I tried this: Create a new .afphoto file in CMYK/8 colour format Add that image to the afdesign file Change the afdesign file from RGB/8 to CMYK/8 Save Close and reopen Change file back to RGB/8 Delete the inserted image Save Now the file is a few hundred bytes larger than what I started with. Please someone official make a statement if this bug is being considered and how I can repair my existing file. I can also send you the original file for repair if I cannot do it myself with the public software.
  4. Has anybody found out what the issue is and fixed it? I'd like to reduce the size of my file soon. If the bug still exists, what workarounds do exist to repair that file?
  5. Looks like we won't see hatched fills in AD within the next 5 or 10 years. I don't fear because I won't get them when I'm very old, I do fear because I don't have them right now. How did you implement the alternatives? I don't know about those assets, can they be used to create patterns that just fill out any shape I throw them into?
  6. It's easy if you already know what bloats the file, in your case a colour profile. But mine is in sRGB and always was (AFAIR). So there's got to be something else in it.
  7. I'm wondering why this file is 1.3 MB large even though it has no content anymore. With the content (a few icons, nothing complex) it was 1.4 MB. I was surprised and tried to find the mysteriously complex shape by deleting one after the other. In the end, there was nothing left and the file size hasn't really gone down. The colour space is sRGB, even if the profile was embedded I'd not expect more than a few tens of kB. An SVG export of the whole document is 13 kB. Maybe a developer could inspect this file and tell me why it needs to be so large and what I can do about it. I have other files here that contain just a few icons (same style) of 40-50 kB. That's a much more reasonable file size. The original file contains icons that I have designed with Affinity Designer and exported to SVG for use in a web application. It also contains construction layers that I merged for the SVG export. I'd like to add the .afdesign file to the code repository so it's with the app code. But I'm hesitating to check in an image file that more than doubles the repository size. ItemTypes-2.afdesign
  8. Thanks for the references to other tools, I'll take a look at them. Maybe it'll be better to build my tool with Python instead of PHP (went faster for me) so I can more easily use the Fonttools API. I had to read this out loud a few times to get it – did you mean: voilà? 🙃
  9. I'm certainly not doing commercial things here, but the Material Symbols (and Icons) are released under the Apache 2.0 licence. I assume that also applies to the font files that the owner of that icon set provides. I'd be sure to place attribution where possible, certainly in my edit tool because the icon set is its main feature. Anyway, the tool will download the fonts itself, so every user of it acts on their own behalf. Source 1, Source 2, and from the slightly older Source 3:
  10. I get the font files from the Google Fonts CSS API. It's a bit complicated but I've automated these steps: Manual input: Look up the base URL for the font, here https://fonts.googleapis.com/css2?family=Material+Symbols+{style}:wght,FILL@{weight},{fill} Download that page with a Firefox user agent header Extract the font file URL from the provided CSS Download the font file These are woff2 files and I fetch them individually for each style because their CSS contained ambiguous specifications last time I checked. And the fonts are complete, not subsetted. They can do this for text fonts but don't even offer it for symbol fonts. I also haven't found the SVG sources for the new weights, so the woff2 file is my primary source now. I have no problem with that. My end goal is to have a tool that creates a subset of the icon fonts. A prototype of it has extracted me 33 icons into a tiny woff2 file of 3.5 kB. With manual postprocessing I even merged the icons of three styles (three files) into a single file of 5 kB. (woff2 compression works much better if all (and similar) glyphs are merged into one file rather than separate files.) And then, part of that tool should be a way to remix the icons. Like take a small checkmark from one symbol and insert it into another symbol to create a new combination. I might implement these simple edit operations directly on the contours and points of the font (converted to XML with Fonttools) with a live preview converted to SVG (view only). But for any more advanced editing like cutting away or merging shapes I need a graphics editor, like Affinity Designer. When I integrate that into the workflow, I have two extra conversion steps on the outlines: Convert double-quadratic curves by inserting the implicit middle curve point (and AD will then convert Q to C). After the edit, convert back the curves from C to Q. Meanwhile I've found that Fonttools provides code for that (cu2qu), but it's in the Python API so it would require extra integration work. In the end, when the user has edited the outline, there are some 3 points more for each curve. The next edit of the same glyph will already be harder and increase the number of points per curve to 9 or so. That's why I'd like to avoid these conversions altogether and import, edit and export only Q curves. I don't see any problem with the XML dump from TTX. The dumped data can reproduce their original SVG (tested for one symbol). And the round-trip conversion woff2→ttx→woff2 gives a working font with the same symbols. I could also copy glyphs and ligatures from one font style to another and merge them together. It's all there. The only problem left is that graphics editors wipe out Q curves and replace them with C curves which can't be used directly in fonts. Or maybe I'll have to convert the TrueType glyphs to OpenType which supposedly uses cubic curves. I haven't explored that path yet. Hope this explains it.
  11. Hello, Background: I'm working on a tool for font editing. The font is Google's Material Symbols (which I've learnt is completely new but I didn't know that when I discovered it 2 days ago). It comes in 6 styles and 7 weights. Each WOFF2 file has 200 kB and I only need a small part of the icons. So I found tools to extract information and create a subset of it. That's all good. But now come the ideas. As I'm already taking the font files apart and reassemble them better, I might as well edit some of the broken icons (yes, Google's quality isn't the best here) or even add and mix new ones. The Fonttools package for Python converts the WOFF2 file to XML and back. In the XML I get the points of each contour in a glyph. I made the test and converted one symbol by hand from XML to SVG. Apart from a vertical flip, it looks exactly like the original SVG (which is only available in a single weight, so unusable for me). A specialty of fonts is that they don't use cubic bézier curves with 2 control points but quadratic bézier curves with a single control point. And each visual curve seems to be constructed of a pair of quadratic curves with an implicit curve point in the middle of two specified control points. I could compute that manually and see the result. Problem: But editing and re-exporting this is odd. Of course I get the extra curve point (the middle one) that their original SVG with "C" curves doesn't have. But the quadratic curve is also gone in Affinity's SVG file and replaced with a "C" type cubic bézier curve with 2 control points that are different from what the quadratic curve had. At the moment I'm not sure if and how I could convert that back to put the curves back into the XML for the font file. Do I see it correctly that Affinity doesn't support editing quadratic curves and always just reads them as cubic bézier curves? Is there something I can change to keep the single "Q" type control point that I gave Affinity in my converted SVG? Or better yet, can I tell Affinity to export all (old and new) curves in the quadratic format? Should some curves not be available as Q, then I'd love to see Affinity constrain my edits to what Q can represent in the export.
  12. This happens too rarely to wait for it. Working without magnetic snapping seems impossible for me. And for the same reason I also cannot make a screen recording. But it does happen more often recently. Sometimes not for hours, then again several times.
  13. Have you changed something recently which sneaked onto my computer through automatic updates? Can I see when the last update was installed (through Microsoft Store)? I have Affinity Designer 1.10.1 on Windows 10 and only since a couple of days, when I click on any object to select it, it gets immediately moved by a few pixels. Probably towards some snap target that happens to be nearby. I haven't found a pattern behind it. This has never happened before and I've been using this app quite some time during the last weeks, so I can tell. This is very annoying. Most of the time I notice, so I can undo, but I fear that sometimes I might not, so I'd introduce inadvertent changes to the layout just be selecting something. I've enabled the magnetic alignment option but not the pixel alignment. My document is set up for home printing (A4 format), not web.
  14. Hello, Is there a specific reason why I can't make the line ends (arrow heads etc.) larger than 500%? I'd need that and this feels like an arbitrary limit. When I enter 700 the value is reverted to 500.
  15. Still an old thread. I have exactly (I guess) the same problem here. I'm designing icons at 16x16 pixels, each one in an artboard with a name that describes the icon so that I know what to draw/see here. At 100% scaling, the target size, the artboard names are so big that they not only overlap each other (not a problem) but also the row of icons above that (obstructs my view entirely). The artboards are aligned in 3 rows of 5 icons. Deleting their names would remove any documentation what they are and needs to be reverted. Not a feasible task for a quick look at the unfinished result. Increasing their spacing would require lots of scrolling in the zoomed in view where I edit the icons. Also, the icons will appear close to each other in the target application, so having them close in the preview is useful. I don't know anything about the other advanced features mentioned before. I just want to hide those labels for a moment. Can't be that hard. Just give me a menu command in the View menu and I'm happy. It's been a while since I've last seen a new feature in Affinity apps.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.