Jump to content

Search the Community

Showing results for tags 'abort'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Special Interest Boards
    • Professional User Interface Design in LabVIEW
  • VI Package Manager (VIPM)
    • VI Package Manager (VIPM)
  • JKI Tools
    • JKI Flat UI Controls
    • JKI Design Palette
    • JKI State Machine
    • JKI State Machine Objects (SMO)
    • Caraya Unit Tester
    • VI Tester
    • JKI JSON
    • HTTP REST Client
    • JKI Simple Localization
    • EasyXML Toolkit
  • Legacy Tools
    • Legacy Tools

Calendars

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. Hi, One nice feature of SMO is the ability to programmatically abort an instance of a SMO that did not stop properly when asked to. Very similar to what you would do with the big red "abort" button in the labVIEW IDE. The abort method is called in the "destroy.vi" method of the SMO. However, this functionnality doesn't work for me and I'm not sure it is supposed to work. Indeed, the SMO is attempting to call the abort invoke method on the reference of "process.vi" which is a subvi of "LaunchProcess.vi". To my understanding, LabVIEW does not allow to programmatically kill a subvi. Only a top level vi can be killed with the "abort" invoke node (top levels vi include vis launched with the "run" method or with the "asynchronous call" method and the x80 flag for instance). Calling the "abort" method on a subvi's reference ends up with error 1000. Hence I think that LaunchProcess.vi can indeed be aborted programmically but not process.vi and this is why the abort feature doesn't work in SMO. Am I missing something? Best regards, Christophe
×
×
  • Create New...

Important Information

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