Jump to content

Neil Pate

Members
  • Posts

    989
  • Joined

  • Last visited

  • Days Won

    82

Neil Pate last won the day on September 22

Neil Pate had the most liked content!

5 Followers

Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 2020
  • Since
    2004

Contact Methods

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Neil Pate's Achievements

  1. This is how I include the RTE as part of an installer. Note: outside of the scope of the installer I manually unpack the relevant NI distributed RTE
  2. I would definitely not use a Swap Values here as it just makes the code confusing. Of the three I think the top is the most natural (but there is something about the inner dequeue which does not sit well with me).
  3. I just include the whole runtime and don't bother trying to cherry pick the perfect dependencies. I did try this once upon a time but could never figure out the right dependencies.
  4. Nice idea hooovahh, I did not think to solve it this way. I already have a nice Steel Series mouse which comes with a macro configurer and I have some set up for LabVIEW but I always forget to use them! This might be one I remember to use 🙂 My problem with using the middle mouse button is that unless other applications use it already (like Chrome or Firefox to close tabs) so you need to make it application specific. My Steel Series configurer has a way to do this but it seems to be a bit clumsy especially when dealing with multiple versions of LabVIEW and then switching over to a browser mid session. Is this XMouse Control thing any good?
  5. Today I Learned: you can pan around the block diagram by pressing Ctrl-Shift and then clicking and dragging the left mouse button! Not as useful as middle button dragging, but still interesting.
  6. As suggested here This is something us LabVIEW devs have gotten used to not having but is now so common in other graphical tools. Pan to scroll the block diagram or front panel seems like something I would actually use quite regularly.
  7. Another option... Use a third party installer. InnoSetup works really well.
  8. We could always just make dumb posts and rate each other 😉 For some reason this seems appropriate...
  9. Yeah that sounds familiar. A terrible workaround would be to make a transparent button with your cool symbol on it and overlay it on the row header, and have it intercept the click event. I have to do crap like this so often in LabVIEW to get nice looking GUIs 😞
  10. Just be careful. Weird things sometimes happen when you change the font of just some of the text in a table. I recall trying to get some Greek characters into a table and header and I could not make it work properly. This was waaay back in 2010 so things might have changed. Please let us know if you get it working nicely!
  11. One simple (but mostly unsatisfying way) is to make it up out of other characters. \/ /\ For example see how it is done in VIPM.
  12. http://localhost:3580/dumpinfo? Found in this knowledge base. If you are not able to access this page from another PC but it works ok on the local machine you will probably need to get port 3580 opened up.
  13. Sorry I thought I had replied here, but it looked like I did not click Submit! Thanks for everyone's comments. I have passed them on to my customer.
  14. A bit more information. According to the Dependencies application the LV2020 also has a dependency on this System.dll that is located in the GAC. I have tried copying that DLL to various locations (I think I am not supposed to because this is system stuff!) but it still gives me the same error.
  15. Recently I have tried to package up some code as a .NET Assembly. I managed to pack some pretty complicated LV2019 code (including some LabVIEW classes and dynamically called code) into an assembly and was able to call it just fine from a simple C# console application. However, this does not work when I moved over to LV2020. To make things simple to try and get to the root of it I created the simplest possible example I can think of. One copy is in LV2019 and it works fine, the other is LV2020 and it does not work. The assembly builds fine in LV2020, and indeed is callable from LabVIEW code. The test is just a simple Increment VI. This works fine when the assembly is built using LV2019, the num variable is correctly 2 after running this line of code. However in LV2020 I get the following exceptions after running that line System.TypeInitializationException HResult=0x80131534 Message=The type initializer for 'MyAssemblyNamespace.LvClient' threw an exception. Source=Increment2020 StackTrace: at MyAssemblyNamespace.MyTestClass.Increment(Double input) at Increment.Program.Main(String[] args) in C:\dev\Scratch\DLL Build Test (2020)\Source\C#\Increment\Increment\Program.cs:line 10 Inner Exception 1: FileNotFoundException: Missing Dependency in: Inner Exception 2: VIAssemblyException: Missing Dependency in: I have tried playing around with including the LabVIEW Interop assembly in the C# application (C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2019\NationalInstruments.LabVIEW.Interop.dll) and changing this to 2020 for the LV2020 version, it does not seem to make any difference. The LV2019 version runs without this assembly included in the project. Is this something to do with the GAC? This is now getting into the details of .NET that I am not really very familiar with. Does anyone have any tips for things I can look into? I have attached a zip of everything for anyone curious. Build Test.zip
×
×
  • Create New...

Important Information

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