JimboJones

Thanks, I’ve just sent you the palette. I think what we need for global colours is an initial color space. When I create a colour in CMYK, I want to keep the exact values, as long as I work in a CMYK file.

Mostly I just want assign a profile to match it with the print shop's profile. Having an already pressed convert button doesn't help here when all I want is change the profile, not the color values. Maybe this is just a UI thing that needs to be solved. But other than that, the initial problem described above is the bigger issue. Nonetheless, thanks for your help!

Well, I interpret it as a setting. It is actually in the "settings" dialog. Also, the "convert" button is in the pressed state, telling me that this is the current behaviour. Also, no way to keep the assign button in the pressed state.

Hi Callum, thank you! Is there a way to provide it non-public (as it contains client information)?

In V1 I created a system palette for my most important client corporate colors in CMYK. When I created a new document in CMYK would go the system color palette, pick the color and had the correct CMYK values in my document. In V2 I experience a weird color shift, making the whole color palette nearly unusable. Whenever I chose a color, most of the values are wrong. Let's say I have saved a CMYK color with C50 M90 Y10 K0. When I use it in a new document it changes to C78 M97 Y0 B0 which creates drastically different color. When I reedit the saved color in the system palette, it works for some time, but the whole thing is far from reliable. Also there is a problem with color profiles. When I chose CMYK/8 and my profile ISO coated V2 for example, I want to chose "assign" to keep my exact color values. But when I click "ok" to leave the document settings and go back to them later, it is switched back to "convert", so no chance to chose "assign". Maybe the relates to my initial problem? Has someone else experienced this?

Hi there, here is what happens: I create a text frame and put in a few paragraphs of text. Then, I select one paragraph and change font-size, for example. Now, the weird thing happens: As soon as I click the move tool (v), ALL paragraphs are changed to the text settings of the one that I wanted to change. This is so annoying. If I wanted to change all paragraphs, I would have selected them all. It doesn't happen if I just click outside of the textframe while still in texframe tool (t). This behaviour still appears in version 2 as well. I guess it's a bug. Bug baybe I'm just missing something or there is a hidden setting somewhere? Cheers, Christoph

Ok, I gues I know what the problem is and have a workaround. And an idea for improvement, as well. Here are some steps to recreate the initial problem: If you draw a rectangle, path, whatever shape with integer values, they are exported to SVG as expected (with integer values in SVG). As soon as you start transforming your rectangles/paths a transform matrix is added to the SVG (NO integer values in SVG!) You can flatten those tranforms in export settings, but doing so won’t bring back integer values to SVG. So, the problem is, when you transform an object, the transformation factor seems to be saved somewhere. This info is then used for the transform matrix in the SVG. To solve this and erase the transform information you can join your shape with another shape and you get back your integer numbers without transform matrix (when exporting to SVG). A better solution would be to add a visual cue, some form of indication to the transform panel, wether a shape is transformed or not. This way you could see that your current shape is transformed in some way (scaled 1.5, for example) and provide an option to reset the value or to use the current transformation as new default. Would be great if someone could pass this to the dev team, Thanks! By th eway, @jc4d asked for something similar a while ago, I guess:

No, No, still weird numbers all over the place. I did some further testing. I guess it all has to do with transforms. If I draw new lines, nodes etc. they all are exported pixel perfect. If I don't flatten transforms, there are no transforms in the SVG. Maybe there are some transforms saved in the background somewhere, messing up the numbers?

I define a path in Designer like this: One point is on 2.000 px from top 5.000 px from left. After creating the SVG I get numbers like 12.234 or 4.114. I know that the numbers change as SVG works different when creating paths. But I'm missing the ability to achieve precision. It doens't matter if "flatten tranform" is activated. The numbers just don't correspond to the original. This leads to an imperfect svg that doesn't align to the pixel grid as expected. Also, as mentioned above things like clip paths I didn't create in my Designer file, but are there in the SVG. Maybe we need a preference in the SVG export where you can define the decimals. Or a general "save SVG for Web" that reduces some of the not needed complexity. Figma wrote about that https://www.figma.com/blog/with-figmas-new-svg-exports-less-more/. Maybe this helps for some future updates

Ok, this is because I copied the art board to a new file and didn't change the resolution. But this doesn't change anything to the output. Even if I transfer everything to px values everything gets messed up in my SVG

cz-logo.svgcz-logo.afdesign Thanks for your quick reply! Here is the requested file, alongside the corresponding svg I created from it. I did, they are exactly corrent with three decimals, eg 60.000 pt

Hi there, I have some problems exporting SVG for Web. I created a 60px x 60px art board and drew a pixel perfect icon. I set units to 3 dedimals in preferences. Now comes the export mess: 1) The viewport in the SVG is set to width="60px" height="61px" Why? 2) Every path gets a transform matrix. WHY? If I flatten transforms then there is a mess of calculated numbers that doesn't fit the initial positions. 3) I get a clip path although there is noone set in my document. With als this there is no chance to get the icon perfectly aligned on a pixel grid. What can I do about this?

I have the same issue on Mac, Catalina, running Designer 1.8.1. I can't see any grid smaller than 4 px. Also, the automatic grid disappears when zooming in. Makes the grid quite useless if you want to achieve pixel perfect work. UPDATE: Looking into the bugs board I see developers are already aware of …

Guys, honestly, this shouldn't be an issue still in 2020.

This is pretty anoying. If I uncheck the "snap to baseline grid" in the paragraph settings, I'd asume that the baseline grid is ignored for that paragraph and vertical alignment works corrently, then. To me quite some time to figure out …