Search the Community
Showing results for tags 'afd-867'.
Found 4 results
I've a series of diagrams I have produced in a single Designer file, on separate artboards. The diagrams are related in a series, so it is easier to produce them in sequence. I am however having difficulties adding them to a Publisher document using the picture insert tool. I've attached one of the designer files and corresponding svg files in the hope someone has an idea what is going wrong. If I save a Designer file for each individual diagram, the diagrams are on the whole as I would expect, except I am experiencing an issue with items outside the artboard being visible. If I export the individual diagrams as SVG, they look fine when viewed in a web browser. However, place them into a Publisher document and something rather bizarre is happening. The diagrams are made up of numbers of layers of the same elements - often in the same location, with the upper layers cropped so the whole thing replicates 3d knitting. The whole thing appears flattened, and it looks like the cropped layers are removed. I'm not entirely sure whether there is a better way to do this, or if there is bug or two causing the issue. Any help would be appreciated. I'm working with 18.104.22.1681 for both software packages, though the Publisher document was started with the previous release. 3 round bobble for publisher.afdesign 3 round bobble #1.svg
So, I generated this SVG file in Affinity itself and saved everything perfectly; as shown in the Opera view and also when I open in Inkscape, the SVG file is working perfectly (attached prints); only that, when I re-open the SVG file in Affinity, the layers that were one inside the others - to generate the format of the photo - get lost; they remain in the file, but as if they were hidden below the photo. I guess it's not intentional and, as seen, I'm reporting it as a bug. Thank you, guys
Affinity Designer appears not to import the following SVG correctly: the `transform` on the `g` element is not being applied to the `clip-path` on the `path` element. <?xml version="1.0" encoding="UTF-8"?> <svg xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" viewBox="0, 0, 200, 100" width="200" height="100" xmlns="http://www.w3.org/2000/svg"> <defs> <clipPath id="c1"> <path d="M 50,5 5,50 50,95 95,50 Z"/> </clipPath> </defs> <g transform="translate(50, 0)"> <path clip-path="url(#c1)" d="M 20,20 20,80 80,80 80,20 Z" fill="blue" stroke="red" stroke-width="5"/> </g> </svg> I tried to find how W3 spec says these attributes are supposed to interact, without success. However, Safari, Chrome, Firefox, Sketch, and Graphic all applied the transformation to the nested `clip-path`, and I did not find any other applications that matched the behavior of Affinity Designer.
Hello, I have downloaded the trial version and have to say it is very nice. I loaded my current tvOS projects character SVG which has about 110 frames of character animations. Each frame comprised of about 30 elements. So a good test to compare to Inkscape 0.91 for performance. System is fairly maxed out 2011 iMac. Pros: Wow it is fast and scrolls in and out so smoothly Using the same keyboard shortcuts as the rest of OSX is nice as well Near perfect import of the test SVG (see cons for issues) Easy to use so far Awesome export options Cons: Clipped & Masked items in the test SVG did not import clipped or masked. This is actually quite a mess to have to clean up by hand. Color picker eye dropper was not nearly as intuitive to use as pretty much any other apps I have used. The click & hold then move selection area to color felt very awkward. Much prefer the select tool then move to area and click on color desired style eye dropper tools. Not so happy with the path node tools either. Enjoy having control arms on all three types of control nodes in Inkscape. Questions: 1. Is there something I am missing to fix the problem with Clipped elements on SVG import? I use this technique often in Inkscape so getting this right on import is important. Just to much work to fix it all by hand on every image and if I can't bring in all my old art it negates the value of moving to AD from Inkscape. 2. Is there a way to get a color picker that works more in line with the select object, select tool, select color (like inkscape) with out the need for the click/hold/drag AD uses? Being new I bet I missing something here. 3. Path node control arms for all nodes types would be nice, so am I missing the obvious on how to get them to appear? 4. I know they keep this tool up to date so I will ask about PNG export without transparency (Alpha). Anyone that is developing for Apple knows that they have moved several items to no Alpha channel and that they prefer PNG format files. The latest is Image Stacks for tvOS apps require the back most layer to not have any Alpha. So could that becomes a PNG export option? I ask about PNG because it is easier to keep all images in the same format vice a mix of PNG and JPG files. Also right now Apples tool chain for image stacks is young and mixing PNG/JPG in the stack has resulted in fun and for me it being easier to use Preview to fix the alpha channel as required and stay all PNG files. 5. Speaking of tvOS will there be an Export option to create the Parallax Images (.lsr files) added at some point? I have an idea on this might be done. Special template with 1 to 5 layers (range that Apple's LSR format allows. The export option would export each layer into the LSR file (layer 1 being back most) and then counting up from there. It would sure be awesome to have something like this for AD given that Apple released a plugging for PhotoShop to do just this. Again great product. Loving the trial version. Besides the clipped and masked objects not importing correctly I am thinking this is a clear move from Inkscape for me. Look forward to hearing back. Matt