coco822

Thank you for your reply, it is indeed a possibility (of which I was unaware) so thank you very much.

Have a nice day.

Hello,

I wanted to use a PictureBox in .NET and perform actions when I moved the mouse.
That's when I noticed that the "Mouse Move" event was detected when I was moving around the .NET Control, but that this was no longer the case when the mouse was pressed down.

If anyone has any idea how to detect the "Mouse Move" event when the mouse is pressed, and if not, I'd like to know what the mechanism is behind this failure to detect the event.

Attached is a VI showing the behavior.

Thanks in advance.

Mouse Event over .NET Controls.vi

Finally it seems that the build error (when there is no block diagram) is related to the VIPM version.
When compiling with version 2020.1 there is no problem.

Hello,

I am working on a function library and I want to package it with VIPM.
On this side I have no problem, my problem appears when I want to remove the block diagram of my VI in order to protect my source code.

I first tried to use the pre build actions calling a VI using scripting to remove the block diagram from my VIs (something like below). However when I do this I get this kind of error message.

It seems that we cannot remove the block diagram before the build.

My question is "How can we remove the block diagrams from a post build action ?" 

After some research, I came across this post  in which Jim Kring says "This should be possible with a custom post-build action VI", however he does not explain how to achieve this.

I was able to remove the block diagrams using the post install actions however my goal would be to remove them with a post build action. 

18 minutes ago, Rolf Kalbermatter said:

IMAQdx Open Camera VI accesses the IMAQdx driver API which only can recognize certain types of cameras that must themselves somehow announce to the system.

For Webcam cameras this happens through the dedicated camera driver that is installed in the OS system and which installs the camera in the Windows DirectShow system which IMAQdx can access. For other Cameras it depends on the camera. Firewire cameras install in the Fireware driver stack which IMAQdx also can access. But Network cameras are an entirely different beast. IMAQdx has functionality to work with such cameras as long as they support the Genicam standard, which is part of the GigE standard (although not every GigE camera implements this properly and therefore may not be compatible with IMAQdx). Any other camera is NOT automatically supported by IMAQdx. If you want to access it in IMAQdx you have to install them as a Windows DirectShow device with an according DirectShow or kernel driver. In your case you are wanting to find most likely an RTP-UDP DirectShow driver for your camera. There are many around on the internet, most not for free, and all of them require you to setup the actual camera URL in the driver settings.

Thank you very much for this comprehensive answer. 
I will try this.

Hi,

I’m trying to interface a camera using the UDP protocol thanks to Vision, unfortunately i struggle to detect it with the « IMAQdx Open Camera VI » or NI MAX.

However, I can get data in string form when I use the classic VIs during a UDP communication, which means that I can receive the data from the camera but I can't get it under Vision.

Does anyone have an idea how to solve this problem?

Thanks in advance

Camera UDP.vi