Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QML and Qt Quick
  4. QtQuick - Busy Indicator

QtQuick - Busy Indicator

Scheduled Pinned Locked Moved Unsolved QML and Qt Quick
2 Posts 2 Posters 361 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N Offline
    N Offline
    nvharisha
    wrote on last edited by
    #1

    Hi,

    we have a Qt5.4 with QtQuick running on a MIPS platform. We use QML application. We have busy indicator, when ever the data from network is yet to be received.

    BusyIndicator {
         id: loadingIconId
         objectName:"loadinglcon"
         x:500
         y:300
         visible: false
     }
    

    But it gets jerky when there is some activities.
    As there is network activity, as well as some other activities going on, we thought UI ‍thread might get stuck / busy processing the events and hence we wanted to move to Render thread and hence we used Animator. (

    Image{
           id: loadingIconId
           objectName: "loadinglcon";
           x: 875;
           y: 340;
           height: 100
           width: 100
           visible: showHideIndicator;
           source:"../images/busyindicator.png"
           RotationAnimator {
                   target: loadingImageCustom
                   from: 0;
                   to: 360;
                   duration: 500
                   loops: Animation.Infinite
                   running: showHideIndicator
               }
       }
    

    But we are still seeing the same issue. Any suggestions?
    Is there any thing that is causing issues in scenegraph rendering? How can we investigate?

    We need to run the Loading-Icon till all the data has been received/loaded.

    Thanks

    Hari

    1 Reply Last reply
    0
    • dheerendraD Offline
      dheerendraD Offline
      dheerendra
      Qt Champions 2022
      wrote on last edited by
      #2

      Jerk indicates the still UI thread is busy processing. Just a suggestion. How about moving the processing the data itself to different thread & communicate using the signal/slots across threads ?

      Dheerendra
      @Community Service
      Certified Qt Specialist
      http://www.pthinks.com

      1 Reply Last reply
      0

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved