Jump to content

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
    • Affinity Support & Questions
    • Feature Requests & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 373 results

  1. For some reason, some SVG elements keep turning into images? The file I have uploaded is part of a bigger illustration. However, whenever I export it as an SVG it turns into a png (i think) and the quality is terrible. I have opened the file up in Brackets a free Adobe code editor and reading the code you can see it's a PNG. Is there a workaround? I have also included the greater picture (not finished) and it looks like everything below the eye level is images. Thank you very much for your prompt response. I have noticed that this has been happening all the rime but now I'm turning pro and it can't continue really. JUST DECKING SVG.svg broads-animation.htm 01-2 NORFOLK BROADS WINDMILL.afdesign 01-2 NORFOLK BROADS WINDMILL.svg
  2. Hi, there is one thing I miss from Illustrator and it's the ability to attach scripts, or some metadata, to elements; layers or groups of layers. It's helpful when creating interactive SVGs. Of course it's possible by naming layer/group and edit the code of the exported SVG but it becomes repetitive when you open the SVG again and the code is stripped of the additional code. So the option to have some extra content in the code of an element and keep it intact on re-opening or saving the document, would be terrific. It does not have to do anything, just a field to type som extra attributes to the element and keep them throughout the workflow.
  3. I am using Affinity Designer to create file to upload into Cricut Explore Air2, to draw embroidery designs on fabric. If I export a png file, the image looks perfect but the Cricut treats each line as an object and outlines it - not what I want. I want a line drawing. After hours with Cricut tech support, I discovered that by exporting my file as an svg, the single line problem was solved, however, the image broke apart into single strokes and scattered over the page. I tried grouping elements in layers and then grouping all the layers together and the file arrived partially intact and the rest scattered and chaotic. I am attaching 2 screen shots. the first is the png file that is plotted as an outline by Cricut. The second is the way the file looks when uploaded as an svg file. (I know why some of the circles are filled in and know how to fix that) If anyone can advise me, I would be so grateful.
  4. Hi, I’ve been looking into an issue with parsing SVG files exported from Affinity Designer and have noticed that the ‘defs’ element is consistently exported after the referencing elements. While many SVG parsers assume order independence, it is considered best practice to write the ‘defs’ element before the referencing elements are described in 5.3.2 The ‘defs’ element as follows: “To provide some SVG user agents with an opportunity to implement efficient implementations in streaming environments, creators of SVG content are encouraged to place all elements which are targets of local IRI references within a ‘defs’ element which is a direct child of one of the ancestors of the referencing element.” Could you please let me know if plan to update your SVG export to incorporate this recommendation in a future release? Many thanks, Derek testwithgradient.svg
  5. It looks like Designer cannot import or export from/to the SVGZ format. I understand that it is simply a compressed version of a plain SVG document which I can compress / decompress myself but it would be more practical if Designer could handle that.
  6. It seems that Affinity Designer can't handle some of the SVG content in the digikam and showfoto logos. Text is lost "Lens glass" has different blur / transparency Shadow / blur around the lens is gone Sources of the files can be found at https://cgit.kde.org/digikam.git/tree/core/data/pics/digikam https://cgit.kde.org/digikam.git/tree/core/data/pics/showfoto logo-showfoto.svg logo-digikam.svg
  7. I am trying to export SVG files from Affinity Designer and bring them into a range of programs for generating tabs / notches and then outputting for laser cutting. In Adobe Illustrator it is very simple - you set the document units to mm, design something with specific dimensions, and export your SVG. What comes out will be interpreted by other software, and by the laser cutter at the exact dimensions. With Affinity Designer, I've spent hours troubleshooting and digging through the forums and no matter what I do dimensions seem to vary depending on the DPI and all sorts of other options, and even slices of objects with the same height will export at different dimensions. It makes it practically impossible to predict what size your object will be. (as an aside, I thought DPI was completely irrelevant to vector - why is it even an option in a vector format?!) So is reliable scale something Affinity Designer just can't do? How are people delivering documents for print if they don't know how the printer will interpret the dimensions of their final files? I dumped Creative Cloud, bought the Affinity hoping to replace AI and now am faced with going back to Creative Cloud and getting stung with higher fees as a result of leaving. For my line of work this seems like really simple stuff...
  8. Continuing from this post, I think it would be really cool to have a tab added to the export persona that would allow us to attach exportable attributes to layers, so that when we export an svg, all of our attributes for that layer are preserved. This would solve so many of the problems I've had whilst using designer. It would allow us to: Invoke svg filters defined externally Save class names on elements Add interactivity and styles Better yet, it would be cool to also use empty layers to add some svg markup to the final exported document, so we can define our own symbols, filters and the like. This would solve the issue I keep having (and no doubt others have had) while trying to use affinity designed svgs in production. If somebody asks me to change a colour, its always the same workflow: change color -> export -> make text edits -> repeat...
  9. I have a situation where I create an svg in affinity designer, and then I have to modify some of the resulting svg plaintext by hand. I would then like to open the exported svg into designer, make some changes and then save it out to the same file. The primary issue I'm having is that if I export a new svg, all of my edits are gone. Is there some way to modify an svg and leave all of the elements I don't touch alone?
  10. I need to export icons in an svg dialect which is compatible with Qt SVG plugin which means I don't want any clipPath in the generated svg format. Most of the time the SVG export works perfectly and my SVG icons are Qt compatible, but I came across one icon for which the export would always add the dreaded clipPath. I tried redoing the icon from scratch with the same result. Only one thing would solve the problem: relocating the icon elsewhere. It seems the export problem is related to the precise icon location. I have attached the file with the export issue as well as the good and bad export which can be generated from it (the same icon at two different locations). ExportBug.afdesign GoodExport.svg BuggedExport.svg
  11. Hi, I'm facing an issue when I export SVG with Affinity Designer. I'm working on a website and would like to export an SVG in the best way following some guidelines describes here : https://www.sarasoueidan.com/blog/svg-tips-for-designers/. My Issue : I want to export in SVG a shape and move it with code. When I export it, I get a <path d="..."> instead of a <polygon> or <rectangle>. Sadly I'd like to have a <polygon> object in order to move it with Javascript. Can anyone tell me what am I doing wrong ? I would like to do someting like that <polygon points="215, 110 0, 110 0, 0 47.7, 0 215, 0"/> But I get path like this <path d="M1920,0l-1669.99,0l-250.011,0l0,1200l1920,0l0,-305.211l0,-894.789Z" style="fill:#fa9090;"/> animation.svg pos2.svg pos3.svg
  12. this is something I am sure has been brought up about a year or so ago. but could not find it on here. SO this link here is how you can use inkscape to design levels in video games, parsing the SVG data in whatever you are using that can be used for collision, shapes & other such things I really think this would be a fantastic feature for designer, photo, or whatever affinity product that can have SVG output. please look at the link & see how it works & uses the data to build levels. its super awesome & would be even more awesome to have http://www.fierysquirrel.com/post.php?id=705 all the best
  13. Good morning, all. I am new to Affinity and also new to creating SVG files. I feel as though I’ve got the SVG file creation part down. Lol. This is what I need help with, and I will try to explain this by example: Lets say that I import a simple two layer SVG file into affinity. By this I mean, a transparent background (as displayed by the white and grey checkers) and a layer on top holding the vector (as displayed by the shape represented in black so that I can see the transparent background behind the shape). Let’s say that the shape is a black rectangle. Inside the rectangle I would like to write text. Then, I would like to make that text transparent so that it appears to have been cut out of the rectangle, so I can see the checkered transparent background where the words used to be, in the shape of the text. How do I do this? If you could describe it to me in simple steps and assume that I’m a total n00b, I would greatly, greatly appreciate it. Thank you so much for reading my post!
  14. When exporting a file to SVG from within Designer, for each layer or group having an opacity set below 100%, Designer automatically adds an extra, redundant, group just to apply opacity to: * Adding a group without opacity set less then 100%: <g id="myID"> <rect x="152.01" y="85.967" width="142.705" height="84.033"/> </g> * But when opacity of the group is set below 100%: <g id="myID"> <g opacity="0.5"> <rect x="152.01" y="85.967" width="142.705" height="84.033"/> </g> </g> This results in larger and more complicated SVG-outputs then necesary, but most importantly: it breaks the structure and hierarcy as meant by the designer causing all kind of problems when using the SVG for styling and javascript usages: interactivity and animations. Because suddenly there is an extra, unexpected level in hierarcy and the ID is on a different level then the opacity. That way webdevelopers can't trust the ID anymore. Instead the opacity should be applied directly to the group like visually done in Designer, keeping the structure the same as in the GUI and so meant by the designer: <g id="myID" opacity="0.5"> <rect x="152.01" y="85.967" width="142.705" height="84.033"/> </g>
  15. When the attached SVG is imported into AD, the second rendering of the path is not in the correct location. The SVG and a screenshot of the incorrect placement is attached. Thanks. sprite-search.svg
  16. When I take an SVG and scale it down, the exported resulting SVG seems to still use the original path, but applies a transform to scale the path down. Is there a way to cause the path itself to change to the new scaled-down dimension and NOT apply a transform? In other words, I want a new path scaled to the new dimensions, not the original path transformed to the new dimensions. Thanks.
  17. I've just started using Affinity Designer and so far I love it. When I export to SVG I get weird results. Circles get look like they are partially inside a black box, croped objects does not look croped. If I export to EPS everything looks fine. It also depends a bit on the app I use to view the SVG file. Finder in MacOS shows the SVG file as I expect when I preview them. But a bunch of other application does not. Please see the attached image. The symbol to the right is EPS and looks like it should. The symbol to the left is SVG and that's how it looks i most applications when I import it. I'm nor very familiar with SVG, I know there are different versions. Are there settings somewhere I could try or is this a bug?
  18. Hello Every one and first lets say: Affinity Designer is a great looking alternative to Adobe for working with GUI prototypes. My reason why I am writing this ticked is the issue that Affinity Designer is renaming the id entries from the original ones to some own unique ids, which I cannot use. The SVG file is a graphic which will be loaded in an application and get modified via JavaScript. For the correct functionality, each element (group) needs to have the right id name to its corresponding element in the graphic. I have noticed that Affinity Designer has replaced the groups ids into the ids from the text element inside the group (KDIFF3 snippet). Through the investigation, I recognized that the groups will be already removed in the application, as you can see on the objects list in attached screenshots - one from Affinity Designer, the other one from Adobe Illustrator. Is this a common issue with a known workaround? Do I have to change some settings? I haven't found anything relating to this. Best regards Denis
  19. Rightnow exporting to SVG has all styles inline on all seperate svg-elements. And elements don't have classes or IDs. Using SVGs on web and making interactive animations on a daily basis this way it's impossible to animate elements and use external stylesheets without having to manually add classes and IDs to each element and remlve all inline styling in a text-editor after each export. I don't like to say it, but that makes this workflow impossible to use. Having to stick to inline styling inside the SVGs is another problem: - These days inline-styling is a big nono and validators throw penalties if inline styline is being used. The preferred way is internal style department, or use with external stylesheets. - A lot of layouts use the same styling on multiple elements. With inline styling all these styles got copied for all elements, resulting in a way larger SVG file then needed because of a lot of repetitive redundant data. This can easely be avoided by adding classes to the SVG elements and having one style-rule inside the general section for each different style. That makes the export a lot more efficient and makes it easier for developers like me to just copy the generated styles and move them to an external stylesheet if needed. - When styling is in the general <style> tag inside the SVG, a developer only have to change 1 stylerule if something needs to be changed instead of having to change all objects having all the same inline-styles - Because there are no classes nor IDs added to elements, we are unable to animate the elements with javascript, or again, we have to add IDs to all elements we want to animate each time after an export... A little bit like the Adobe Illustrator advanced settings offer, but that could even be improved to keep the SVG output as small as possible: My suggestion would be to add this to the SVG exporter settings: - A checkbox to add IDs to SVG elements where the layer-name starts with an asterix ('#'), followed by the name of the layer/curve. That way we can decide wich elements get IDs so we can address these elements later with Javascript to animate and so on. And with this we also prevent adding IDs to all elements in the SVG (resulting in a large SVG file with a lot of unused, redundant IDs). And when no # is add to any layer, no IDs are being written to the SVG. So full control here I'd say. - An option to choose one of the following for the SVG Export: - Use inline styles - Put styling inside <style> tag (recommended - mostly resulting in smaller files and less redundancy) (Perhaps to be complete even a: - Put styling inside svg attributes (but not my taste ) ) When a user picks 'Put styling inside <style> tag' the elements get a class attached with the styling in the general <style> tag inside the svg. Long story short: for real / advanced usage of SVG on the web for web development, interactivity and animations (by css and javascript), these options are indespensable! It would be very much appreciated if Affinity developers could look into this! Thanks a lot!
  20. Looking at the SVG output at the moment SVG's always get a 100% width and 100% height, meaning they always scale up or down to a parent-window (in a browser). But there are a lot of usecases we don't want SVGs to scale on websites and if we do it would be nice if we could set how the responsiveness would behave, so to wich windowborder the image would stick and if we want to keep the aspect ratio while scaling. These are all very simple SVG attributes that only have to be added to the svg when we need it. Browsers are doing the rest. At the moment there is no setting in the SVG settings to turn the auto scaling (100% width/height) behaviour off in the SVG, meaning we have to manually take these attributes out of the SVGs each time we export an SVG if we don't want autoscale. It would be a lot easier, faster and less time consuming if we could just set these settings once inside the SVG export options to save it with our own preset. So what I ask for in the SVG export settings dialog is: - A switch to choose between using document width/height (keep size) or 100% width/height (auto scale) - A listbox to choose the 'preserveAspectRatio' attribute in the SVG so we can set this to: - none, xMinYMin, xMidYMin, xMaxYMin, xMinYMid, xMidYMid (the default), xMaxYMid, xMinYMax, xMidYMax, xMaxYMax (as described here: https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/preserveAspectRatio) These are important settings for exporting SVGs for Web and not very difficult to add to the dialog cause they only change 3 attributes in the svg tag. But they speed up the process of SVG exports a lot because these changes don't need to be made by hand in a texteditor after each export! Thanks!
  21. Hello, I have a strange issue: exporting SVG as usual to be used on websites, Designer makes a font/svg file instead of a image/svg+xml file. This makes the file unusable in my WP websites. I already compared the SVG files text using TextWrangler but they seem equal. I attach one of them for analysis. What do you think the problem could be? Thanks for your support. LovelyApart 2018.svg
  22. I am aiming to export SVG files with 12 point text (in Affinity) where that text is the same size as the 12 point text in the HTML where the SVG is embedded. As you can see, the text in the SVG and PNG is smaller that the text in the HTML above it. The HTML <!DOCTYPE html> <html lang="en" dir="ltr"> <head> <meta charset="utf-8"> <title>Test</title> <style media="screen"> * { font-size: 12pt; font-family: "Open Sans"; } </style> </head> <body> <p>This is a test of SVG sizes from Affinity Designer.</p> <p>The font on this page is 12 point Open Sans Regular.</p> <p><strong>SVG</strong></p> <p><object type="image/svg+xml" data="1.svg">Your browser does not support SVG.</object></p> <p><strong>PNG</strong></p> <p><img src="1.png" alt=""></p> </body> </html> The SVG <?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="400px" height="300px" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" xmlns:serif="http://www.serif.com/" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linejoin:round;stroke-miterlimit:1.41421;"> <rect x="0" y="0" width="400" height="300" style="fill:#f2f2f2;"/> <text x="10px" y="19.117px" style="font-family:'OpenSans-Regular', 'Open Sans', sans-serif;font-size:12px;">This is 12 point Open Sans Regular.</text> <text x="62.674px" y="162.808px" style="font-family:'OpenSans-Bold', 'Open Sans', sans-serif;font-weight:700;font-size:52.831px;fill:#fff;">400×300px</text> </svg>
  23. As SVG is open source I would appreciate that Affinity support SVG files without having the need to import or export the file. Regards. Camille Desmots
  24. Hello, I have exported two SVGs in two different ways. I am running 1.6.1 on OSX and have some issues 1. via MATLAB - This imports fine but there is a curve mask which covers the real content of the image. I can delete the mask, but its pretty annoying to have to do this, and I spent a good half an hour trying to figure out if my image was even there. 2. via Python (using matplotlib) - The file is 50mb, not sure if this is the issue...but basically Affinity designer just hangs indefinitely. The plot was generated with https://matplotlib.org/api/_as_gen/matplotlib.pyplot.pcolormesh.html which I believe increased the size. (This is a big issue for me) - Smaller plots which just include a basic contour plot work just fine.
  25. Hello world, Affinity designer has taken me out of complete design noob into semi noob. Any help would be greatly appreciated in this trying time.. In summary, I need to create single line strokes out of some curves/shapes that i've made. I have taken a font, built a shapes over the letters, now I have shapes with hundreds of nodes. If I have the shape of a "P" consisting of dozen nodes, is there anyway to represent that by two single stokes. EG. One stroke for the " I " another for the ")" Any advice or further reading materials would be excellent, although, explicit instructions would be superb. Thank you world, Adam (It's to be used with the following if that's any help) https://maxwellito.github.io/vivus/
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.