Search the Community

Showing results for tags 'SVG'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Questions
    • Feature Requests, Suggestions and Feedback
    • Bugs in Affinity Designer & Affinity Photo
  • Learn and Share
    • Tutorials
    • Share your work
    • Resources
  • Affinity Beta Support
    • Photo Beta on iPad
    • Designer Beta on Mac
    • Designer Beta on Windows
    • Photo Beta on Mac
    • Photo Beta on Windows

Found 246 results

  1. Hello there, I am drawing on a Wacom Bamboo Slate, which can export your drawings (and writing via a kind of OCR) to text, image formats and SVG. Here's Wacom's specs for the Slate: http://www.wacom.com/en/products/smartpads/bamboo-slate#Specifications The Slate's ballpoint pen is marketed as having 1024 levels of pressure which in theory seems a bit much for a ballpoint pen, but would be nice if it could reproduce the light and heavy strokes you have made on paper. My problem is that the SVG files exported from Wacom's Inkspace app are filled black shapes instead of strokes. The shapes are thicker than the original paper lines, losing most of the line width variance, and I cannot find a way to reduce the width as you would with a stroke. I am attaching an image to illustrate my problem. Any thoughts on how to convert these shapes into strokes so that I could make them thinner? Many thanks in advance! PS there may be an answer in the thread below ('line width is not yet fully supported in the SVG standard'), but I'd like to confirm if something can be done about this using Affinity Designer? https://forum.affinity.serif.com/index.php?/topic/45452-how-do-i-import-paths-they-keep-turning-into-shapes/#comment-227169
  2. I'm interested in creating SVGs on macOS. And I like to edit the source code (often) directly so that it has an immediate effect on the graphic. Exactly the same concept you find e.g. in Adobe Dreamweaver for HTML. A "design view" and a "source code view". Alway synchronized. What do you think about adding such a functionality? Thanks.
  3. I want to import/place the following SVG file (hlines.svg). It looks correct in Illustrator. I can also open the file in Chrome and it looks correct. Here is how it looks when imported/placed in Designer: It is faint, but only the square in the upper left corner appears and it is missing the two horizontal black bars. How do I fix this? If I open the file it looks similar but I get a long list of layers. It seems that all of the boxes are being stacked on top of each other. I can select a layer and then move the SVG object to a different location. In this example, I moved each of the boxes from the upper left corner, where they were stacked on top of each other. I don't care if the objects are on separate layers or flattened on the same layer. I am not doing any editing except for scaling the entire image to 30 in x 30 in. I just need it to look like the image at the top, hLines.svg
  4. Before 1.6.0, whenever I opened my old .svg files (created in Inkscape) in Designer they would open with all layers and objects visible. Now many objects are hidden when opened, without any clear pattern that I can tell (it's always the same objects every time for the same file, but which parts are affected vary from file to file). The same thing happens if I just copy and paste the objects from Inkscape into Designer.
  5. I have a SVG file that looks normal when I open it in the browser or preview it with the built in preview tool in macOS. If I open the SVG in Affinity Designer it gets all twisted. I have open the SVG in Affinity Designer earlier and it worked just great then. Is there a setting that I have managed to turn on in order to do this, or is there a bug in Affinity? Affinity Designer: V. 1.6.0 MacOS: 10.13.1 This is how the SVG looks like when I open it in Affinity Designer. And this is how is how it is suppose to look like. This is how the image is suppose to look like. Teknologi_header.svg
  6. When drawing elements to be cut on a laser cutter, setting up a document in mm is very helpful. Unfortunately, the common interchange file format for this kind of device is SVG. While the file format supports measurements in defined units, Designer converts to pixels during the export, which means that after import, the dimensions have to be recalculated. Therefore, it would be great to have the option to preserve the units from the document during export, such that a 50x150mm rectangle is exported just as such.
  7. In the forum and in AD Help I find little on SVGs although SVGs are commonly used and can be problematic. I create graphic overlays in AD, copy each graphic or set of graphics to the clipboard, isolate the graphic in its own AD doc using "New From Clipboard" (a handy AD feature with its shortcut!) and then export it as an SVG for use in an app on a base map of the exact same size and the exact same Document Setup parameters. This SVG may only be 4k while the graphic in my original AD doc would be considerably larger. For the app I need very light weight SVGs. I'll try to explain my problem clearly. 1. An ellipse is created in AD but can only be elongated on one of two planes at right angles (up-down and across). See image one below. 2. For my graphic I need to rotate such an ellipses, say 45 degrees. See image two below. 3. When I select the rotated ellipse alone (within a layer which may have other graphics but *only within* the rotated ellipse), I get one set of numbers in Transform = the limits of the actual rotated ellipse. However, if I select layer, then the area is no longer restricted to the edges of the ellipse but rather to the bounding box, now rotated together with the ellipse. See image three below. The corners of this rotated bounding box of course extend beyond the original non-rotated bounding box, and thus beyond the borders of the actual ellipse. This may related to AD's point of origin requirement, etc. 4. I copy this rotated ellipse to the clipboard and isolate in its own AD doc using "New From Clipboard." This new doc shows all "empty space" around the actual ellipse (the same as in image three below) since the clipboard apparently recognizes and uses the existence and four corners of the rotated bounding box. 5. PROBLEM: As you can imagine, my original placement numbers for the rotated ellipse, recorded from Transform (x and y and w and h of ellipse), have changed. They are no longer the actual edges of the rotated ellipse but rather the four corners of the rotated bounding box. Therefore another set of numbers from Transform must be recorded. Worse than that, pasting the SVG into my original doc (to be sure it is aligned correctly), none of my recorded placement numbers work. I am forced carefully to realign the SVG over my original non-SVG ellipse and hen make a new set of placement numbers that work properly. 6. QUESTION: Is there any way (and if not could be in future versions) that the actual size of the ellipse (not the four corners of the rotated bounding box) could be maintained when "New From Clipboard" is used so that the "empty space no longer appears and the placement numbers remain stable? (Yes, I do try placing the ellipse with the numbers from image three, but these numbers place the image below and the the right of its proper position.)
  8. Hi. When I import a SVG with a rectangle with the rounded corners property, for example: rx="15%" Affinity Designer ignores the value and sets a default absolute value of 0.2px. guidelines.svg
  9. Hi. I'm not sure whether this is a bug or done intentionally. If I created a gradient-filled-shape in AD. Then the shape is skewed. Then export it to SVG. The resulting SVG file created an image in place of that gradient. Thanks.
  10. There are problems with the display / rendering of connectors and labels of connectors on import of an SVG into Affinity Designer. In Affinity Designer the connectors are no longer properly connected to the nodes. I attach a comparison of the appearance in the Fnder vs that in Affinity Designer. Affinity DesignerScreenSnapz001.pdf FinderScreenSnapz001.pdf Argument_supports_Claim.svg
  11. When exporting an svg, we can get issues where the id of an exported element may clash with the id of something else. For example, in one of my files, I could have a layer called "myTest". The problem occurs when I embed this into html, which may also inadvertently have myTest defined as well. This will lead to a name clash, which as you can image; would lead to all kinds of trouble. I'd ask if theres any way to prefix the exported id's with something upon export. For example if I have a file called abc123, upon export, the id will be set to "abc123__myTest", or something like that?
  12. Attached is a screenshot of a problem I'm having with masks in SVG. On the left is the SVG opened with AD 1.6 and on the right is the SVG opened with Chrome. As you can see, the U logo and the shading along the upper left edge does not show properly in AD. I found a couple of other forum threads discussing issues with SVG masks that go back more than a year. Is this the same known issue? Any idea when it will be fixed? Attached is the SVG file I am working with if you need it for testing. For reference, it was created in Adobe Illustrator and taken from the UniFi-2017 SVG.zip file in the Ubituiti Networks Support Forums. Thanks UniFi_Video_UVC-G3-Dome.svg
  13. Image clipping on an SVG file is not displayed correctly and the vector mask layer is missing, this is not a problem when I tried to import it into Adobe Illustrator. This problem is not present in the previous version (1.5.2.58) here both Inkscape and Illustrator displayed the SVG correctly as you can see, the circle vector mask is deleted, caused the clipping not displayed correctly, and the image size/image scaling is not correct here is the file to check it out drawing.svg
  14. Hi, I noticed I now have to remove xmlns:serif="http://www.serif.com/" from the svg files to be able to upload to Canva.com. Any chance of leaving this out in future releases?
  15. got lost... - I have SVG file that, when imported to Canva.com project, has editable color (within Canva). - When I open that SVG in Designer (with an intention to do some tweaks) and export it (without changing anything) to SVG, then when importing it to Canva, it looks ok, but suddenly the color is not editable. - I have absolutely no idea what I'm doing wrong - or if any of the export setting is not right (I tried so many combination without any effect). Attached files: test-vctr.svg ... original file that I'm importing to Designer (and it works as it is within Canva -- possible to change color) test-aff.svg ... exported above file (without any action) from Designer to SVG (when imported to Canva, color cannot be changed). I know I'm discussing another online tool (Canva) here, but in general it's the export process within Designer that is causing "some" change in the workflow. Anyone? thank you test-aff.svg test-vctr.svg
  16. Hi, I'm newer in Affinity Designer. Adobe illustrator has line segment tool, when i use it, and then export to SVG file in which has <line> tag.But Affinity Designer don't. I use pen tool with line mode, and export to SVG, only <Path> tag. Can Affinity Designer export to SVG file with <line> tag?
  17. i have a bug, the exported SVG file is not show the real resolution. i create 100x100 px in affinity designer, and export it with export persona, but what i find when i open it in another app like Illustrator or Corel draw, it's show 800x600 px (SVGA). i export it as SVG for web and SVG for export and make some change with that option's, but i did not find the way to make it exported with same resolution. here i put 2 images. np: if i open the SVG file on affinity, there's no problem, but the problem only happened when the file is opened on another vector app
  18. Hi, Attached two files. In one exported all right, because elementry redrew, while in the second file is exported as a path. Previously, there was a problem with opacity, or something else, now everything seems to have checked, but are exported anyway wrong. tell me what the problem is and how it can be solved without re-drawing elements riga1.afdesign riga2.afdesign
  19. Hi! Firstly, I want to thank you for your products. You do amazing work guys and I really enjoy using them! I believe there are more important features to be implemented, but I couldn't find this one here, so let's list it: There is a "new" font format called OpenType-SVG that stores vector or bitmap informations to create colored fonts. Would be great to push the limit :) PS: Links explaining OpenType-SVG/Color Fonts: http://www.colorfonts.wtf/ https://creativemarket.com/blog/color-fonts?utm_source=ownedsocial&utm_medium=social&utm_campaign=blogposts&utm_content=inspiration
  20. Working with simple shapes creates simple SVG files, but the moment I add an outline the path... Well, haha, it becomes a nightmare. TWO objects are exported: the solid fill object, and the outline object (why?). The fill object is fine, but the outline has gone from 10 control points to ~2200. Best I can figure AD is doing this because it doesn't do outlines the same way SVG does, but since SVG supports strokes of different widths and miter types, I don't know what, specifically, the issue is. If I export a solid object, it works as expected, same number of points in AD and Inkscape. Add an outline, and hahaha ouch. I'd love to know what's up with this and whether AD just can't do outlines->SVG without becoming unwieldy.
  21. Hi, Seems that colors in SVG files using RGBA (RGB with Alpha value) is rendered with 100% opacity. I have attached an example SVG file. Did I mention that also HSLA colors are not handled correctly? /Sten myspace.svg
  22. Hello, I have generated an SVG file using a Blender add-on, which is scripted in Python. When I try to open the file in Affinity Designer 1.5.3.69 I get the following error: "Failed to open file" "The file could not be parsed." The file opens fine in the latest Google Chrome and Adobe Illustrator CS6 I found a solution to fix the error: Change the line: <?xml version='1.0' encoding='ascii'?> to: <?xml version='1.0' encoding='UTF-8'?> This issue is the same as the one reported on the "Bugs on Mac" forum: Here is a sample file: 0001.svg Thanks, Dave
  23. When exporting to SVG, is it possible to get HTML5 output without putting every property into styles? Example: <?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <svg width="100%" height="100%" viewBox="0 0 300 57" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:1.5;"> <rect x="78.614" y="8.716" width="220.68" height="14" style="fill:#e0e0e0;"/> <ellipse cx="28.992" cy="28.132" rx="24.492" ry="23.632" style="fill:none;stroke:#e0e0e0;stroke-width:9px;"/> </svg> According to https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute#Core_attributes this can be written like this (looking only at the rect and ellipse): <?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <svg width="100%" height="100%" viewBox="0 0 300 57" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:1.5;"> <rect x="78.614" y="8.716" width="220.68" height="14" fill="#e0e0e0"/> <ellipse cx="28.992" cy="28.132" rx="24.492" ry="23.632" fill="none" stroke="#e0e0e0" stroke-width="9px" /> </svg> In my opinion this a more modern and cleaner way of writing SVG.
  24. I have an SVG which contains a gradient with 2 stops (darker blue to lighter blue) that I created with Affinity Designer that I later optimised with SVGO for smaller size for web use. However, after re-opening the optimised SVG in Affinity Designer, the gradient doesn't show - the entire curve appears as filled with only the first colour stop. However, when clicking on the curve, the fill settings show the correct gradient with both stops. The gradient in the optimised SVG shows up fine in all web browsers and a few other graphics editors. Attached is the file. Thanks mountain.svg
  25. Hi again, as I was importing some of my SVGs, I noticed some slight issues with their appearance in Affinity. So, I did some testing and found out what was causing these issues. I've created a separate file for each bug (14 in total). It should become clear by following the instructions below. If not, just let me know! Disclaimer: Importing the first file will (most likely) make Affinity crash. Please save your work progress before trying! Instructions: 1. Open the attached files in a web browser 2. Now import them into Affinity (Photo or Designer) 3. Compare both versions closely Cheers! ------------------------------------------- Affinity Designer Version: 1.5.1.43 Affinity Photo Version: 1.5.1.54 Operating System: Windows 10 1_crash_when_colour_capitalised.svg 2_stroke_although_colour_not_set.svg 3_no_fill_when_colour_capitalised.svg 4_incorrect_gradients_when_gradientUnits_objectBoundingBox.svg 5_nested_svgs.svg 6_no_repetitive_gradients.svg 7_stroke_dasharray_wrong_direction_starting_point_array_too_short.svg 8_no_patterns.svg 9_incorrect_skewing.svg 10_no_drop_shadows.svg 11_no_blending.svg 12_close_path_and_moveToEnd(!).svg 13_no_masking.svg 14_no_markers.svg