How to give Image from another thread?












1














I have a code for getting user pic:



if let photoURL = message[Constants.MessageFields.photoURL], let URL = URL(string: photoURL),
let data = try? Data(contentsOf: URL) {
cell.userPic.image = UIImage(data: data)
}


When I'm using it, tableView lagging at scrolling.



Please help me to put this code in another thread.










share|improve this question



























    1














    I have a code for getting user pic:



    if let photoURL = message[Constants.MessageFields.photoURL], let URL = URL(string: photoURL),
    let data = try? Data(contentsOf: URL) {
    cell.userPic.image = UIImage(data: data)
    }


    When I'm using it, tableView lagging at scrolling.



    Please help me to put this code in another thread.










    share|improve this question

























      1












      1








      1







      I have a code for getting user pic:



      if let photoURL = message[Constants.MessageFields.photoURL], let URL = URL(string: photoURL),
      let data = try? Data(contentsOf: URL) {
      cell.userPic.image = UIImage(data: data)
      }


      When I'm using it, tableView lagging at scrolling.



      Please help me to put this code in another thread.










      share|improve this question













      I have a code for getting user pic:



      if let photoURL = message[Constants.MessageFields.photoURL], let URL = URL(string: photoURL),
      let data = try? Data(contentsOf: URL) {
      cell.userPic.image = UIImage(data: data)
      }


      When I'm using it, tableView lagging at scrolling.



      Please help me to put this code in another thread.







      swift multithreading






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 21 at 8:08









      Артем Ильинский

      969




      969
























          1 Answer
          1






          active

          oldest

          votes


















          5














          Here is a good sample provided by Apple, that you can adapt for your needs:



          Prefetching collection view data



          Basic idea is to create AsyncFetcher for your images and put image creation code to separate operation.



          func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell {
          guard let cell = collectionView.dequeueReusableCell(withReuseIdentifier: Cell.reuseIdentifier, for: indexPath) as? Cell else {
          fatalError("Expected `(Cell.self)` type for reuseIdentifier (Cell.reuseIdentifier). Check the configuration in Main.storyboard.")
          }

          let model = models[indexPath.row]
          let id = model.id
          cell.representedId = id

          // Check if the `asyncFetcher` has already fetched data for the specified identifier.
          if let fetchedData = asyncFetcher.fetchedData(for: id) {
          // The data has already been fetched and cached; use it to configure the cell.
          cell.configure(with: fetchedData)
          } else {
          // There is no data available; clear the cell until we've fetched data.
          cell.configure(with: nil)

          // Ask the `asyncFetcher` to fetch data for the specified identifier.
          asyncFetcher.fetchAsync(id) { fetchedData in
          DispatchQueue.main.async {
          /*
          The `asyncFetcher` has fetched data for the identifier. Before
          updating the cell, check if it has been recycled by the
          collection view to represent other data.
          */
          guard cell.representedId == id else { return }

          // Configure the cell with the fetched image.
          cell.configure(with: fetchedData)
          }
          }
          }

          return cell
          }


          But in your case you should use Table View prefetching



          I can confirm that this approach works and (when done right) results smooth scrolling and good UX






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53407646%2fhow-to-give-image-from-another-thread%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            5














            Here is a good sample provided by Apple, that you can adapt for your needs:



            Prefetching collection view data



            Basic idea is to create AsyncFetcher for your images and put image creation code to separate operation.



            func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell {
            guard let cell = collectionView.dequeueReusableCell(withReuseIdentifier: Cell.reuseIdentifier, for: indexPath) as? Cell else {
            fatalError("Expected `(Cell.self)` type for reuseIdentifier (Cell.reuseIdentifier). Check the configuration in Main.storyboard.")
            }

            let model = models[indexPath.row]
            let id = model.id
            cell.representedId = id

            // Check if the `asyncFetcher` has already fetched data for the specified identifier.
            if let fetchedData = asyncFetcher.fetchedData(for: id) {
            // The data has already been fetched and cached; use it to configure the cell.
            cell.configure(with: fetchedData)
            } else {
            // There is no data available; clear the cell until we've fetched data.
            cell.configure(with: nil)

            // Ask the `asyncFetcher` to fetch data for the specified identifier.
            asyncFetcher.fetchAsync(id) { fetchedData in
            DispatchQueue.main.async {
            /*
            The `asyncFetcher` has fetched data for the identifier. Before
            updating the cell, check if it has been recycled by the
            collection view to represent other data.
            */
            guard cell.representedId == id else { return }

            // Configure the cell with the fetched image.
            cell.configure(with: fetchedData)
            }
            }
            }

            return cell
            }


            But in your case you should use Table View prefetching



            I can confirm that this approach works and (when done right) results smooth scrolling and good UX






            share|improve this answer


























              5














              Here is a good sample provided by Apple, that you can adapt for your needs:



              Prefetching collection view data



              Basic idea is to create AsyncFetcher for your images and put image creation code to separate operation.



              func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell {
              guard let cell = collectionView.dequeueReusableCell(withReuseIdentifier: Cell.reuseIdentifier, for: indexPath) as? Cell else {
              fatalError("Expected `(Cell.self)` type for reuseIdentifier (Cell.reuseIdentifier). Check the configuration in Main.storyboard.")
              }

              let model = models[indexPath.row]
              let id = model.id
              cell.representedId = id

              // Check if the `asyncFetcher` has already fetched data for the specified identifier.
              if let fetchedData = asyncFetcher.fetchedData(for: id) {
              // The data has already been fetched and cached; use it to configure the cell.
              cell.configure(with: fetchedData)
              } else {
              // There is no data available; clear the cell until we've fetched data.
              cell.configure(with: nil)

              // Ask the `asyncFetcher` to fetch data for the specified identifier.
              asyncFetcher.fetchAsync(id) { fetchedData in
              DispatchQueue.main.async {
              /*
              The `asyncFetcher` has fetched data for the identifier. Before
              updating the cell, check if it has been recycled by the
              collection view to represent other data.
              */
              guard cell.representedId == id else { return }

              // Configure the cell with the fetched image.
              cell.configure(with: fetchedData)
              }
              }
              }

              return cell
              }


              But in your case you should use Table View prefetching



              I can confirm that this approach works and (when done right) results smooth scrolling and good UX






              share|improve this answer
























                5












                5








                5






                Here is a good sample provided by Apple, that you can adapt for your needs:



                Prefetching collection view data



                Basic idea is to create AsyncFetcher for your images and put image creation code to separate operation.



                func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell {
                guard let cell = collectionView.dequeueReusableCell(withReuseIdentifier: Cell.reuseIdentifier, for: indexPath) as? Cell else {
                fatalError("Expected `(Cell.self)` type for reuseIdentifier (Cell.reuseIdentifier). Check the configuration in Main.storyboard.")
                }

                let model = models[indexPath.row]
                let id = model.id
                cell.representedId = id

                // Check if the `asyncFetcher` has already fetched data for the specified identifier.
                if let fetchedData = asyncFetcher.fetchedData(for: id) {
                // The data has already been fetched and cached; use it to configure the cell.
                cell.configure(with: fetchedData)
                } else {
                // There is no data available; clear the cell until we've fetched data.
                cell.configure(with: nil)

                // Ask the `asyncFetcher` to fetch data for the specified identifier.
                asyncFetcher.fetchAsync(id) { fetchedData in
                DispatchQueue.main.async {
                /*
                The `asyncFetcher` has fetched data for the identifier. Before
                updating the cell, check if it has been recycled by the
                collection view to represent other data.
                */
                guard cell.representedId == id else { return }

                // Configure the cell with the fetched image.
                cell.configure(with: fetchedData)
                }
                }
                }

                return cell
                }


                But in your case you should use Table View prefetching



                I can confirm that this approach works and (when done right) results smooth scrolling and good UX






                share|improve this answer












                Here is a good sample provided by Apple, that you can adapt for your needs:



                Prefetching collection view data



                Basic idea is to create AsyncFetcher for your images and put image creation code to separate operation.



                func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell {
                guard let cell = collectionView.dequeueReusableCell(withReuseIdentifier: Cell.reuseIdentifier, for: indexPath) as? Cell else {
                fatalError("Expected `(Cell.self)` type for reuseIdentifier (Cell.reuseIdentifier). Check the configuration in Main.storyboard.")
                }

                let model = models[indexPath.row]
                let id = model.id
                cell.representedId = id

                // Check if the `asyncFetcher` has already fetched data for the specified identifier.
                if let fetchedData = asyncFetcher.fetchedData(for: id) {
                // The data has already been fetched and cached; use it to configure the cell.
                cell.configure(with: fetchedData)
                } else {
                // There is no data available; clear the cell until we've fetched data.
                cell.configure(with: nil)

                // Ask the `asyncFetcher` to fetch data for the specified identifier.
                asyncFetcher.fetchAsync(id) { fetchedData in
                DispatchQueue.main.async {
                /*
                The `asyncFetcher` has fetched data for the identifier. Before
                updating the cell, check if it has been recycled by the
                collection view to represent other data.
                */
                guard cell.representedId == id else { return }

                // Configure the cell with the fetched image.
                cell.configure(with: fetchedData)
                }
                }
                }

                return cell
                }


                But in your case you should use Table View prefetching



                I can confirm that this approach works and (when done right) results smooth scrolling and good UX







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 21 at 8:19









                fewlinesofcode

                2,024518




                2,024518






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53407646%2fhow-to-give-image-from-another-thread%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    404 Error Contact Form 7 ajax form submitting

                    How to know if a Active Directory user can login interactively

                    Refactoring coordinates for Minecraft Pi buildings written in Python