Jump to content

asbo

Members
  • Posts

    1,256
  • Joined

  • Last visited

  • Days Won

    29

Everything posted by asbo

  1. Man, that is a massive palette. Why does the it have its own version of the variant constant? If you eliminated that, you could condense it to a more reasonable 5x5.
  2. Conversely, you can build a VIPC for your project using one of the pay-to-play versions of VIPM. It lets you scan a project and make a list of all of the necessary packages, with the option to actually include them in the VIPC.
  3. Can you post the VI or snippet that's generating and saving the spectrogram?
  4. It sounds like your stumbling block still has primarily to do with SNMP. Personally, I don't know anything about generating a MIB, so I can't help. Unless someone else swoops in with some expertise, you may be out of luck.
  5. If you're having trouble using the VI, it probably means you don't know enough about SNMP. There was a thread a while back where someone contribute a set of VIs for working with SNMP. I've used it before in a rudimentary sense to manage a router, but that's it. You should study up on SNMP and see if the VI makes more sense after that.
  6. candidus makes a very good point, and on top of that, encourage developers to be vigilant about locking VIs their modifying and subsequently locking VIs which may be affected by those changes. In multi-developer projects, it's pretty normal that we don't do a re-save for all recompiled VIs for lengths at a time. Probably should, since this adds to everyone's load time when the disk version has to be recompiled every time, but so long as there's no manual changes to the VI, I don't go out of my way to make sure all the interdependent stuff gets resaved. Especially in large projects, it can be a tedious effort to do so.
  7. Yeah, Goggle translate is a life saver. The Windows Update makes makes sense, but they almost always include the 'wu' abbreviation for those services. OTOH, like Saverio says, it looks like it's related to an AV solution from Symantec. This would probably also be something you might want to stop during a long test.
  8. asbo

    Wat.

    https://www.destroyallsoftware.com/talks/wat
  9. In addition to what Tim_S said, another caveat of 64-bit LabVIEW is that most toolkits having not been ported to x64 yet. If you think you're going to use toolkits and are sure you need 64-bit LV, make sure the toolkit you need to 64-bit compatible before taking the plunge.
  10. Re-saved in LV2009. OpenG LVOOP Suggestions.LV2009.zip
  11. And you begin to get pulled right back in ...
  12. Keep in mind that this method will be slow for large objects because it uses Flatten to String. In any case, I would think that parsing the string would be easier than trying to walk the byte array, but if it works, it works.
  13. I thought this might be the case. I know the IDE will still try to load VIs in a disable structure. I'm not sure how smart the compiler tries to get with controls, but you could try wiring a control to the selector instead, then hiding the control on the FP. The compiler might be smart enough to realize the control doesn't/can't ever get used, though. This approach starts to feel more kludgy to me, though.
  14. The largest problem with using SVN is if you commit partially-working code (and you should, versioning isn't just for major, functional versions of code) and someone pulls the partially-working code thinking that it's an update. I suppose you could make the trunk your release version and then always branch to do development.
  15. I wonder if placing those VIs in a disable structure or opposing case of a constant-wired case structure would trick the deployment into including them as well? It would feel a little less kludgy to me and you'd probably see an improvement in start-up time.
  16. I don't understand why you can't wrap the ActiveX component. Obviously you got it to behave as desired in your VB6 code, so just crank that code out as a stand-alone DLL and use the CLN to call that from LabVIEW. If you need to support multiple sessions/references/etc, you may have to do some fancy footwork in the VB code, but it should be relatively trivial.
  17. This is my preference as well. In general, I think the usefulness of the Format/Scan functions are overlooked when working across data types.
  18. I wonder if you're truly guaranteed concurrent transactions, e.g. simultaneous operations on the same field. I don't know if it's relevant for your use case, but it might be worth the peace of mind to check it out. Thanks for posting back with your solution.
  19. Did you look up what your ADO exceptions are referring to? ADO Error 0x80040E0E refers to an invalid bookmark. Despite having used ADO before, I have no idea what this is referring to. ADO Error 0x80020009 refers to an EOF, of sorts. It essentially means your query returned no results or you reached the end of your record set.
  20. Also, stable, which is pretty important for some sorting applications and particularly OP. You've missed guentermueller's link.
  21. I don't recognize any of the authors off-hand, but I would at least the first three topics good for general-purpose integration knowledge. The last two seem like they could be vague wrt a specific application, but on the balance it seems like there would be useful information. $100USD is rather steep for a casual read, though.
  22. Can you group the increment and decrement buttons in edit mode?
  23. Does the USB version of the autosampler actually connect as a USB device, or does it show up as a virtual COM port? The latter is what I would expect, and if that's the case then the point about "newer hardware" is moot. From the way you phrase option 2, I think this is the case. Is the autosampler well documented with regard to its protocol? If it is, writing a driver using VISA would be relatively trivial.
  24. Ah ha! I had a quick look for that event, came up empty, and went home confused. Thanks for the clarification.
  25. I thought you might be able to track the combo box's enter/leave events and use that to dictate logic in the tab control leave event, but the combo dropdown itself doesn't re-establish the bounds of the control and when you mouse to select something in the list, LabVIEW still registers the combo leave event. You could instead track mouse down events on the combo box, but that becomes messy when you need to figure out if the user clicked off the combo box somewhere (anywhere) else.
×
×
  • Create New...

Important Information

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