Non-LabVIEW look

First, I am relatively new to LV.
I've been assigned the GUI that our Customers will see whenever they use our product.
Often our Customers are not literate, much less computer literate; unfortunately, most of LV's controls resemble engineering tools. We need to make the controls look less technical, bigger and include numerous pictures to convey information.
Is there a tutorial that shows how to "disguise" the LV controls?
For example: The picture control (Classic | Classic Graph | Controls | Picture) wants me to enter rectangles, colors, etc. on the block diagram to draw on the control, but I need to select an image from a list. Also, this control defaults to a thick border with a white background, and I can't seem to find any info on how to edit this setting.
Next, I'm looking for something on how to make a custom Message Box (aka Dialog Box), because the standard 1, 2 and 3 button dialogs (Programming | Dialog & User Interface) would be too small on our screens and would require custom images (instead of the standard MB_ICONINFORMATION, MB_ICONQUESTION, and MB_ICONERROR images).
Where would be a good place for me to find information such as this? I am sure it has been covered before, but I have not seen anything like this when I searched.
Angus Cattle from Pool Ranch and Steel Repairs via Joe's Welding.

First I'll advice you to use system controls, this will give your application an OS compliant look (even if your OS is customized).
Here's a screeenshot of such a VI:
Secondly if you need pictures for controls you should use the Boolean XControl to create boolean buttons with an image. I've created a large set of VI's to load into the Boolean XControl with icons from the Tango projec here
There's even a book about creating LabVIEW GUIs with tips an tricks.
An excellent example of a LabVIEW non-LabVIEW looking application is VIPM
Good luck,
Ton
Message Edited by TonP on 12-05-2007 04:57 PM
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!
Attachments:
System UI.png ‏4 KB

