loukash

Because that's what manuals are being written for…? A self-respecting professional software user reads manuals – if available – to learn all those nifty tricks that may be intentionally hidden from the surface in order not to distract novice users. Perhaps it's just me, but that's how I've been proceeding in the past 35 years of my DTP experience. (Although, back in 1989 I didn't have a user manual for the PageMaker 3 that someone installed on the Macintosh SE/30 in the public university library, and it took me quite some time to figure it all out by myself, without any former computer training while I was at design school…) Once I have looked it up (in Ash's post above, as it's not in the manual yet), it appears totally obvious and intuitive to me. But again, perhaps it's just me… And you still can. It hasn't been taken away.

That's why it will be very likely mentioned and described in the user manual, once the feature has been finalized. Because e.g. I, for one, also don't remember every field input expression by heart, even after all those years, and may need to look them up every now and then…

Those numbers don't mean anything. Or is there a Worldwide Versioning Standard Committee® whitepaper which every developer must painstakingly follow otherwise they will be removed from their License To Develop™…?

Definitely a bad decision… My take on this still stands:

Still not fixed, obviously… ^ Just checked using my above test stroke which I have then saved as an asset.

Some issues on Mac here: the popover panel should not float above the modal dialog (even though the latter is movable) descenders are cut off with UI Large Font (a.k.a. what's a Cateqorv…?! )

This has been a general issue with the pressure feature since it was introduced in v1. In that sense, the new Line Width tool is apparently "only" a different front end to what's been there for a long time and only editable via the Pressure curve until now. But at least it's more convenient. (Considering this, I can't say that I'm overwhelmed either… )

For closed curves, it's a Good Thing™. Perhaps the profile panel should be a bit smarter and differentiate between closed and open curves. Agreed

Of course! But it was off topic anyway, hence in parentheses.

(Also, I'm in fact still eagerly waiting for exactly the opposite: a roughen effect à la Illustrator… )

This please!

Another option would be using overprint swatches when possible: Once I also tried another weird experimental trick by using Symbols and Linked Layers via Designer and Photo personae: apu_pinned_in_background.mp4 That all said, not being able to simply place pinned objects behind text is a serious omission.

It's a MacOS security feature. Not a "bug".

Probably you have accidentally enabled View → View Mode → Pixels

As noted, that is a "limitation" of e.g. InDesign as well: The layout app expects to find an image file at the saved location (which by itself is already a kind of "alias concept") to replace the saved low-res preview with the original image data on the fly. But instead it finds a file of the same name that doesn't contain any image data whatsoever. For a layout app, that is a "corrupt file". Therefore the asset must be relinked to the alias so that the layout app is now told by Finder where the original is stored. It's a limitation of the Finder alias feature. Some apps can't handle Mac aliases at all but may work with Unix symbolic links instead. Other apps have it vice versa. I've been doing lots of alias/symlink trickery in the past decades, and often it's been a hit-or-miss.