PPPeter

When changing colour profile in document setup one would think that "Assign" keeps the set CMYK values and "Convert" changes them to the new colour space. But this is not the case, both settings changes the CMYK values. How do I assign a colour profile without changing the values?! Also; if I copy an object from a document with one colour profile to a document with a different colour profile the CMYK values change. This is not how colour profiles should work. In the most common workflow is that you design stuff with set CMYK values and assign the colour profile the printshop wants. I can see the point of being able to convert colours but this is not something you do most of the time.

I would say it's a big difference since the invisible, clickable, area extends outside the bounding box. If you have a 0 opacity rectangle the bounding box would show exactly where the rectangle is. In the text box the invisible area is totally unpredictable. This error was introduced in v.2 and I have a hard time thinking it is by design since it's not consistent with how other contained objects work.

I don't know if you misunderstood the topic but the problem is not the bounding box only showing the visible text, have a look at the video again. The problem is that it acts like the invisible rows are there, the invisible part can cover underlaying objects. If you click the invisible part of the bounding box the box get selected. It can surely not be by design that if you click a random space in your design that accidently is covered by some invisible, non-predictable object is selected instead? It is only text that has this behaviour but if it would be by design this would also apply to objects cropped by a rectangle for example, no?

Not fixed in 2.1.0 😔

If an artistic text object has empty lines at the end the bounding box only shows the visible part. The same goes for v1 but in v2 the invisible part can overlap other objects. Designer_wIigBqIOLy.mp4

+1 Still not supported in v2

Currently it's only possible to set export name, path and variables per slice. It would be a huge improvement if you could set general values for all slices, like Illustrators prefix and suffix settings. One way would be simple prefix and suffix fields in the export options tab, or there could be a project wide path constructor for all slices with user variables and path components like document name, date, incremental counter (for versioning) etc. Even an option to add incremental numbers instead of overwriting, like when you download files with the same file name, would be something. Disappointed to see that this is still missing in export persona in v2 In fact, it seems like export persona did not get any love at all in the update.

Disappointed to see that this is still missing in export persona in v2 In fact, it seems like export persona did not get any love at all in the update.

Wonder why they removed the public roadmap...

First of all; nice work with all the improvements and functions. Still I found that a few (for me) key functions are missing: Export persona still has no general suffix or prefix options for all slices, no version label or the possibility to save a project file path. Palettised png export is still totally worthless, in both quality and file size, and you are much better off taking the trip around pngquant/TinyPng with your 24-bit version. (TL; DR: a 350x500 px image: 24-bit: 78 kb, jagged, ugly, 256 colours: 36 kb, jagged, ugly, 128 colours: 31 kb, pngquant 128 colours, indistinguishable from 24-bit: 22 kb.) Envelope/mesh distortion, or any kind of free distortion, of vector objects. You can find threads about this being in the roadmap since 2016 but still no word about implementation from dev. Funny thing; they use a distorted text in the promo for 1.8:

Currently it's only possible to set export name, path and variables per slice. It would be a huge improvement if you could set global values for all slices, like Illustrators prefix and suffix settings. One way would be simple prefix and suffix fields in the export options tab, or there could be a global path constructor for all slices with user variables and path components like document name, date, incremental counter (for versioning) etc.

+1 I'd also love to see a version component for the path so that slices don't get overwritten. It's good to know what version you send to clients. filename.png filename(1).png filename(2).png