By Gan Uesli Starling
We have a gage supplied by a company that shipped it with a *.exe application targeted for LVRTE 2009. I need to retarget it for 2017, but don't have the source code. The supplier had said they'd gladly supply me with a copy of the *.LV source, but they have looked and cannot find their own copy in-house.
History of Need: Our global corporate mother ship's IT department, in their infinite wisdom, is mandating an upgrade from Win7 to Win10. That with yet even further constraints. They enforce a list of "approved versions" of "approved applications". And for LVRTE, they are insisting upon 2017, with 2009 being a red light.
So, then, my query. Is converting an app without the source for a higher LVRTE doable at all? File is attached.
If it is doable, instructions on how?
I'm trying to execute LPR.exe command to print some labels on a printer. However as its normal, problems occur. I could not find answer on any topic conneced with "sytem exec". I already tried all described methods (I think so). That's why I'm asking very kindly for any help.
When trying to execute or call the LPR.exe from System exec VI, I'm receiving error:
"'C:\Windows\System32\lpr.exe' is not recognized as an internal or external command, operable program or batch file."
Generally I would like to call function: "lpr -S 192.168.1.5 -P lp C:\test\do_druku.txt" which works from command window without any problem.
Out of the box text in the icon editor looks awful. (See attached image, which is better looking than most.)
(Yes, even with small fonts: https://forums.ni.com/t5/Linux-Users/Labview-Icons-under-GNOME/gpm-p/3379530.)
LabVIEW 2016 64-bit, CentOS 7 Linux OS
We have tried many things to get this to work, to no avail.
Does anyone have a solution?
I wanted to cross post metux's discovery here asap, and have a separate discussion.
Metux's original post:
The recent Linux driver package introduces a CRITICAL security vulnerability:
It adds additional yum/zypper repos, but explicitly disabling package signing and using unencrypted HTTP transport. That way, it's pretty trivial to completely takeover the affected systems, by injecting malicious packages.
DO NOT INSTALL THIS BROKEN SOFTWARE - IT IS DANGEROUS !
CERT and BSI are already notified.
I have never gotten the performance that I desire out of the 2D picture control. I always think that it should be cheaper than using controls since they don't have to handle user inputs and click events etc. But they always seem to be slower.
I was wondering if any of the wizards out there had any 2d picture control performance tips that could help me out?
Some things that come to mind as far as questions go:
Is the conversion to from pixmap to/from picture costly?
Why does the picture control behave poorly when in a Shift register?
What do the Erase first settings cost performance wise?
Anything you can think of that are bad ideas with picture controls?
Anything you can think of that is generally a good idea with picture controls?