Jump to content

mocny

Members
  • Posts

    10
  • Joined

  • Last visited

  1. Well, it definitely feels as a bug, altough designed to function as is, it is unnatural, so that is why I considered it a bug and still do. In case of bigger documents it is very cumbersome and unnatural to use navigator, that is why I ditched it completely. If you are able to move this into feature request, feel free to do that.
  2. I am having much difficulty making SVG animations according to my needs, because Affinity removes redundant nodes (e.g. nodes laying on the straight lines). I need all of the nodes I use and transform for SVG to animate properly, so removal of redundant nodes needs to be OPTIONAL! and not mandatory. Check the files. Reproduce: export the attached file with `flatten transforms` and `add line breaks` checked as 2 files: 1. one with the 'redundant' node/point on the left arm 2. one without it Both of the files produce same amount of coordinates, but the first one should be having one more, if we would have option to uncheck `Remove redundant nodes`. redundant-nodes.afdesign
  3. Bug in every app: Scrolling with mousewheel inside navigator does not respect position of the mouse inside navigator panel view, but it is using position of the mouse of the whole affinity publisher application. It should work either like manual zoom input > zooming in/out centered on actual view or zooming based on mouse location inside navigator panel.
  4. 1. Exporting rectangle with radius or circle to SVG, produces path element and not rect/circle with their's attributes. This, in case of multiple objects, creates a lot of unnecessary code = bigger size & heavier load & also a file, that has lost compatibility with (any) software, to edit afterwards. 2. I would also appreciate some support for adding "classes". Just to have some checkbox in SVG export panel like: Treat same layer names as "class" instead of "id" So as no to add numbers, if there are layers with the same name, but it would convert "id" export tag into "class". If the layer name would contain more words, it would add multiple classes. This would be a great help in creating SVGs that could be manipulated. Maybe also possibility to check on/off "ids" would be nice. Or even better would be to have just option for typing it into layer name such as "#idname .class1 .class2" and SVG exporter would handle the rest. 3. Last one would be to have a look at gradients. When there is one and the same gradient, it creates multiple <linearGradient> instances in <def> since it adds also longer gradientTransform attributes. I do understand, that Affinity uses specific coordinates for this (matrix), since gradient can be positioned outside of the object, but if not, and gradient tool is inside the edges of the object, this could be exported as a can be seen in reference manual on mozilla or example on this tool, just with x1/y1/x2/y2/rotation (etc. depending on gradient type used as can be seen in the tool mentioned). This would also make code more easier to read & edit & also more compatible. Thank you!
  5. AFD-1907 I also need this fixed ASAP. The glyphs can be found in "Glyph Browser" in fonts like "Arial Unicode MS" or "Tiro Devanagari Sanskrit" so I am sure, there must some way to fix this. Please bump this up. It is unacceptable, that this hasn't been fixed since V1. Ligatures need to be working properly in any graphic software like Affinity products, otherwise we will be kept stuck. I am actually using MacOS, but this isn't OS/app dependent bug, it is faulty also in iPad and same on Publisher/Photo.
  6. in this video you can clearly see where the problem is... when you use eyedropper drag function and not eyedropper tool directly it works partialy however... I am saying partially, because the change of sampled color wont take effect in specific gradient POINT and there is still some default RED ugly color in that sampler... so I hope all is clear now affinitybug.webm
  7. actualy it works at some points so I need to make a video what I am talking about indeed...
  8. I am repeating myself guys... sampling color wont change inside SAMPLERS that are located deep within Gradient or Stroke SAMPLERS... I am not talking about actually changing the color of Gradient or Stroke, I am indeed talking only about sampling... again, eyedropper is in multiple places inside the product, as there is that small sample circles and no matter which eyedropper I will use, the color should change in ALL OF THE SMALL circles right? or at least in my opinion should, because you may want to use that sampled color again in STROKE for example, but lets say you have sampled some color for use in GRADIENT... you guys are talking about changing actual color, thats not what I am talking about
  9. You didn't get my point, please re-read the ISSUE carefully again as I wrote it. IN SHORT: Picked color should be changed in all of the windows, not only "Color" panel swatch, but all of the Color Picker Swatches in whole Affinity product. It is clearly understandable from the picture provided.
  10. There is a bug in Affinity (whole 'family' - Designer, Photo and also Publisher), where sampled color won't relfect change inside FILL/STROKE window. This is mostly relevant (and needed) to the gradient tool. Sampled color won't change inside specific color of gradient tool. 'Drag picking' does work, so it is possible to do it this way, however, if I picked color from different place of document at some point, it is a problem and I would need to select the object that I want change the color of first and only then navigate to the place of the color needed. Also another bug is that there is default red sample, which doesn't matter, but is kinda odd , but will be resolved with fixing this anyhow. EXAMPLE: As you can see in the picture, I sampled yellow color inside document, however, this sampling doesn't reflect inside Fill/Stroke, which should. PS: I am kinda missing in this forum another sub-forum for bugs that are relevant for whole 'family' (?) and not app-related as there probably are cases as this one. I am using latest version 1.7.1.404 on Windows 10.
×
×
  • Create New...

Important Information

Terms of Use | 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.