Hi, I have been testing TOMSMorphingLabel and after some time displaying the label I got memory warnings. I looked at the memory usage and I saw that it was increasing all the time. Although the increase was slow, it ended up giving me a memory warning. Changing the label to a normal UILabel make the problem go away so I think TOMSMorphingLabel is the one that is leaking.

Anyway, nice work.

Hi! I suppose TOMSMorphingLabel should also respect the global areAnimationsEnabled flag of the UIView class so that setting the text like this:

[UIView performWithoutAnimation: ^{
     tomsLabel.text = @"new text";
}];

will actually set the text without animation as expected.

The same goes for the following:

[UIView setAnimationsEnabled: NO];
tomsLabel.text = @"new text";

As per documentation for setAnimationsEnabled:, if we disable animations, the currently running animation blocks will continue, but subsequent animation blocks will perform without animation. So checking the [UIView areAnimationsEnabled] state in the isMorphingEnabled getter seems reasonable enough - it won't affect the already started animations but will prevent new ones to start.

Hi, thank you for your awesome lib.

Do you know how could we increase performance ? When animating 2 labels simultaneously, I get a decrease in frame rate.

Thanking you in advance.

Hello! Ported your awesome component to iOS 6. The changes are actually very simple. Since the new iOS 7 APIs are wrapping existing CoreText functions, it was a matter of simulating what happens behind the curtains.

The precise method probably incurs in more overhead than the iOS 7 API it attempts to reproduce, but that's what the public APIs allow. The quick'n'dirty method is probably good enough anyway.

In any circumstance under the simulator the iOS 7 version runs much quicker than the iOS 6 one. That's not a limitation of the overhead: even the QnD version seems slow, and if the foundation guard is taken away and the CoreText method is run unconditionally, the iOS 7 animation speed is the same as before. So there's something weird with (simulated) iOS 6 that's probably not even worth tracking down.

Anyway, great job, and hope you like my contribution!

Hi, I've implemented a simple solution to the retain cycle problem described in #12. Please tell if that works for you.

CADisplayLink retains the object set as its target and TOMSMorphingLabel references the display link strongly. This gives a strong reference cycle and TOMSMorphingLabel is never deallocated. This PR adds a helper class named TOMSMorphingLabelWeakWrapper which holds a weak reference to the label and forwards necessary messages to it. This breaks the reference cycle and allows deallocating the label.

Note that if the weak wrapper's label reference gets nullified due to the label being deallocated, the display link would continue firing its events to the weak wrapper. So it is necessary to properly invalidate the display link in the TOMSMorphingLabel's dealloc.

Hi! I think the completion block of setText:withCompletionBlock: should be called regardless of whether we're setting the text with animations or not.

When a method with completion block is called, it is kind of assumed that the block will be executed at some point. Otherwise we cannot really know whether it would be called or not without checking the isMorphingEnabled property.

If the text color of the label changes, the animated characters will stay the original color during animations. During the attribution stage, the current color of the text is applied to the attributed text so that that the animated changes are the correct color.

You can use this mod to add the morph to a button label. (I use it for cross-language apps).

• (void)toggleTextForLabel:label1 { NSLog(@"toggleTextForLabel"); self.label1.text = @" "; //cleans out prior label self.label1.text = textValues[self.idx++];

  dispatch_after(dispatch_time(DISPATCH_TIME_NOW, (int64_t)(4 * NSEC_PER_SEC)), dispatch_get_main_queue(), ^{ [self toggleTextForLabel:self]; [button1 setTitle:self.label1.text forState:UIControlStateNormal]; }); }

I saw that the animations are very slow on my iPhone 5 (no problems on my iPhone 7+) and then I tried out the example from the website: those animations ran smoothly as expected.

@tomknig, I've corrected a typographical error in the documentation of the TOMSMorphingLabel project. Specifically, I've changed configureable to configurable. You should be able to merge this pull request automatically. However, if this was intentional or if you enjoy living in linguistic squalor, please let me know and create an issue on my home repository.

1. It's more conventional to define external symbols for constant strings.
2. Adding IBInspectable to the label's properties makes it configurable from interface builder.

Xcode 14.1, iOS 16.1

When the TOMSMorphingLabel is set to use the system font, there is a flash of a serif font (looks like Times New Roman) during the animation. Workaround is setting a custom font.

This updates the library to support Swift Package Manager.

To do this, I rearranged files in accordance with the traditional Swift Package Manager structure:

Source files reside in a folder named Sources and are scoped per Target. A Swift package can contain several targets, and, as a convention, each target’s code resides in its own subfolder.

Other notes:

• Objective-C headers were moved to Sources/TOMSMorphingLabel/include, to be found by SPM by default.
• The example project's use of Cocoapods was removed and replaced with use of SPM.

I need to change font but I see an old font in animations. I fixed it, but can't create pull request.

-(void) setFont: (UIFont*)font
{
    [super setFont: font];

    @synchronized(self)
    {
        for (NSMutableDictionary* attributionStage in self.attributionStages)
        {
            UIFont* prevFont = attributionStage[NSFontAttributeName];
            attributionStage[NSFontAttributeName] = [UIFont fontWithName: font.fontName
                                                                    size: prevFont.pointSize];
        }
    }
}

Over the last days, I have tried to port this class to OS X. The problem is that CADisplayLink is not available on OS X. Its counterpart, CVDisplayLink should work, but I was not able to get to a working solution.