Jump to content

chigaitakanoha

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by chigaitakanoha

  1. Has anyone here ever used BlockCopy function for a library written in .NET (C++/Cli) ? https://forums.ni.com/t5/Developer-Center-Resources/Dereferencing-Pointers-from-C-C-DLLs-in-LabVIEW/ta-p/3522795
  2. Thank you Smithd, I am able to access the managed memory space. I am trying to access the native memory space. So what has been done is this I have a buffer in the native and that's marshalled and stored in the managed space for LabVIEW to access. I am trying to access the native buffer from LabVIEW. Thanks,
  3. Hi, I have a DLL written in C++/CLI and have a property available to LabVIEW to access the native memory space, but from the property I can't use examples described in this link: https://forums.ni.com/t5/Developer-Center-Resources/Calling-C-C-DLLs-Containing-Simple-and-Complex-Datatypes-from/ta-p/3522649 Is it because the DLL must be written in pure C/C++ instead of C++/CLI (.NET) ? Thanks!
  4. Hi Michael, Yes. I played with it the source distribution. After building with it I see a new folder "My Source Distribution" and all my VI files and the dll are inside. It seems that everything was just copied into one directory - this is not so different from just zipping the folder.
  5. Hi I have a question about general rule of packaging and distributing LabVIEW code. I have a LabVIEW project (please see below tree structure) which contains numerous VI sample code which invokes function calls in the dll (PVCamNET.dll). As the project needs to be shipped to the world I would like to package it more professionally than zipping the entire folder. Note the folders, DemoApp and Examples contain VI code. Looking at the build specifications there seem to be many options for packaging. I have a DLL enclosed in the folder and besides the VIs the DLL must be part of the project. My question is quite simple - what is the best way to package this project for the user to play with the VI code ? Thanks!
  6. Hi Mikael, Thanks for taking a look. Does my explanation make sense to you ? I don't know why the width of the slider changes as new data arrives. For the slider I set the minimum to be 0 and maximum to be the BufferSize and x to be the index that gets updated from the callback. I don't understand why it behaves like this in the video.
  7. Hi I wrote a live acquisition vi to acquire data from the camera to display the buffer index on the scroll bar, but it seems to act strangely. I expected the scroll bar's slider size to be 1/(max size), but it starts from 1. As an example, when the first frame arrives then the scroll bar's slider size is equal to the UI element's width. When the 2nd frame arrives then the scroll bar's slider size becomes the half of the UI element's width. Similarly when the 3rd frame arrives then the scroll bar's slider size becomes the 1/3rd of the UI element's width and this continues... Please see the video in the following link: https://yoshidad-gmail.tinytake.com/sf/MzA2MTc5MF85MTc2NTc2 Please see attached VI as a reference. Thank you! 1106_ni_request.7z
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.