Jump to content

LV-Vikingr

Members
  • Posts

    9
  • Joined

  • Last visited

    Never

LV-Vikingr's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hello everyone. I am looking for work developing LabVIEW applications. I have no idea where to begin looking, the classical sources are turning up nothing. Any pointers in this regard would be much appreciated. Thank you, LV-Vikingr
  2. I would save the selected path to the Windows registry every time the user wants to choose a different selection. When the program loads, look in the registry for the path.
  3. Hello Hoeloeloe, An increase in CPU usage does not necessarily mean that the program is running faster. Most likely, right clicking on a control is causing other events to occur which require more CPU power. Also, you might want to clock the time it takes for one iteration of the loop to complete. Have that display somewhere on the screen and watch the speed (in ms) while it runs and while you right click on a control. I'm sure that the speed will decrease or stay the same. It might also help to see a sample of your code...
  4. Although I don't spend too much time wondering what other programmers think of me or the language I choose for developing in, I have encountered similar circumstances. People who work in C/C++ tend to have that disposition, Eugen. They are equally, if not more, critical of VB programmers. Their assertions are based on the idea that C/C++ requires you to build most aspects of your program from the 'ground up'. However, ask them what headers they use? Did they make the header or are they using something someone else did? Also, one of the great strengths of LabVIEW is that it is easy to make cross-platform applications. How often do they even attempt that in C/C++? When they do how much extra work is that? There are definitely advantages to using C/C++ over LabVIEW. For example, the ability to make Win API calls that return STRUCT data types. LabVIEW will not always work with these data types (especially STRUCT data types that contain other STRUCT data types). However, the ease of development and handy tools to make development swift and reliable far exceed, in my opinion, other shortcomings.
  5. Hello everyone! I am adding new print forms directly into HKLM\System\CurrentControlSet\Control\Print\Forms. However, the new form is not visible in the Print Server Properties until after restart. The form is also not usable by any of the printers until after restart. Is it possible to add user forms and have them be usable without a restart? Creating a new form from the Print Server Properties display does not require a restart so I have to believe there is a way... Any insight would help greatly! LV-Vikingr :beer:
  6. Unfortunately, I need to acquire the image from the Windows clipboard. That method acquires images from the LabVIEW clipboard. The reason this is important is that I am acquiring an image the user acquired using Print Screen or Alt + Print Screen. My apologies, it does acquire images from the windows clipboard. Thank you for finding this, but could you tell me how you got it? I can't seem to replicate the application clipboard getimage method, I can only get to read and write string methods for the clipboard. Thanks again!
  7. Hello everyone, I have been trying to get an image from the windows clipboard for some time now and have had no success. The problem is that the getclipboard data function in the user32.dll does not seem to be usable with the Call Library Function Node. Although I know that it would be easy enough to create some other code to translate data types between the function and the program, I would like to find a more eloquent way of handling this (through LabVIEW exclusively). I have no sample code for this problem as it is, as yet, unsolved for me. I do wonder if there is a way to use functions in ntdll.dll that may accomplish this task for me better. Thank you! :beer:
  8. It is indeed Thors hammer. My programming experience has been mostly spent doing machine automation and data acquisition. However, I try to push my knowledge in all ways and am always interested in any programming challenge. My experience with LabVIEW has been dealing with GPIB communication, datalogging, report generation, and a little IMAQ. I have many questions to ask and look forward to helping others if I can. :beer: Nice to meet you both yen and Mike Ashe!
  9. Hello everyone! I have been programming with LabVIEW for about 1.5 years. I also have a year of experience working with VB 6. I'm looking forward to getting to know everyone and learn as much as possible. Thank you and see you around, LV-Vikingr :beer:
×
×
  • Create New...

Important Information

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