Fixed Grid issues, where the layout calculations were being deferred and causing inconsistencies in layouts.

Author: Daniel Dahan

CHANGELOG.md

@@ -1,3 +1,8 @@
+## 3.1.7
+
+* Fixed Grid issues, where the layout calculations were being deferred and causing inconsistencies in layouts.
+* Updated to [Motion 3.1.2](https://github.com/CosmicMind/Motion/releases/tag/3.1.2).
+
 ## 3.1.6
 - [issue-1245](https://github.com/CosmicMind/Material/issues/1245): Fixed issue where completion block was not executed when calling Switch.toggle.
 

Material.podspec

@@ -1,6 +1,6 @@
 Pod::Spec.new do |s|
 	s.name = 'Material'
-	s.version = '3.1.6'
+	s.version = '3.1.7'
 	s.swift_version = '5.0'
 	s.license = 'BSD-3-Clause'
 	s.summary = 'A UI/UX framework for creating beautiful applications.'

Material.xcodeproj/xcshareddata/xcschemes/Material.xcscheme

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <Scheme
-   LastUpgradeVersion = "1020"
+   LastUpgradeVersion = "1030"
    version = "1.3">
    <BuildAction
       parallelizeBuildables = "YES"

Sources/Frameworks/Motion

@@ -15,7 +15,7 @@
 	<key>CFBundlePackageType</key>
 	<string>FMWK</string>
 	<key>CFBundleShortVersionString</key>
-	<string>3.1.6</string>
+	<string>3.1.7</string>
 	<key>CFBundleSignature</key>
 	<string>????</string>
 	<key>CFBundleVersion</key>

Sources/Info.plist

@@ -216,6 +216,13 @@ public struct Grid {
       return
     }
 
+    /// It is important to call `setNeedsLayout` and `layoutIfNeeded`
+    /// in order to have the parent view's `frame` calculation be set
+    /// for `Grid` to be able to then calculate the correct dimenions
+    /// of its `child` views.
+    canvas.setNeedsLayout()
+    canvas.layoutIfNeeded()
+    
     guard 0 < canvas.bounds.width && 0 < canvas.bounds.height else {
       return
     }