Jump to content

All Activity

This stream auto-updates

  1. Today
  2. I reported all of them last week. Did not notice at first either but in the last post somehow the link sprang in my eyes and I was first thinking it was a special name for quote marks wondering what that word would mean. 馃榾 Google quickly taught me that it is some drugs name and from there it was obvious. Then looked at the other 3 before that and saw the same pattern together with a pretty meaningless message.
  3. How do you figure out the dependencies? My eyes just glaze over when I look at this screen:
  4. Buenas tardes, estoy usando tu proyecto, y quiero ver si puedo tener tu autorizacion para poder usarlo junto con el mio, mi corres linkzelda60@hotmail.com espero no ocasionarte problemas muchas gracias

  5. Is it ever conceivable that there will be more than two Queues to monitor? If so then the last one would scale up better. That being said it isn't the one I'd find myself using, just because the other two are much more readable. I'd probably go with the first one. Swap values is pretty handy when you actually need to swap two values. Here you aren't really using one of the values. From a memory or speed perspective I bet you can't measure the small amount of difference (if any) that is taking place.
  6. Thank you for posting this. It's very helpful and informative. I was noticing icon font issues in LabVIEW 2020 Community Edition for Linux, so it doesn't look like NI has fixed (or knew about) the issue in LV 2020 for Linux either.
  7. I understand how to call a LabVIEW VI from Bamboo and pass in parameters but I have no idea how to return any pass/fail results back to Bamboo or if I even should. Any one have any suggestions?
  8. Personally I don't think of delegation as a pattern, just a natural consequence of encapsulation. In your example, you've included demonstrating polymorphism and delegation. If you want to focus only on delegation, I would probably make some adjustments: Two classes - "Duck" and "QuakingFunction". Duck class contains a QuakingFunction object. It has a 'constructor' or method to set the required object for that task (dependency injection). Duck class exposes the static "Quak" method. This method internally calls QuakingFunction.Quak() method of the object (your delegation). Note - if you make the QuakingFunction.Quak() method virtual, it lets you implement new child classes in the future that Quak differently (Strategy pattern). You inject the one you want at the time. You don't need the derived Duck classes at all in order to demonstrate delegation. The Duck.Quak() method can of course be called with the child class objects so that they too can quack .. like a duck (Inheritance).
  9. Last week
  10. Hi, I made a small example for delegation pattern. hope this is the right way to teach the delegation pattern. suggestions & corrections are welcomed...... duck delegate patern.rar
  11. So I managed to find the underlying issue and at least one solution to it - sharing the information here. The Icon editor enumerates the font list in linux with command 'fc-list'. With OpenSUSE 43.2 / LV 2016 combo the fontlist looks like this: The listed fonts are essentially a list of the font files with full paths, and that does not work well with the font tool LV uses. If this list looks similar to yours and the fonts are not looking pretty, I have a solution for you - read on. To fix this a command 'fc-list : family' should be used instead, to come up with a list like this: There are two solutions (and I'm sure there are more) - you can decide which one to pursue depending on your expertise. As the Icon Editor in LV2016 (starting with LV2011 I think) is in packed library for execution optimizing purposes, the Icon Editor code can't directly be altered to fix this. One can come up with a solution where the command 'fc-list' is overridden in linux so it will always use the (proper for LabVIEW) format 'fc-list : family'. This may have some unwanted side effects if other programs use the command in similar fashion, so this may not be the best solution. It would be pretty easy to use for assessing whether this could be your problem also. There are multiple trivial ways of implementing this, so I won't be giving an exact solution - here is a list of them: https://lmgtfy.app/?q=override+command+in+linux Darren Nattinger has provided the source code for Enhanced Icon editor in https://forums.ni.com/t5/Enhanced-Icon-Editor/Icon-Editor-Source-Files-for-LabVIEW-2016/m-p/3538808 - You can replace the packed library LabVIEW uses as editor with this source. There are easy 3 step instructions on the site - even I managed to do that. Please give kudos to Darren should you go this way. When you have the shipped Icon Editor replaced with the source, you can directly edit the file in /usr/local/natinst/LabVIEW-2016/resource/plugins/NIIconEditor/Miscellaneous/Font/Linux.vi so it uses the correct form, like this:
  12. Can you rank these three options? Specifically, I'm looking at what are the best options for avoiding mem copies of the string. Is the "swap value" primitive buying me anything?
  13. Another VI I thought someone reading this forum thread might find helpful. This one calls the one I posted previously as a subVI. "Make Control Glow.vi" draws a fading rectangle behind the specified control. Save it and its subVI ("Offset Glow Rect.vi") to the same subdirectory. For example, here's a glow on a system OK button. Color and border thickness are parameterized. Saved in LV2020. Make Control Glow.vi Offset Glow Rect.vi
  14. Yup, thanks for reporting. I saw the post but didn't look close enough at it.
  15. Hi LogMAN, thank you for the reply, it does indeed. However attempting to fix the issue with the instructions on that page offered no help for me with this issue. Specifically, even if there at one point were useful information, the links are not working anymore. I created another issue, so if there are any good solutions, the rest of the conversation can be continued here: https://lavag.org/topic/22205-font-issue-in-icon-editor/
  16. Your issue could be related to these topics (I assume "glaring front issue" means blurry): Texts in Icon Editor Get Blurry - National Instruments
  17. Referring to comments in here, I'm looking for a solution to the font issue in the Icon Editor. Selecting different fonts does not seem to change the font in the Icon Editor, specifically in the Icon Text tab input. I've had no luck playing with the Tools=>Options=>Environment=>Linux=>Use pixel-based font sizes, it seems like whatever I select, the font won't change at all. This leads me to believe the issue is with the icon editor and the way it loads the fonts in Linux. I know that it works in Windows, but in Linux it seems as if the Icon Editor always defaults to a same font. It does change, but for the worse if I select any of the builtin(?) fonts, LabVIEW Application / LabVIEW Dialog / LabVIEW System - in the Icon Editor Properties. I've tried most of everything I found from internet plus then some. I've rebuilt the font cache, copied the small fonts .ttf file from windows etc. so I'm thinking the easy fixes are already exhausted. Environment: LabVIEW 2016 on OpenSUSE Leap 42.3. So, looking for help in LAVA forums for this.
  18. This issue arose from the fact that I could not easily figure out a way to fix the glaring font issue in the icon editor, so to go around that I decided to create the letters I use in icons as glyphs instead. These might come in handy for other users as well so I'm sharing them here. Letters.zip There are better solutions for this I'm sure, thus this is only a stop gap hack.
  19. The best way is to report posts via the three dots in the upper right corner. That way moderators get notified.
  20. It's a pretty common spam technique, designed to sneak spam links into innocent-sounding posts. A moderator should clean out the spam.
  21. I managed to figure out the solution to this, so will share it here. In this article there was a mention of the setting, that defines where LabVIEW will look for the icons and glyphs. In Options/Paths the default value for the "Default Data Directory" path is /root/natinst/LabVIEW Data. => this then is the correct place for also the user defined glyphs, and I can verify that this works. After any change, do delete the Glyphs.<LVversion>.bin file in the same folder. This will force the LV to recreate the glyph cache, no need to restart LabVEW.
  22. Something fishy is going on here though. Is it me, or some spammer is managing to inject spam links in jrpowell quotes? Hmm, last four messages, single posters to a dead thread.
  23. To create user defined glyphs in the icon editor the Windows documentation states the correct place for the .png files is under the \LabVIEW Data\Glyphs\. Using 32-bit LabVIEW 2016 with OpenSuse Leap 42.3 the location should IMHO be ~/natinst/LabVIEW Data/Glyphs but this does not seem to work. I have tested that the glyph files can be loaded from wherever, so the file format is correct, but I would like LabVIEW to load these to the Glyphs menu in Icon editor. Refresh does not help. I'm thinking the glyph files are probably in incorrect folder. Has anyone managed to accomplish this, and could you give me a hand with configuring this?
  24. I didn't use it at all, even though most of my lab instruments are from Keysight.
  25. A 9039 may be of interest, but I don鈥檛 think the 9038. Thank you for checking. Still looking for 9047s.
  26. I typically use a second lvproj file, not for installers, but for the unit testing. The benefit is that I can segregate the dependency on the unit test framework (i.e. Caraya) from the source file that runs the build specs. Although, I don't know if that's super useful if you use a CI server to run both UTs and perform your builds...
  1. Load more activity
  • Create New...

Important Information

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