Problem is, we need to exclude the accidental triggering of these functions. In other apps, that is too easy. How can we make sure slanting and rotating is enabled only when it is clear it is the user’s intention?
I still think there must be a more distinct way to differentiate it, more distinct than in AI. As opposed to vector illustration, in type design, scaling is frequent, but rotation and skewing is rather rare, so accidental triggering is an issue. We are discussing solutions internally.
Yes, skew is more rare though I use rotate a reasonable amount while getting the main shapes in order. I also use Glyphs for lettering projects too which benefit from quick controls.
As designing type is an accurate task I would say the designer’s use of the controls reflects this. So maybe keep the proximity quite tight and, like many of the extensions enable the user to toggle on/off in the view menu.