Hoi.
I have a project with a custom font of my customer. Whyever the client wants
theirs font in some typos (strings/labels/buttons on screen) to be compressed
by 20%.
Compressing in this case means that the glyph/character (Latin1) should be 20%
smaller in width than it is in the font.
I digg
On Sep 30, 2014, at 3:04 AM, Hado Hein wrote:
> I have a project with a custom font of my customer. Whyever the client wants
> theirs font in some typos (strings/labels/buttons on screen) to be compressed
> by 20%.
>
> Compressing in this case means that the glyph/character (Latin1) should be
Thank you, Kyle. :-) I’ll study the bit about using a custom pasteboard type.
On another strange note, I followed the quick start program in the Collection
View Programming Guide last night, using Swift, and it up and worked! I really
stressed over finding the syntax for the four KVO methods,
Thanks, Dave. I took a similar route myself for debug builds, to test that my
UI was behaving correctly. I just was hoping that there was a more "official"
way to test it so that the payment queue was fully in charge.
On Sep 29, 2014, at 2:33 PM, David Brittain wrote:
> The best I could come
One of my big gripes with the Mac or iOS text system is the lack of a real
super/subscript attribute. I haven¹t tried doing custom attributes. Is it
possible to define and use custom super/subscript attributes which combine
the normal baseline shift attributes with NSExpansionAttributeName to get a
your client must be very aesthetically oriented to have had a custom font
created; they would more likely be happier having a compressed cut made, as
well: algebraic adjustment is just distortion. however, if you would like to
control compression/expansion algebraically, you may wish to investig
Is there a way to incrementally adopt auto layout with storyboards? I have
a storyboard with a large number of scenes. If I turn on "Use Auto
Layout" for the storyboard then all scenes are using auto layout (which
makes sense). Is there a way to not use auto layout for some of the
scenes? For exam
Hello everyone. This seems to be an upside-down question, but bare with me...
Our Mac Client-side application can (sadly) only be built and run in
32bit-only. Reason is: bit parts of it are legacy 32bit-only C++ code shared
with other platforms (Windows, Android, Linux, etc.) client code as well
On 30 Sep 2014, at 20:49, Motti Shneor wrote:
> Hello everyone. This seems to be an upside-down question, but bare with me...
>
> Our Mac Client-side application can (sadly) only be built and run in
> 32bit-only. Reason is: bit parts of it are legacy 32bit-only C++ code shared
> with other pl
On Sep 30, 2014, at 1:04 AM, Hado Hein wrote:
> Hoi.
> I have a project with a custom font of my customer. Whyever the client wants
> theirs font in some typos (strings/labels/buttons on screen) to be compressed
> by 20%.
>
> Compressing in this case means that the glyph/character (Latin1) sh
> On Sep 30, 2014, at 12:49, Motti Shneor wrote:
>
> Hello everyone. This seems to be an upside-down question, but bare with me...
>
> Our Mac Client-side application can (sadly) only be built and run in
> 32bit-only. Reason is: bit parts of it are legacy 32bit-only C++ code shared
> with ot
I have a complex migration that uses a combination of MappingModel and
Migration Policy. From version 5 to 6, it seemed to work fine. I've duplicated
the policy to make a version 5 to 7 policy, which is virtually identical
(there's a single new relationship). But when I run through the migration
I tried using NSExpansionAttributeName when sending a NSAttributedString to
CoreText, but it didn’t work. Docs say it should be a NSNumber of the log of
the expansion factor. This is confusing because log normally means base 10,
except that in C it is actually ln() (Naperian). Either way, it had no
13 matches
Mail list logo
