使用SnapKit约束UITableViewCell子视图时设置Frame的方法咨询

Hey there! Let's work through your problem and answer your questions clearly.

Why Are You Getting a 44pt Height for Your Background View? #

That 44pt number isn't random—it's the default height of a UITableViewCell. Here's what's likely going on:

• You haven't configured your table view to calculate dynamic cell heights based on Auto Layout constraints. Even though your background view's constraints are set correctly, the cell itself is stuck using the default fixed height, which limits your background view's height.
• The timing of your setNeedsLayout() and layoutIfNeeded() calls might be off. If you're running these methods before the cell is added to the table view's view hierarchy, the layout engine hasn't had a chance to calculate the actual height based on your constraints.

Fixes to Get the Correct Height: #

1. Enable dynamic cell heights in your table view:

   tableView.rowHeight = UITableView.automaticDimension
   tableView.estimatedRowHeight = 100 // Use a reasonable estimate for your content
   

   This tells the table view to calculate each cell's height based on its content's Auto Layout constraints.

2. Verify your constraint setup is complete:
   Your background view's edges are pinned to the contentView with insets, which is good—but make sure all other subviews inside the background view have complete constraints (top, bottom, leading, trailing, or fixed sizes). This gives the layout engine enough info to calculate the full height of the background view (and thus the cell).

3. Call layout methods at the right time:
   Avoid trying to get the height in the cell's initializer or awakeFromNib(). Instead, access the height after the cell has been laid out, like in cellForRowAt (after configuring all subviews) or in the cell's didLayoutSubviews() method:

   override func didLayoutSubviews() {
       super.didLayoutSubviews()
       let actualHeight = background.frame.height
       // Use the height here
   }
   

Can You Set a View's Frame Directly with SnapKit? #

Short answer: SnapKit is built for Auto Layout constraints, not direct frame manipulation. Its entire purpose is to create and manage constraints in a cleaner, more readable way than UIKit's native API.

That said, you can simulate setting a frame using constraints if needed. For example, to replicate frame = CGRect(x: 16, y: 0, width: 300, height: 200), you'd write:

background.snp.makeConstraints { make in
    make.top.equalToSuperview()
    make.leading.equalToSuperview().offset(16)
    make.width.equalTo(300)
    make.height.equalTo(200)
}

This achieves the same visual result as setting a frame, but it's still using Auto Layout under the hood.

If you try to set the frame directly (background.frame = ...) while using Auto Layout constraints, the layout engine will override your frame changes the next time layout runs. Mixing direct frame changes with Auto Layout almost always leads to unexpected layout bugs, so it's best to stick with constraints.

内容的提问来源于stack exchange，提问作者ilikecode