Convert DAQmx task to code in LabVIEW NXG

[Austin-Downey]

Greetings, 

I am new to NXG but not to LabVIEW. I generated a task in the front panel like the one below, 

Is there a way to convert the task directly to code? Or do I have to build this up by hand. For example, I want code in NGX that looks like this:

Thanks

[cbutcher · Accepted solution]

Hi Austin,

I don't know the answer to your question, but I wanted to post to make sure you'd seen this: Our Commitment to LabVIEW as we Expand our Software Portfolio (end of NXG development).

I suspect the answer is unfortunately that you'd have to build the code in your image up from scratch, but if the task varies, it might be possible to extract some information from the task? (In LabVIEW, you could do this with Property Nodes etc, but I don't know about NXG).

[Austin-Downey]

Thanks!

Well it's not the answer to my question, it is the answer to the problem. I was only looking at migrating to nxg because I thought it was the new labview.

So the question is now, will I be able to zoom in on labview? My eyes aren't very good and the fact that I can't zoom in is the one thing that makes me want to give up on this.

[cbutcher]

Zoom! The debate continues - unfortunately for you, the Idea Exchange post here (Add a zoom function) is already marked as completed, thanks to NXG.

The comments there are continuing regarding LabVIEW 202x, but whether it will change I don't know.

Some changes from NXG will make their way 'back' (forwards?) to LabVIEW 202x, but I have no idea as to timelines, priorities, etc.

You can post on the Idea Exchange to try drag it towards the top again, but I don't think that NI don't know people want this (it has been wanted for at least a decade, I think...)

[Yamaeda]

---

@Austin-Downey wrote:

Thanks!

Well it's not the answer to my question, it is the answer to the problem. I was only looking at migrating to nxg because I thought it was the new labview.

So the question is now, will I be able to zoom in on labview? My eyes aren't very good and the fact that I can't zoom in is the one thing that makes me want to give up on this.

---

I sometimes use Windows Magnifying glass for that. Especially if I need to work on my laptop and there's some multi input VI.

If you have 2 monitors you can use the 2nd one as a constant zoom in, or just have the zoom window in a corner. But I agree, a real zoom in is handy at times.

[Austin-Downey]

I try to be a positive person, but NI's lack of ability on this is pathetic. I have to buy special low-resolution monitors for my lab and crappy old laptops to run LabVIEW. 

[cbutcher]

Although I agree that the DPI scaling settings/behaviour with LabVIEW (at least on Windows) are pretty annoying, you can use them to 'solve' this problem if it suits your needs.

In multi-monitor setups with different resolutions, it causes a different problem though...

If you set the DPI scaling higher (than 100%) then LabVIEW (after restarting the application, not just libraries/projects etc) will respect that change. This can help on high-res monitors.

However, if you have two monitors and they have different DPI scaling (say a 1920x1080 at 100% and a 4k at 150%) then your right click menus will not line up with the cursor properly on the second monitor (where 'second' is whichever LabVIEW didn't launch on, I think).

As a result, I just run both of the monitors on my desk at 100%, and if I need to see something in closer detail I move it from the main 4k monitor to the vertical 1920px monitor off to the side (acting like a constant zoom, as Yamaeda mentioned).

The high-res, standard scaling configuration is really useful for opening a bunch of VIs at the same time and checking multiple block diagrams - this helps me 'look through' execution flow and so on (or compare dynamic dispatch overloads, etc).

(It also helps when downloading some forum code... 😉 )