Jump to content

jackscl

Members
  • Posts

    5
  • Joined

  • Last visited

LabVIEW Information

  • Version
    LabVIEW 2016
  • Since
    2016

jackscl's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi Everyone, This days, I meet a strange thing: The exe created by LabVIEW might be no-acitve status anytime when my customer use it to get current data from 6485 and product SN from a Bar code scanning gun then recording data by NPIO .Unfortunately I have a long time business travel. My customer ask me to solve it -- he does not like using mouse to click the exe to active it. Hence I want to use winapi detect my UI's status and make it activity.But it does not work well .... Thanks. Add: When I click the desktop , the front panel will be as this status.The problem is that I still can't input keyboard. Another: I find that the focuse threat should be the UI THREAT ,But I can't get this vi's threat by GetCurrentThreat(). WindowSet.vi Test.vi
  2. Thank you for your explanation.I get it.I will convince my boss.
  3. Thank you very much. I find if i use value change event,it will be pass current value.(I usually use it).I will search the different between value change and mouse down.
  4. Maybe the mouse down event and the button's mechanical action is the reason? I like using value change event in my code. It's a Retired colleague's program,I delete the subVIs which the company doesn't want show. Test.vi
  5. It's a very easy event case. The problem is that the String to write (hex display) terminal passes the old value rather than the new value to the String out on my boss's computer when I clicked COM Write Button.But the problem never happens on my computer.Our computers' environment both are win7 and LabVIEW2014-Chinese. Is there anybody can explicate this phenomenon? Thanks.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.