Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. How to begin an instrumentation simulator
Forum Updated to NodeBB v4.3 + New Features

How to begin an instrumentation simulator

Scheduled Pinned Locked Moved General and Desktop
4 Posts 3 Posters 2.6k Views 1 Watching
  • 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.
  • mzimmersM Offline
    mzimmersM Offline
    mzimmers
    wrote on last edited by
    #1

    Hi -

    I've been asked to look into writing a program that will accept telemetry from a communications device via TCP/IP and display graphically the information it receives. The display will look something like this (slightly less complicated):

    !http://scopedin.com/images/6100.jpg(6100 display)!

    The grid in the upper left will contain many sample points (represented as dots) and will need to be updated regularly (like once a second).

    Controls will be limited to rescaling, refreshing and a few other minor tweaks. Mostly this is a display project.

    What would anyone recommend as the Qt path to take for this? Should it be a Quick project, a Widget project, or something else?

    Thanks for any ideas.

    1 Reply Last reply
    0
    • S Offline
      S Offline
      sidewinder
      wrote on last edited by
      #2

      I would go for a Widget project. Combined with "Qwt":http://qwt.sourceforge.net/ it should be fairly easy to create ui like one you presented. QtQuick may have better performance in complex graphics, but it's not yet as productive as Graphics View/Scene system when it comes to using standard controls (like line edits, spinboxes, radio buttons) and, AFAIK, there is nothing like qwt for QtQuick.

      "Never memorize what you can look up in books."
      Albert Einstein

      1 Reply Last reply
      0
      • A Offline
        A Offline
        andre
        wrote on last edited by
        #3

        I agree with sidewinder on this one, though it might be smart to keep portability of the GUI in mind while designing your application. If you design your backend/gui separation as if you were going to use a Quick ui (clean separation of ui and implementation, all property and signal/slot based interface), you will have an easy time porting to a different GUI later on if you wish to do that.

        1 Reply Last reply
        0
        • mzimmersM Offline
          mzimmersM Offline
          mzimmers
          wrote on last edited by
          #4

          Thank you for the suggestions. Since this will be my first project that actually uses Qt for more than an IDE, I'd like a recommendation on an example as well, something I can use as a starting point. Any ideas?

          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