Supposedly there are Labview tools available at
But whenever I try to register or login, nothing happens. (Also, I try to think, but nothing happens.) Are there any other Labview codes that use the Windows Memory-Mapped Files functions, or should I just reinvent this wheel? By the way, here is a Microsoft document on the subject: https://msdn.microsoft.com/en-us/library/ms810613.aspx
We use USB-connected Microsoft Smart Card Reader. The devise crashes sometimes. It does not happen often thus search for the reason could take time.
The only way to get the devise functioning again, is to open Device Manager, click Uninstall then Scan for hardware changes (that installs the Reader again).
Is there any method to do this from LabVIEW? I.e. send commands to reinstall the USB device?
I know this could be a bad fix. However, it can help in long-time tests (while we are searching for reason of these crushes).
By Jillu Pravin
Hi all ,
Need help regarding the Vi i have made which works fine with labVIEW pane.Which i need to capture in windows screen.
I have attached the vi which works great in labVIEW pane and records each event of click inside the pane.i haven't find any options in event structure for capturing mouse events out side the pane (ie which captures windows UI ) . I know i could make it with while loop capturing mouse coordinates still i feel its not a reliable way to record .So please let me know how to make it in Event structure or is there any reliable way to make without event structure.
Capture tool LabVIEWpane.vi
Good morning everybody,
I'm new to the forum and I'd like to show you my last creation as a presentation.
It is called Hackman, and it is a PacMan clone I've made while trying some OOP in Labview.
I have programmed chasing and moving methods as in the original arcade.
From the website http://hackyourpack.altervista.org/
you can download the executable... If anybody's interested I can provide source.
It is keeping track of the global high score.. so try it and put your name on it, so everybody will know your mastery!
I'm experimenting with porting my existing LabVIEW application from Windows to Mac OS X. The code uses several instances of 'Build Path' function in 'File I/O' functions sub-palette. The 'Name or Relative Path' input is being connected with a 'string' data type rather than a 'file path' data type. With some quick code change and checks, I've realized that it's better to use the latter data type, so that the separator character '\' in Windows is automatically interpreted as ':' in Mac OS.
Some parts of the code, however, build up the string. E.g. a 'Format Into String' is used to output based on a format string, e.g. 'Images\%s.jpg'. Doing a 'String to Path' after this function does not automatically interpret the '\' in Mac OS to ':'. (I can imagine that it would be difficult for the compiler to recognize that a specific character is meant to be a separator and not part of a file/folder name.)
I can write more complicated code where the format string is itself concatenated based on the execution platform. Are there any easier or recommended approaches? Also, does LabVIEW have any 'File Constant' that provides the equivalent string character depending on the platform?