Neil Pate

And 2015

Thanks hooovahh, I did try changing the device ID in windows, something happened in that my sound went "away" from the PC speakers, but I could not find the right device for my headphones. I will play a bit more.

Anybody been able to play sound through the headphone output on a PC? I have exactly the same issue as here. All my other Windows apps play nicely, I can divert sound to my headphone output as needed on the fly using the Windows 10 sound "thing" down in the taskbar without changing any settings in individual applications, but LabVIEW refuses to play on anything but my speakers.

Zyl, personally I trust Bitbucket and their IT staff with backing up my data way more than I trust my Synology NAS (which is great by the way, I have a two bay RAID1 setup and I use it as an additional backup device). LabVIEW knows nothing about my VCS, I do not bother with locking or anything like that. The only setting relevant in LabVIEW is the separate compiled code which helps prevent the old problem of LabVIEW wanting to save 500 VIs just because a typedef changed. Merging can be tricky but if you communicate things properly with the rest of the team and agree who gets to touch what I find it is generally not a problem. (Use Slack, it is a super tool).

I switched over to Mercurial from SVN about five years ago and have never looked back since. I work remotely to the rest of my teams and find the DVCS nature a very good fit. Actually it was a good fit even as a sole developer. I use Bitbucket for hosting, very reasonable price for small teams (free!) I use the TortoiseHg plugin for Windows, I usually version my entire directory which contains docs, source, builds etc. (Not installers though, they cause the repository to get big very quickly).

Yup, that is the key LogMAN referred to in his post. Switching off auto-wiring also fixes the problem. That is the one problem with the beta, I always run it in a VM, so issues like this I assume are just because the VM is getting in the way.

Doesn't seem to have made it into plain 2017. Not sure when SP1 is coming out as now they have moved the release dates around. Perhaps before the end of the year? Not really sure how stuff like this makes it into production. I have a *beast* of a dev machine and am working with a tiny block diagram at the moment but still the grey selection colouring feels so sluggis

Thanks, that partially solved my problems. Dragging in from a different VI works properly now. Still cannot turn off that stupid grey filled selection box which is so sluggish.

I am pretty sure I saw somewhere on the darkside (perhaps in the beta discussion) there is a LabVIEW.ini key to turn all this "goodness" off. I cannot find the thread now that I need it.

I am just getting started with LV2017 on a new project, and have found some horrrible IDE "improvements" that are messing around with my work-flow. The first one is auto-wiring when you drag code into a stucture (as discussed here). My latest gripe is strange behaviour when dragging a VI from one BD window to another. I do this operation quite a bit to copy code. In LV2017 now when I drag a VI in from another VI as soon as it enters the new VI (but before I have released the mouse) it is as if the block diagram of the target VI only refreshes like once a second and so I see my VI jerk around. It does this the primitives as well as other VIs. I cannot comment about LV2016, but at least in LV2015 and every other version I can remember, dragging a VI from one block diagram to another was butter smooth. Anybody else seen this or is it just me?

Found this on LinkedIn. https://0patch.blogspot.co.za/2017/09/0patching-rsrc-arbitrary-null-write.html Not going to pretend I follow most of what they are talking about, I am just surprised that something as niche as LabVIEW is even being tested for vulnerabilities.

I have fought this for close to a decade trying to get a slick splash screen that does not exhibit some stupid behavour like spawning before the application is even ready to run (so showing toolbars etc), not being centered etc. I currently have the same code that works differently on difference PCs due to their speed. Eventually I just stopped getting annoyed by ignoring everything as virtually nobody even comments on it.

I have just wrapped the VI mentioned by the link hooovah posted in some code that iterates over all the classes in my project. I really have no use for the mutation history and wish I could permanently turn it off. Also I think it is buggy especially when classes contain classes that have changed or been renamed. Seen some terrible IDE bugs related to this.

Yup we were trying to be positive. I have not experienced too many crashes involving classes lately although I do purge the mutation history every few weeks (No problems with a medium size project including approx 85 classes).

I have had good success using the NI Database toolkit.

I usually have one user event per "actor" which is used to broadcast when its state changes. Recently I have been playing around with not using the event data terminal and instead having a global data repository implemented using a DRV to a variant (with the data stored as named attributes), the actors user event data is a timestamp that I set when I generate the event. If I had a cent for every time I have created and deleted the register event terminal which never propagates properly...

Even to this day when I open a random VI from my project, click run-continuously and quickly iterate through some input scenarios to make sure the VI is still working as expected makes me smile. No additional code needs to be written to quickly test a single VI, I just love this

James I agree, I did report the post a few days ago.

Managed to get this working in the end. http://labelary.com/viewer.html

That file format looks an awful lot like the one used internally by LabVIEW if you use DAQmx channels in the project. A long time ago I asked if there were any available tools to parse these files (as they are read at runtime in a .exe) but did not have any response.

Nice tip, thanks! I tried that and it seemed to generate some sensible ZPL. Interestingly it is using ^GFA rather than the ^GFB which I was trying to use. I do not have access to the printer anymore but should be able to test soon.

Thanks Phillip, I did actually try there first, there are some nice threads on zebra specific stuff, but the forum would not allow me to post for some reason! Will try again.

Firstly, although I was able to get the custom VISA driver to work (USB Zebra printer) I have reverted back to this technique for getting the printer to work. Have had good success with it. Now onto my problem. I want to print a logo on a label and am struggling to get the ^GF command to work properly (with binary data). I can successfully print a stripe pattern but am not having any success printing the actual logo. In the attached code (very rough prototype code just to get me up and running) I can print a stripy pattern (0xF0, so 11110000 alternating gives me columns of printing in the desired dimension) if I change the selector input to a T (to print my bit-packed logo) nothing prints and the printer seems to get stuck. I do not understand what the problem is as I just assumed, even if my logic for packing the logo into bits is incorrect, I should still get something printed. If I force the top bit high in my bit packing routing I get something printed but obviously not what I expect. Any ideas what could be wrong? I have tried lots of variants of this code without any success. I am stumped why it does not print. My only conclusion is that Windows is mangling the string commands because technically I am sending null characters and backspace etc in my binary data, but I really just assumed the printer would interpret this stuff correctly. logo (64x64).bmp Print Test 5.vi

Rolf, I did see the Rect input, but at the time I did not really consider it useful as I did not know that the problem was related to the image size. Now that you have pointed this out I think that would definitely have helped. I am still getting strange out of memory errors which I have no been able to track down but I strongly suspect are also due to the Picture control functions. Time to use the Rect input I think!

I do not do too much vector darwing, but under some (error) circumstances I have realised the coordinates of my drawing instructions could actually get quite big (as in 32k *32k), I just assumed the picture would be constrained in size to the size of my pixmap data which is not huge, but probably given what you say this is actually causing the out of memory error. Knocked up a test VI to simulate this error condition and I think this is exactly what is happening for me. A line being drawn from (0,0) to (32000, 32000) and then an attempt to get the pixmap will definitely cause problems!