jacobson

A while ago I developed an Xnode that has an ondoubleclick ability which opens up a configuration window. I noticed that every time that ability was called, even if you immediately closed out of that configuration window that it would produce a dirty dot in the owning VI. This seemed to happen with the ondoubleslick and onoperateclick abilities even if there were no replies or added code to the abilities themselves. I attached my Xnode which demonstrates this behavior. I was wondering if there was any way to prevent a dirty dot in the owning VI if nothing has changed in the Xnode's state or generated code. -Matt J Random Xnode.zip

If you want to use the New VI Object VI to insert a custom control you need to feed it a valid path and set the Class input to GObject or a class it inherits from. I would be interested to know if there is a way around this but I think you will also need to save the .ctl (at least temporarily) so you have a valid path to reference. To explain the error you were getting, you were telling LabVIEW to put whatever was at the path "Control 1" into your new VI. That isn't a valid path so LabVIEW just gave an error saying that it couldn't create that object. -Matt J

Great series of articles. I appreciate how you took a lot of time to explain where all of the actions are really taking place, like helpers and good methods to override. I haven't taken the time to really investigate AF (I really need to know OOP better first) but other documents I read went so far into the messaging that I could never figure out how you were supposed to do anything once the message reached its destination. -Matt J P.S. small writing mistake in part 4 in "Doing Work in Messages vs in the Helper Loop where you say, "The helper loop would then start working through he file."

Disclaimer that this is from the perspective of someone who helps people who call in to NI with problems rather than a developer If you have not built an application using RT/FPGA, are very familiar with DAQ, and do not need to use the FPGA for any of the reasons smithd mentioned I would agree with using the cDAQ controller. You'll probably save a lot of development time if you stick to something you're comfortable with. In terms of general use and debugging for your real-time application, it will feel very similar to testing and debugging a windows application. When you click the run arrow on your VI it will deploy code to your target (minimal time) and you will be running your code interactively which means the application is running on the remote target but still gives you access to most of the normal debugging tools. When you are done and want to deploy an executable, you can build an rtexe and set that to run when your target powers on all from your project. You can troubleshoot this the same as you would a debuggable executable running on a separate computer. FPGA is a separate beast and it does add to development time as people have mentioned, especially if it's your first time. I think RT is pretty good once you get past the whole finding the target in MAX part. -Matt J

Thanks, I'll have to take a look at that plugin. If you invoke the menu from a wire, where is the location of the wire though? My first guess would be the center of the wire but I'll have to test it out with different configurations. Matt J

I am finally checking out the new 2015 feature that allows you to add features to your right click menu and was having trouble figuring out how to do something. I wanted to start with a very simple project that would allow you to create an IMAQ image container when right-clicking on an image reference wire/node rather than just a reference. What I cannot figure out is how to get the location of where the user spawned the right-click menu. I want to mimic the behavior or creating an indicator from a wire where it will place the block diagram terminal where the user right-clicked. Any help would be appreciated. Matt J

And I finally learn what that QD shortcut does. I'm also surprised you would need a license to view certain properties but I guess I will have to check that. Do they not show when Xnodewizardmode is enabled as well? Edit: You are correct Hooovahh

Still sold as far as I know. The price is listed as contact your sales representative on the product page but not cheap would be the answer.