Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. Best way to intercommunicate between apps

Best way to intercommunicate between apps

Scheduled Pinned Locked Moved C / C++ / MFC
question
6 Posts 4 Posters 0 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.
  • E Offline
    E Offline
    EiSl
    wrote on last edited by
    #1

    Hello all, We've a couple of applications using to perform regression tests. The 'front-end' application which launches and controls all. Current situation (part of) - Front-end launches the 'big-app' and uses a fixed delay before continue operation to give 'big-app' the possibility to initialize itself. Bad part: fixed delay in combination with fast or slow PC. Prefered situation - Front-end launches the 'big-app' and continues execution when 'big-app' signals its ready to continue. My question: What is the best solution for this signalling event. I need no other info than: "I'm ready... go on". A named pipe looks a bit overkill too me. With regards, EizSl

    T P C 3 Replies Last reply
    0
    • E EiSl

      Hello all, We've a couple of applications using to perform regression tests. The 'front-end' application which launches and controls all. Current situation (part of) - Front-end launches the 'big-app' and uses a fixed delay before continue operation to give 'big-app' the possibility to initialize itself. Bad part: fixed delay in combination with fast or slow PC. Prefered situation - Front-end launches the 'big-app' and continues execution when 'big-app' signals its ready to continue. My question: What is the best solution for this signalling event. I need no other info than: "I'm ready... go on". A named pipe looks a bit overkill too me. With regards, EizSl

      T Offline
      T Offline
      Tomasz Sowinski
      wrote on last edited by
      #2

      If the big guy is Windows (not console) app, you should use WaitForInputIdle. Tomasz Sowinski -- http://www.shooltz.com

      Free your mind and your ass will follow.

      1 Reply Last reply
      0
      • E EiSl

        Hello all, We've a couple of applications using to perform regression tests. The 'front-end' application which launches and controls all. Current situation (part of) - Front-end launches the 'big-app' and uses a fixed delay before continue operation to give 'big-app' the possibility to initialize itself. Bad part: fixed delay in combination with fast or slow PC. Prefered situation - Front-end launches the 'big-app' and continues execution when 'big-app' signals its ready to continue. My question: What is the best solution for this signalling event. I need no other info than: "I'm ready... go on". A named pipe looks a bit overkill too me. With regards, EizSl

        P Offline
        P Offline
        Pavel Klocek
        wrote on last edited by
        #3

        You can use named Win32 event - see CreateEvent and OpenEvent API functions or CEvent MFC class. Sonork 100.15206;PavelK

        1 Reply Last reply
        0
        • E EiSl

          Hello all, We've a couple of applications using to perform regression tests. The 'front-end' application which launches and controls all. Current situation (part of) - Front-end launches the 'big-app' and uses a fixed delay before continue operation to give 'big-app' the possibility to initialize itself. Bad part: fixed delay in combination with fast or slow PC. Prefered situation - Front-end launches the 'big-app' and continues execution when 'big-app' signals its ready to continue. My question: What is the best solution for this signalling event. I need no other info than: "I'm ready... go on". A named pipe looks a bit overkill too me. With regards, EizSl

          C Offline
          C Offline
          Christian Graus
          wrote on last edited by
          #4

          WM_COPYDATA is hands down the easiest way to communicate between two processes. Christian We're just observing the seasonal migration from VB to VC. Most of these birds will be killed by predators or will die of hunger. Only the best will survive - Tomasz Sowinski 29-07-2002 ( on the number of newbie posters in the VC forum ) Cats, and most other animals apart from mad cows can write fully functional vb code. - Simon Walton - 6-Aug-2002

          E 1 Reply Last reply
          0
          • C Christian Graus

            WM_COPYDATA is hands down the easiest way to communicate between two processes. Christian We're just observing the seasonal migration from VB to VC. Most of these birds will be killed by predators or will die of hunger. Only the best will survive - Tomasz Sowinski 29-07-2002 ( on the number of newbie posters in the VC forum ) Cats, and most other animals apart from mad cows can write fully functional vb code. - Simon Walton - 6-Aug-2002

            E Offline
            E Offline
            EiSl
            wrote on last edited by
            #5

            Thx for reply Christian, You mean using the WM_COPYDATA with use of HWND_BROADCAST in SendMessage ? With regards, EiSl

            C 1 Reply Last reply
            0
            • E EiSl

              Thx for reply Christian, You mean using the WM_COPYDATA with use of HWND_BROADCAST in SendMessage ? With regards, EiSl

              C Offline
              C Offline
              Christian Graus
              wrote on last edited by
              #6

              If you don't know the target HWND, yes. I have used it in the past by naming one of my apps so I can use EnumWindows to find it, send it my HWND, and then they can both talk to each other without sending a message to every window on the desktop. Christian We're just observing the seasonal migration from VB to VC. Most of these birds will be killed by predators or will die of hunger. Only the best will survive - Tomasz Sowinski 29-07-2002 ( on the number of newbie posters in the VC forum ) Cats, and most other animals apart from mad cows can write fully functional vb code. - Simon Walton - 6-Aug-2002

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • World
              • Users
              • Groups