Jump to content

battler

Members
  • Posts

    16
  • Joined

  • Last visited

Posts posted by battler

  1. Build using LabVIEW a reusable library for Software Updates for standalone exes. This library should check the current version and periodically (user settable) search a particular database (held by and kept up to date by us) location on the internet in a format and using a method proposed by the developer. If it's found that the current version is older than the latest available then the library will download (from a location and using a method to be proposed) and install the latest version automatically (to be proposed). The library must be generic in that it can be used for any parent application. It must be efficient, robust and reusable. VI source code is required.

    Checking for updates.jpg

  2. Established start-up seeks experienced LabVIEW developer.

     

    Develop and maintain large technical engineering software applications in LabVIEW.  Note there is no data acquisition/hardware development required.

     

    Location is western Sydney.  Please PM me to apply.

     

    A. MAIN DUTIES

    1. Design, develop, verify and document new software applications from concept to deployment.

    2. Maintain and upgrade existing software applications.

    3. Be involved in consulting and project work surrounding both areas of expertise of the business and applications which the software has been designed for and beyond.

    4. Be involved in technical training seminars.

    5. Develop and/or contribute to technical research publications.

    6. Develop company standards documents; technical, non-technical, quality, procedures etc. with input from engineers and other parties as required.

    7. Provide technical support and advice both internally and to customers and clients.

    8. Develop technical procedures which assist with the company achieving and maintaining ISO 9001 quality accreditation.

     

    B. SELECTION CRITERIA

    • Honours degree in Electrical/Electronics Engineering or Computer Engineering.

    • Experience in developing medium to large LabVIEW software applications.

    • Knowledge and experience planning and developing software algorithms.

    • Experience with other programming languages.

    • Knowledge of electrical/electronics systems modelling concepts would be advantageous.

    • Knowledge of object-oriented principles and patterns would be advantageous.

    • Knowledge of cloud-based application deployment would be advantageous.

    • Knowledge and experience applying formal software lifecycle processes ensuring quality.

    • Experience writing technical documents.

    • Proficiency in using Microsoft Office products.

     

    C. DESIRABLE ATTRIBUTES

    • Excellent team working ability.

    • Conceptual and analytical problem solving ability.

    • Detail oriented with a high-level of organization.

    • Excellent written and verbal communication skills.

    • Driven and motivated with a passion for learning.

    • Resourceful, investigative and innovative.

  3. Hi David,

    I've built an application using the Type Sensitive Popup VIs you've provided.

    When I build an exe out of your Demo (and my VIs) they do not seem to work. The pop-up occurs but the VIs do not update the cell and your VIs freeze the program.

    Your help would be greatly appreciated.

    Please try to build an exe out of your Demo.

    Cheers.

  4. Thanks Mads, that's fantastic.

    The settings in the exe ini file. How do you know what to put in there? Can you point me in the direction of some documentation about those?

    I'm really keen to explore the ActiveX server method for doing this.

    My apologies, it looks like you can. I'd never played with this before, I'll check it out.

    That's ok I forgive you;-) Especially since you are in Sydney like me.

    I'm really keen to explore the ActiveX server method for assigning file extensions to exe.

    Does anyone have any idea about this (i.e. ActiveX servers)?

  5. Nice!!

    I don't think you can communicate between LabVIEW exe's with ActiveX as this would involve writing your own ActiveX server.

    I thought LabVIEW exe's had the ability to act as an ActiveX server. It's a setting in the App builder.

    I do it this way in my applications. The loader app gets the file path from the argument generated by the OS due to the registry settings - and uses DDE to transfer the path of the opened file. If the DDE connection fails it assumes that the app is not running yet and starts it...and waits until it gets the DDE link. I do not launch the target app with arguments simply because I want it to work smoothly when opening multiple files:

    I have set the .ini file of the launcher so that it runs multiple instances (AllowMultipleInstances=True)...that way people can open multiple files in one go.

    The reason why I chose DDE instead of TCP is because it is less of an open door to the outside world...although I would prefer it if there was indeed a way to esnsure that the communication was only possible locally on the PC (without using the firewall). ActiveX could be an option...as DDE really is a very old technology and might get phased out soon.

    Mads

    Thanks Mads. Can you post some example code?

    How does the "loader app gets the file path from the argument generated by the OS"? You build 2 separate exe's? The loader (laucher?) is registered to the sutom file type (i.e. .myx)with the OS via registry settings?

  6. Sorry,

    I can't locate the code anymore, but here is a VI in 8.6 with two OS.OpenDocument Events (filter and normal).

    I did not get this to work with anything other than 8.2

    Ton

    Thanks Ton.

    From what I've read about VI Scripting I don't think using this OS.OpenDocument Event is a good idea (or even possible).

    What is the best method for associating a custom file type with an application and being able to open the file when the app is both running and closed?

  7. It adds properties and methods to the LabVIEW VI server hierarchy, mostly application related and presumably project and other such stuff, that NI considers to dangerous, untested, or giving to deep insight into LabVIEW. It is related to scripting but not the same thing.

    Rolf Kalbermatter

    I thought you all were joking about the:

    SuperPrivateScriptingFeatureVisible=True

    Based on this does mean that opening a file by double-clicking on it while your main app is open... is not possible?

    Cheers,

    Battler.

  8. Have a look at this LabVIEW wiki topic.

    There is even a specific event, that only works in LabVIEW 8.2.

    To get a good working solution, JKI has implemented a small loader executable that is registered with the extension. This (fas-loading) application sends the actual file path to VIPM via TCP/IP or something else.

    Ton

    Thanks heaps.

    I can't get the code. Where do I get it? The links seem to be broken. Any ideas?

    Nice find, thought there would other ways to do this. LVShellOpen.exe solution is very close to what I'd proposed.

    Were you able to get the code? Thanks.

    Have a look at this LabVIEW wiki topic.

    There is even a specific event, that only works in LabVIEW 8.2.

    To get a good working solution, JKI has implemented a small loader executable that is registered with the extension. This (fas-loading) application sends the actual file path to VIPM via TCP/IP or something else.

    Ton

    JKI software. Is the application downloadable for free from their website? What is the name of the application? Thanks:)

    Thanks heaps.

    I can't get the code. Where do I get it? The links seem to be broken. Any ideas?

    Were you able to get the code? Thanks.

    JKI software. Is the application downloadable for free from their website? What is the name of the application? Thanks:)

    I want to be able to write the code myself;-) Are there any example VI available? Cheers. Battler.

  9. Thanks for your response.

    As you say, perhaps I could register a separate application (App2) to my custom file extension with command line arguments enabled.

    When a custom file is double-clicked App2 would need to either:

    1. If App1 is not running - Open App1 and pass the filename with custom extension; or

    2. If App1 is already running - Send the filename. An event would need to be triggered in App1.

    I like the sounds of TCP/IP as opposed to DDE. How would this work? How would an event be triggered in the event structure upon receiving TCP/IP data (i.e. filename)?

    Nice thinking.

    Cheers,

    Battler.

  10. Hi all,

    I managed to follow the instructions found here:

    http://digital.ni.com/public.nsf/allkb/9538A36E218F10A4862571A8005EF6C0

    Now when I double-click on my custom file (i.e. file.abc) it opens my application. From there I can use the command line interface to open the file.

    This is fine when my application is closed. However, I want it to work when my application is running. My application contains an event structure. I was told that I could probably doing it by using the DDE server functions.

    Would anybody be able to help me to find the relevant information?

    Thanks very much.

    Battler.

×
×
  • Create New...

Important Information

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