Nick
My feedback
6 results found
-
4 votesNick
supported this idea
·
An error occurred while saving the comment -
7 votesNick
supported this idea
·
-
28 votes
we have made note of this feature request and added to backlog
Nick
supported this idea
·
-
33 votes
As per the comment, go to 'Preferences > User Interface > Share Button' and select 'Match Brightness' — it will no longer appear blue.
To achieve the same in Photoshop, try toggling 'Neutral Color Mode' in 'Preferences > Interface'.
If you still wish to just have it gone for good — please upvote this separate request.
Nick
supported this idea
·
-
28 votesNick
supported this idea
·
-
2 votesNick
supported this idea
·
.png){kind=link}
.png){kind=link}
.png){kind=link}
Greetings from the person who made the HEX Franklin font family.
The original poster, Charlie, reached out to me about this issue, and after a long time doing some debugging with Frank Grießhammer from the Adobe Type team, we figured out what the issue is. I've already updated Charlie about this separately but I figured I would post a comment here in case other people come looking for info on the same bug.
Here's the situation …
There is a new bug that breaks how some variable fonts work in Adobe apps. The fonts may not show in the font menu at all, and if they do show, selecting them either results in a blank text field or a fallback to another font.
The issue is apparently tied to how Adobe apps and CoolType's font picking mechanisms interact with the latest versions of macOS. It seems to be affecting CFF-flavored variable fonts specifically. (I was somewhat relieved to find it wasn't just my own fonts that were affected due to some error on my part, because it also affects Adobe’s own fonts – e.g. the CFF/OTF version of Source Serif 4 Variable also suffers from the same issue.)
Frank reports that some Adobe engineers have addressed the issue already, so it should hopefully be fixed in their future app updates.
In the mean time, it's possible to work around this issue by installing the affected fonts into the Adobe-specific fonts folders instead of macOS's system fonts folders (as described here: https://glyphsapp.com/learn/testing-your-fonts-in-adobe-apps ). Fonts in those folders don't seem to be affected by the bug.
Thanks to Frank for helping me figure this out. And also thanks to the Charlie for reporting the issue in the first place!
I'm hoping the fixed version of the Adobe apps will be available for Creative Cloud subscribers soon.