Hi,

I'm having a very strange problem: the empty data set moves to a different position after some data have been available for a controller and then were removed.

The screenshot below shows what I have in mind:

The empty data set first appears as on the left screenshot. Then, after adding and deleting some data it appears as on the right screenshot.

I do reload the view in viewWillAppear.

This is only a minor issue but do you have any ideas on why this might be happening?

Cheers,

Pawel

Since userInteractionEnabled is set to YES on emptyDataSetView, all touches to views underneath are blocked.

This is probably fine for the majority of cases, however I have a header in my UICollectionView using a supplementaryView. Even though the main content is empty, there are still actions that need to be performed from the header. Touches to the supplementary view are currently blocked making it unusable.

It would be great to have an option to enable the behaviour I described above. This is actually what I expected -emptyDataSetShouldAllowTouch: to do, but that is not the case.

I'm sometimes getting an EXC_BAD_ACCESS crash in the first if in this code in UIScrollView+EmptyDataSet.m

- (BOOL)dzn_canDisplay
{
    if (self.emptyDataSetSource && [self.emptyDataSetSource conformsToProtocol:@protocol(DZNEmptyDataSetSource)]) {
        if ([self isKindOfClass:[UITableView class]] || [self isKindOfClass:[UICollectionView class]] || [self isKindOfClass:[UIScrollView class]]) {
            return YES;
        }
    }

    return NO;
}

The buttons returned (shown) from

- (NSAttributedString *)buttonTitleForEmptyDataSet:(UIScrollView *)scrollView forState:(UIControlState)state;

aren't registering touch events. The button appears to be displayed properly but tapping them does nothing on devices running iOS 7.x using Xcode 5.1.1. However, the buttons are working properly in the iOS 8 betas.

Thanks, Wes

Hello and thanks for this excellent library. i am facing a weird issue. In a UITableView environment when a user taps a uitextfield, inside a UITableViewCell, i am showing a uicollectionview as a customInputAccessoryView that shows words based on user input. when the user taps the texfield the app now freezes and memory goes well over 1GB. There must be a code loop thats happening in reloadData i am using this as a inputAccesoryView which is basically a custom uicollectionview that shows words inside horizontal cells. https://github.com/siuying/IGAutoCompletionToolbar

Can you provide any assistance on why this freezes? Is there a way to disable the swizzling for specific views?

thanks Konstantinos

When using the new release 1.6 then this happens when deallocation the TVC using DZNEmptyDataSet

2015-07-13 16:58:43.683 -[UITableView release]: message sent to deallocated instance

This happens even if the data set source and the delegate is set to nil.

-(void)dealloc { DLog(@"Dealloc %@ ",[self class]); self.tableView.emptyDataSetSource = nil; self.tableView.emptyDataSetDelegate = nil; }

Hi, I just encountered this odd bug, which caused me couple days to figure out. My app has a nested scrollView layout. Something looks like the nested layout in this article: http://ashfurrow.com/blog/putting-a-uicollectionview-in-a-uitableviewcell/ For iOS 5 and later, a gesture will lock to a scroll view once it is triggered, which means I can either scroll vertically OR horizontally, but not both. However, if you import UIScrollView+EmptyDataSet to the project above, it will allow simultaneous scrolling. Any idea how to fix it?

I've been having an issue where the empty set view is never shown when the app opens and there is no data in my FetchedResultsController. The view shows correctly if I open the app, inject some data into the data store and then manually delete all the rows.

The issue appears to be in the - (void)observeValueForKeyPath:(NSString *)keyPath ofObject:(id)object change:(NSDictionary *)change context:(void *)context where both new and old never differ because the tableView never adds any rows.

I'm not sure if this is a function of the fact that I'm using a fetchedResultsController to load my data from the store or if this is an issue that happens all the time (I imagine it's the former).

I've managed to hack around this for the time being by changing:

        if (new && old && ![new isEqualToValue:old]) {
            if ([keyPath isEqualToString:kContentSize]) {
                [self didReloadData];
            }
        }

to

        if (new && old && ![new isEqualToValue:old]) {
            if ([keyPath isEqualToString:kContentSize]) {
                [self didReloadData];
            }
        } else {
            [self reloadDataSet];
        }

but I'm sure this isn't the correct or best way to do things here. Is this the way it is intended to work? I can provide a more in depth example if needed.

If you are using DZNEmptyDataSet in your application, please take a screenshot of your empty dataset render and submit it here. This will help others to imagine all possibilities with the library. Thank you!

PS: 320px wide please

For some reason the height of my description label is much larger than it should be. In fact, this seems to be an issue for the bottom most element, as when I add a button title, the button height is abnormally tall as well. Any idea what might be causing this?

Hi, this is just a minor issue but I guess you may want to acknowledge about it.

The vertical alignment of titleForEmptyDataSet, descriptionForEmptyDataSet and imageForEmptyDataSet appears differently in these scenarios:

1. The app is first launched
2. How it looks after 1 row was added and deleted

3 & 4. When moves to another screen (Show segue) and goes back.

Here is the overview of them:

I hope you already have the solution for this.

1. The concept of scene is added. Each scene corresponds to an empty data set. Users can freely switch the display of empty data sets according to the scene to simplify the code logic.
2. The use of chained call mode simplifies the data configuration of empty data sets and greatly reduces the amount of code.
3. Replace the proxy with block, and the code is more cohesive.

For the setting constraints of detailLabel or titleLabel, ` if ([self canShowDetail]) {

        [subviewStrings addObject:@"detailLabel"];
        views[[subviewStrings lastObject]] = _detailLabel;
        
        [self.contentView addConstraints:[NSLayoutConstraint constraintsWithVisualFormat:@"H:|-(padding@750)-[detailLabel(>=0)]-(padding@750)-|"
                                                                                 options:0 metrics:metrics views:views]];
    }`

the leading and trailing constraints priority are not .default as 1000, which make our label will be exceed the superView. Could we set it to 1000 from 750 ?

[DZNEmptyDataSetView setClaCustomViewVisible:]: unrecognized selector;I search all over my project, no method with name related to setClaCustomViewVisible or CustomViewVisible. To avoid the crash, I edited the source code ,implement the method setClaCustomViewVisible