Similar Messages

  • Non-profit looking to purchase creative suite for multiple users

    Hi! I am representing a non-profit who is interested in purchasing the creative suite to be accessed for multiple users. Can someone direct me with how to do that? Thanks.Non-profit looking to purchase

    Start here:
    Adobe nonprofit eligibility qualifications| Adobe Volume Licensing

  • Open Block Diagram After Deployment on a Non-LabVIEW PC

    Hello all,
    I have a application created in LabVIEW which will be deployed on a PC which does not have LabVIEW Development System installed in it, but only the RTE. With this application, I am also deploying the dependent VIs in a separate folder.
    My question is, is there any way we can open the BD of these dependent VIs in Highlight Execution mode on such PC with no LabVIEW Development System installed? I just want to view the BD of the VI in highlight execution mode, I don't want to edit/make any changes to the VI. Then obviously, we would be needing the LV development system.
    Since I've left block diagram (allow debugging) option enabled before deployment, I hope there must be some way we can acess the BD in highlight execution mode. I know that BD get image property works in PC with no LabVIEW Development system installed, so there must be some way or other to access the block diagram in highlight mode.
    Can anyone try to help in this?
    Thanks in advacne!
    -FraggerFox!
    -FraggerFox!
    Certified LabVIEW Architect, Certified TestStand Developer
    "What you think today is what you live tomorrow"

    You can't do it on a PC without the development environment.  If you have debugging enable in the .exe, you can connect to it remotely over the network from a PC with the development environment to watch the execution.  Look for "remote panel connection" under the tools menu.

  • After reboot, Labview looks for RTE 7.1 (RTE 8.2 installed)

    I started developing software using Labview 7.1.  Mid way complete I decided to switch to Labview 8.2.  Now everytime I reboot, I get a Windows installer asking for the Labview 7.1 runtime engine.  I re-installed Labview 7.1 but I keep getting the installer asking for this runtime engine.  Eventually after clicking cancel about 10 times, it finds an engine (not sure which one) and runs the exe.  This exe is on a PC running Windows XP in a factory, controlling a machine.  I need to fix this problem for the customer to be happy.  Is it possible that one of the VIs I used in 7.1 is now in 8.2's code but needs the old engine to work?  How can I fix this problem?  Note that I'm not using any VIs in 8.2 that don't already exist in 7.1. (stupid mistake to use 8.2).
    Hopefully someone can help me.
    Matt Koebel
    Technologist

    Apparently Windows something got messed-up during the installation process. If it were me I think my first step would be to backup the source code and uninstall all National Instruments software. After the uninstall, reboot and run a registry cleaner like CCleaner (free download) to remove any remnants of old installations. Note that before it cleans up issues that it finds in your registry it will ask you if you want to back up the things that its removing - say "Yes". If necessary, run the scan repeatedly until it reports that it found no additional issues.
    Finally, reboot again you should not get the message.
    Now reinstall all the NI software. If the latest version of your code is in LV8.2 just install that (actually 8.2.1).
    Oh yes, the most important thing: Be sure to do all of this from an administrator account.
    Keep us posted on how you are getting on.
    Mike...
    PS: Looking back on what I wrote it occurs to me that perhaps it might be worth a try to download CCleaner and running it before you do the uninstall. It's probably a long shot, but it's clean-up process might fix whatever is causing the trouble. If it works you have saved a bunch of time. If it doesn't you haven't lost much.
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • Bluetooth comunication with non labview device (cell phone)

        Hello everybody,
    my question is "simple" so I'll get to the point:
    It is possible to make a Bluetooth conection between a labview program and another program in other device?
    I want to send commands from a program in my cell phone (Pyhon) to my PC (labview), and I haven´t found information of how to do it.
    If  answer == YES  {
    How?;
    Thanks;
    else   {
    I'm done...  ;
    Thanks for saving me hours looking for the way to do it....

    We were able to succesffully communicate with BT printers using the LabVIEW BT primatives. However, we had to uninstall the deviceand adapter specific BT drivers before it would work. For example, if you are using a BT adapter on a PC you should remove its drivers. Leave the Windows default drivers installed.
    Mark Yedinak
    "Does anyone know where the love of God goes when the waves turn the minutes to hours?"
    Wreck of the Edmund Fitzgerald - Gordon Lightfoot

  • How can I get handle(s) to and poll non-LabVIEW window(s)/application(s) from LabVIEW?

    Want to launch EXE from LabVIEW, wait for user to finish with EXE's UI, and once they closed it, return execution flow in LabVIEW. Cool, no problem.
    Used the System Exec VI and with the "wait until completion" = TRUE the EXE never launches. Not sure why.
    With the "wait until completion" = FALSE, the application runs with no problems, but now LabVIEW no longer waits.  Can't tell when user is done.
    Work around idea... Once the Sys Exec VI launches the EXE, wait and poll some Windows API call to see when the window for the specific EXE closes. Cool.
    I know G and no C.  What I would ideally like is a DLL, that I can wrap with the DLL Import Wizard.  Of course best would be a VI and the wrapped API call.
    Any ideas?
    Scott Rogers
    Sr. DSM
    Western NY

    You could try it with a pipe. With a pipe you can open an exe, and interact
    with it through a read and write reference. Although in your case the exe
    might not start, since the normal sysexec doesn't start it...
    http://forums.ni.com/ni/board/message?board.id=170&message.id=270461&requireLogin=False
    Regards,
    Wiebe.

  • How do I keep the front panel on top of every windows (including non-LabVIEW windows)?

    The question above states it all.  Basically I have a progress bar the tells the user to wait and I want it to remain in front of anything that pops up while it is running.  My program opens up and deploys a VeriStand project and while it is doing that I dont' want the user to be able to do anything in the front panel that launches it.  When VeriStand launches it goes in front of the status window and you can't see it anymore.  I want to prevent this from happening and keep it in front of any VeriStand windows that pop up when I call the executable and the deploy an SDF.  I did take a look at the WINUTIL.llb but it keeps either 1) giving me errors or 2) not keeping it on top of anything but the main front panel.
    Any fixes or alternative solutions would be much appreciated.  Thank you.

    I did read that earlier and I just think I don't know enough of what I'm doing with library calls to make it work.  I kept getting errors and gave up on at the end of the day yesterday.  I'm working on other problems since this isn't a major one and figured I'd post it and see if anyone already had a solution to it.
    Thanks for the help though, it's appreciated.

  • Mouse click control on non-LabVIEW Windows

    I'm using an ActiveX interface to talk to Opus spectrometer software. I can pass data around and start acquiring just fine but each time I run my acquisition LabVIEW software I get a little "ok" popup message from Opus that wants me to confirm acquisition. Is there anyway I can programmatically click this box so it will go away? It is running in a different process than LabVIEW so I didn't know if that kind of mouse control was possible.

    Just check out if pressing Returen (Enter) key closes the dialog?
    If yes then download the llb located at
    http://forums.lavag.org/index.php?act=attach&type=post&id=91
    in this llb file you will get the VI to simulate the keypress.
    then as you launch application wait for some time and then simulate keypress and go ahead
    Note: This may not be very robust solution as the keypress will not work if somebody clicks somewhere on screen and application in focus is changed.
    but its quick solution
    Tushar Jambhekar
    [email protected]
    Jambhekar Automation Solutions
    LabVIEW Consultancy, LabVIEW Training
    Rent a LabVIEW Developer, My Blog

  • Non-sap screen look and feel in webdynpro abap

    Dear Experts,
    I have a Webdynpro ABAP application which is fetching data from LFA1 and LFB1.
    My client wants a non-sap look and feel onto the screen, he doesnt want the SAP Color and all.
    How can i achieve this to look it commercial ??
    Please suggest.
    Regards,
    Mamai.

    Hi Mamai,
    WDA,maintain two parameters WDFORCEEXTERNALSTYLESHEET = 'X' and WDTHEMEROOT = 'CustomerThemes".
    for ur application , add the parameter sap-ep-themeroot=/SAP/PUBLIC/BC/UR/NW5/THEMES/MYCUSTOMTHEME to ur application URL , where MYCUSTOMTHEME is the theme u have created under the path /SAP/PUBLIC/BC/UR/NW5/THEMES/ in ur system.
    Please go through this..
    http://help.sap.com/saphelp_nw70/helpdata/en/7b/fb57412df8091de10000000a155106/content.htm
    http://help.sap.com/saphelp_nw70/helpdata/en/46/89af7fbe4d429ee10000000a1553f7/content.htm
    and for custome theme..
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7015b1f9-535c-2910-c8b7-e681fe75aaf8?quicklink=index&overridelayout=true
    Re: Custome theme or stylesheet for one WD Application
    stylesheets..
    http://help.sap.com/SAPhelp_nw73/helpdata/en/47/af752005c92fe1e10000000a42189d/content.htm
    Cheers,
    Kris.
    Edited by: kissnas on Apr 21, 2011 6:44 AM

  • Labview, degrading quality editor / compiler

    Working with Labview since version 8.1, nearly 6 years ago, the functionality has been extended but the quality underneath the surface of both the editor and compiler is getting worse and worse.  Do others experience this?
    Just some observations:
    - The compiler has become a lot slower, as it seems to be doing continual consistency checks, at each run.
    - Saving a bunch of slightly modified vi's and controls has become a lot slower, as it seems to be doing a lot of continual consistency checks and preemptive/preventive corrections before saving.
    If these checks were effective I could live with the mostly unnecessarily-repetitive overhead.  But then I find that:
    - Since moving to Labview 2010, 2011 and now Labview 2013 I find myself in a position where I have to do 2 (or more) compile runs (Build .exe) of several minutes to create a single .exe.  Each intermediate Build ends with an unspecific, vague error message right at the end of the Build.  As far as I have been able to determine several of these errors have to do with corruption in the underlying database which represents the Labview code.
    - Even though it should be fixed I find that after re-linking a bunch of Property-nodes from one Control to a similar Control, the whole group of Property-nodes is linked to each other but not to the new assigned Control.  This is just an example.
    - Labels not in their default spot are still being mishandled after conversions, re-linking Controls, etc.
    Most of these issues come down to problems (or blatant corruption) in the underlying database where Labview stores your code, introduced or mishandled by either the Labview editor or its compiler.
    In stead of gradually lessen I feel these issues have become worse and worse in recent Labview versions.  Combined with all the minutes wasted by the editor and compiler trying to prevent this I would rate this as a (very) poor state.
    On a personal level I am getting to a point where I will have to advise my manager to move to a different environment for all non-Labview-essential coding.

    Norbert_B wrote:
    OK, "backwards" answer :
    The term "Crosslinking" describes a situation where a component is shared between multiple projects. So obviously, you have crosslinking between at least three projects.
    That being said, crosslinking does not need to be a problem; but it is something easily creating issues as it is a shared resource.
    Updating your projects is a perfect example:
    If you mass compile (you obviously don't do it yet) one project (e.g. "A"), all components are updated.
    After doing this, the other two projects ("B" and "C") wont open up in the 'old' LV version as the crosslinked components are already recompiled for the new version.
    There are three feasable options:
    a) Keep crosslinking. Be aware of all issues which might occur by this, but it could be an advantage (changes dont need to be deployed to each project over and over).
    b) Dissolve crosslinking by putting the shared component into each project as separate, project-specific copy. I recommend you to prepend a project abbrevation to the component during that process; otherwise, crosslinking can be easily re-introduced.
    c) Separate Compiled Code from VI. This is an option NI added to LV 2010. This will add overhead to the development as each machine has to recompile the VIs after opening them (no compiled code in the VI file!). Advantage is that each compilation can be system specific and re-compiling doesnt modify the VI-file.
    It sounds as if you are using implicit bound property nodes. Do you have an example VI where we can reproduce the issue you are seeing?
    Yes, building an application can be tricky from time to time. Another source of errors i forgot to mention are conflicts in the project. Rule of Thumb: Never try a build if there are still conflicts displayed in the project explorer. Do you already follow that rule?
    Please try running the mass compile before working on the project in the new version. Opening the top-level VI(s) and saving is most often not sufficient. This recommendation is 'invalid' regarding your base libraries if you chose to go for option c) mentioned above. Reason: Compiled code is not part of the VI-file, so the compiler has always to recompile all VIs once they are opened first time on the machine.
    Norbert
    Norbert,
    I did a couple of mass compiles to tackle a few "Nonfatal insanity" (talk about "Backwards" ) errors I had, and which mysteriously dissapeared.
    What I do is open each project seperately and save any updates it wants doing.  This -should- do the same as a mass compile.
    And this brings me to one of the main issues I have with Labview:  I constantly have to avoid a straightforward solution because of shortcomings in Labview.  The alternative is just as bad: I have to create examples of bugs to be used on this forum and go through all the effort of generating bug-reports.  A process which has already amounted to several working days of my (and my companies) time so far, to discover none of these bug-reports have been solved a year later or are even mentioned in the "Known bugs" list.
    I will have a look at your suggestions to see if somehow I can make this into a manageable working procedure.

  • Labview 8.5 project crashes when searching for callers of missing lvlib

    I have done a search and reviewed previously reported crashes with LV8.5, but did not find a match to what I'm seeing.
    SYNOPSIS: When selecting Find > Callers, under the project Dependencies, LV crashes as shown in the image below.
    I created a new project and "borrowed" some vi's from another project.  Disconnected all vi's from previous libraries and proceeded to develop code last night.  All seemed well.
    This morning, as I opened the project to continue coding, it complained about a missing lvlib, the one items were "borrowed" from.  No big deal, I'll just look at the dependencies and find out which one I missed.  When doing the search, the program crashes immediately.  Repeated a number of times with the same result.  Verified system performance and memory useage, minimal change when opening the project or attempting to do the search.
    I will attempt a workaround, but I am curious if others have seen this as well. 
    I'll wait before reporting this as a "bug", until more info is gathered on this.. 
    By the way, the original lvlib was NOT deleted, removed, moved, renamed as the error suggests..  LV actually knows where it is because it finds the directory when doing the search..  
    I know the routine, "simply re-install LV8.5", but I'm trying to understand more of what's gooing on and how we can avoid this..  I remember LV8.2 was crashing a lot at the beginning, then for no apparent reason, it became stable, and now I can't remember the last time it crashed..  Do others observe the same thing?  LV gets more stable with time??  LOL!  A program with personality.  Will LV turn into HAL?  LOL!!
    Here's the picture:
    Message Edited by JoeLabView on 02-13-2008 08:35 AM
    Attachments:
    LV8.5ProjectCrash.PNG ‏38 KB

    Good morning Jennifer,
    I'll try to re-create the events from memory. 
    OS:  Win-XP Pro - SP2
    1. Opened library of VI's from Agilent E4440A drivers.  Opened the "Tree.vi" to look at available vi's.  Copied (pasted) some of the vi's into a new folder.   This may be important: I deleted the folder that contained the original library.  (Actually, the zipped file was moved to a storage location).  This means LV has no idea where to find the original library.
    2. Opened all freshly copied VI at the new folder location.  They all complained about not finding the .lvlib file.  Ignored the error and disconnected every vi from the library and saved them.  All except for one which was polymorphic and I didn't need it. I forgot to delete it at this time.
    3.  Created a new folder (real) within the directory structure of an existing project which uses an lvlib. Moved the disconnected vi's into this folder.
    4. Opened the project and added the folder to the project, thus creating the virtual folder and files that were in the folder.  All this was added to the library.
    Note..  I can't remember the exact steps below, but they were something close to what I describe.
    5. Cannot remember if I closed the project then opened it, but I do remember seeing a message complaining that one VI could not find the lvlib (the one from Agilent).
    6. Looked into the folder and examined the saved date, which quickly led to the polymorphic VI that was still part of the original library.  Since I was not sure if I wanted to use it later, I simply changed the extention from .vi to ._vi_.
    7.  Did some work, saved everything. Closed the project..
    8. Opened the project and got an error message about a missing .lvlib.  Again looking for the original Agilent lib. Remember that I had deleted the original library, it's folder, etc. (step 1).
    9. Everytime I would open the project, I would get the error message.  I ignore it and continue working.  Since I don't like errors , I looked at the dependencies to find out what I missed. At this time, the file with the ._vi_ extension was still in the folder.  I had forgotten about it and didn't realize that LV would pick it up.
    10. In the dependencies tree, I right-clicked the error message and selected "Find>Callers", as shown in the attached image of the original post. Got the crash message.  I repeated this 4 times.  Rebooted the PC, and repeated it twice. All the same result >>  Crash.   I may have saved a copy of the "crash" report, although I doubt it...  I didn't bother sending the report to MS; because, well, I don't have much credibility over what those guys do at MS.
    11. Looked at the folder to go through every VI to find out which one was still connected to the library.  None of them were.
    12.  Noticed the ._vi_, and figured there would be no harm to delete it.  Deleted it.  It resolved the dependencies, thus no more error, no more crash.
    I am actually surprised that LV project also looks into non-DOTvi files for dependencies.  I imagined that it would ignore anything non-Labview known extentions.  This is definitely good to know.  However, the crash was a bit unexpected.
    I will look for error logs.  If I have time, I may try to repeat this on my PC and send logs.  It will have to wait until I finish my surrent project (client / revenue)
    Hope the above helps.
    RayR

  • TestStand sequence launchs Labview Window

    When I open a sequence in TestStand 3.5 consequently Labview is opened. But I have a test bench where this doesn't happen. (note: the bench are software and hardware identical, but assemblied in different moment). Moreover, when I launch my testing application (that recalls a teststand sequence), on the first bench appears always the labview window, while on the second bench none labview window is opened.
    I'd like to reproduce the second behaviuor: none labview window is opened.
    There is a particular setting in teststand to block the labview window?
    Note: the testing application and sequences are the same on the two benchs. The bench setting are identical. I controlled every setting between the two benchs.
    Solved!
    Go to Solution.

    There is a setting that I just found out about in the LabVIEW.ini file.  It disables the Getting Started Window dialog on LabVIEW 8.6.  It might work on LabVIEW 7.1 and may be present on one of your two test computers.
    Can I Disable the LabVIEW Getting Started Window On A Macintosh?
    The setting is "showNoNavDialog". Look on your computer that is behaving as desired and see if this setting was added (would be set to TRUE).
    \Program Files\National Instruments\LabVIEW x.x\LabVIEW.ini
    Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
    If you don't hate time zones, you're not a real programmer.
    "You are what you don't automate"
    Inplaceness is synonymous with insidiousness

  • Communicating between Labview RT code running on windows using Linux C code over network

    Hi,
    I have been working with Labview FPGA+RT for robotic applications (impedance control, tendon driven robotics etc.) for some time now. I was wondering if anyone has successfully been able to communicate with
    shared variables being sent over a network by a labview RT program using C/C++ on a non labview Linux PC. I have been working on this for sometime and have read about CVI and Datasocket protocols. I am in the
    process of making a library on my RTAI patched Linux installation to have a high level control loop on the Linux PC communicate with low level motor control and sensor data acquisition codes running on the labview RT
    pc. In the worst case scenario I am planning to use basic network port sniffing to atleast acquire data.
    Just thought I will ask here before wasting time reinventing the wheel. Any suggestions and ideas would be greatly appreciated as well.
    Thank you for your time.
    Prashant

    Morning Prashant,
    You are on the right track. You can use datasockets from any environment to interface with a network shared variable. I've pulled some of the examples from CVI which show how to call network shared variables. These should help. You should search how to call data sockets in C then pass the address to them to read and write from. 
    Look into the polling example for the basics.
    Kyle Hartley
    RIO Product Support Engineer
    National Instruments
    Attachments:
    networkvariable.zip ‏69 KB

  • Runtime tab canvas does not look the same as designed in layout editor.

    I created a tab canvas with the following physical properties:
    Corner Style - Chamfered
    Width Style - Variable
    Active Style - Bold
    The canvas looks nice in the layout editor, with the above properties. However, at runtime, the tab canvas seems to ignore the above properties and instead shows up with non-chamfered looking (whatever chamfered means) fixed-width rectangular tabs and the active tab page label is not in bold font. Is there a runtime setting that I'm missing here?
    null

    I am experiencing the exact same thing. The width of the tabs in the layout editor is varied depending on the length of the text. However, at run-time, the width of the tabs is fixed, causing the tabs to be wider than the window and a set of VCR buttons to appear in the upper right corner of the canvas. Personally, I think this is a Forms bug. Why would they intentionally let us set the width to variable at design-time only to force a fixed width at run-time?

  • Is there a way to make labview messages always appear on top of all windows?

    I have a main VI running and a user selects a non-Labview window to work on. Is there a way make the user prompt or user input express VI messages appear on top of all windows? I have experimented with the "make window always on top.vi" from the NI website. That brings the VI that is running to the top but not the prompt for the express VI message. I have also used the "make window always on top.vi" in a sub-VI and called that sub-VI to be always on top and it works. I was just wondering if there was a way to do it with the express VIs that NI already has written instead of making a custom message the way I have mentioned.
    Thanks,
    Troy

    If you only need to display a prompt and can get by with a limited set of canned buttons (OK, Cancel, Retry, Continue, etc.), you can try a VI that calls the Windows API MessageBox function. You can display a message box with user-defined title, text and buttons. There is an option to use the system modality which is what you want in this case. I use my own version of this all the time for that very reason.
    Message Box

Maybe you are looking for