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. .NET (Core and Framework)
  4. Blocks Aplicattion

Blocks Aplicattion

Scheduled Pinned Locked Moved .NET (Core and Framework)
csharpdotnethelpquestion
4 Posts 3 Posters 1 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.
  • K Offline
    K Offline
    korrea80
    wrote on last edited by
    #1

    Hi all!. Im using Agilent Vee and .NET Framework 2.0. Agilent Vee its a visual language and I can use all libs of .NET Framework 2.0. I want to create some forms who capture some instrument status, I create a form, show, etc ... ok all perfect. But if I move the window, the aplication stop the adquisition. And restart adquisition when I dont move the window. Anyone can help me???? Thanks and regards. P.D. Sorry for my english...

    L 1 Reply Last reply
    0
    • K korrea80

      Hi all!. Im using Agilent Vee and .NET Framework 2.0. Agilent Vee its a visual language and I can use all libs of .NET Framework 2.0. I want to create some forms who capture some instrument status, I create a form, show, etc ... ok all perfect. But if I move the window, the aplication stop the adquisition. And restart adquisition when I dont move the window. Anyone can help me???? Thanks and regards. P.D. Sorry for my english...

      L Offline
      L Offline
      lmoelleb
      wrote on last edited by
      #2

      You are probably better of capturing your information on a worker thread. Notice you can't update the GUI from this worker thread, so you would have to get the data to the GUI thread somehow. Some of the options are: 1) Share the data, do a lock when it is updated/read 2) Clone the data and send the data to the GUI though BeginInvoke I can't say which one (or something completely different) is best, it comes down to the data and - not least - your personal taste.

      K 1 Reply Last reply
      0
      • L lmoelleb

        You are probably better of capturing your information on a worker thread. Notice you can't update the GUI from this worker thread, so you would have to get the data to the GUI thread somehow. Some of the options are: 1) Share the data, do a lock when it is updated/read 2) Clone the data and send the data to the GUI though BeginInvoke I can't say which one (or something completely different) is best, it comes down to the data and - not least - your personal taste.

        K Offline
        K Offline
        korrea80
        wrote on last edited by
        #3

        Hi. This is the problem. Agilent Vee crash with .NET Threading... :( The other question is, only GUI stop or all program stop??? If only stop the gui, no problem, the most important its a second work... Thank your for your ideas ;). Best Regards.

        R 1 Reply Last reply
        0
        • K korrea80

          Hi. This is the problem. Agilent Vee crash with .NET Threading... :( The other question is, only GUI stop or all program stop??? If only stop the gui, no problem, the most important its a second work... Thank your for your ideas ;). Best Regards.

          R Offline
          R Offline
          Ruth Ivimey Cook
          wrote on last edited by
          #4

          If you can't get Vee to work with Threading (and you've confirmed it's not an issue in your code **), you could try a background process that does the acquisition and send the data to the GUI foreground process using a Windows Named Pipe. HTH, Ruth ** Most threading problems arise from invalidly sharing data - either implicitly or explicitly. Keep data sharing to an absolute minimum and ensure you're "lock"ing the rest. Ruth Ivimey-Cook VS2005 / C# & VB

          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