Jump to content
News about the LabVIEW Wiki! Read more... ×

flarn2006

Members
  • Content Count

    289
  • Joined

  • Last visited

  • Days Won

    19

flarn2006 last won the day on February 18

flarn2006 had the most liked content!

Community Reputation

78

1 Follower

About flarn2006

  • Rank
    Extremely Active
  • Birthday 07/28/1993

Profile Information

  • Location
    Northern Virginia

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2018
  • Since
    2005

Recent Profile Visitors

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

  1. flarn2006

    Hidden editable pixmap control

    Well if someone causes problems with it, after coming across it in the way I described that doesn't give any kind of warning, wouldn't NI be obligated to provide support?
  2. Playing around with XNodes—though come to think of it, you might be able to do this in a subVI as well, if you can access the diagram of the VI that's calling it. Call Chain maybe?

    ss_GqSztr.png

  3. flarn2006

    Hidden editable pixmap control

    I wonder, is this something NI would need to provide support for? Its label in the "style" list suggests no, but then if you create the control in the way I described, you wouldn't see that.
  4. Can anyone tell me what I just enabled?

    ss_hjQ3eT.png.d12d89113c9dfd0be1a226841f1d8c98.png

  5. 1. Place a control refnum 2. Right-click, Select VI Server Class, Generic, GObject, Control, Pixmap 3. Now it's a "Pixmap Refnum". Right-click again, Show Control 4. Drag the control out. Unfortunately, I first noticed this control in the VI Scripting style ring, where it was labeled as "warning: dangerous" or something like that. But the class isn't marked private, and it can be placed in the manner I described without any kind of warning, so maybe that warning is obsolete and it's been fixed? Then it would probably be in the palette, I guess, but I'm curious to hear what NI has to say. Maybe it's a bug that it can be placed that easily without generating any warnings. :p
  6. Lol I just noticed I'm the #1 most popular contributor for the week and the month. Not sure how special that really is as this isn't the most active forum, but it's still neat to see. Thanks I guess :)

  7. flarn2006

    building a display calculator

    For me, something being another person's homework assignment is something that would make me more likely to want to do it for them, not less. I enjoy keeping options open for people who want them, especially when others would rather close them off. If it is in fact a homework assignment though, don't get your hopes up, because it would still have to be something I'd want to put the time into doing anyway.
  8. Does anyone have any idea what DCO stands for? It's in the same context as DDO, which I know means Data Display Object.

    1. bbean
    2. flarn2006

      flarn2006

      Not sure. In this context it's part of LabVIEW's internal data structures for front panel/block diagram objects. Often DDO structures are contained within them. But a DCO is often used even when the data doesn't need to be displayed (in which case there's no DDO) such as for parameter terminals, For/While loop terminals, etc.

      Data Container Object maybe?

  9. flarn2006

    test

    Purged frequently, you say? 😛
  10. Bumping this thread because I've posted a new version; see the OP.
  11. Well, not supposed to know according to NI. But of course it's my brain, not theirs. Just mytwocents. Also, there's a reason MD5 has fallen out of favor, you know. 😛
  12. My latest project.

    ss_rLhnXy.png

  13. There are a bunch of objects in LabVIEW that aren't exposed in the default palettes, and are normally inaccessible except through scripting. I made a Quick Drop plugin that exposes all of these. Many of these are no longer supported, and others never were supported in the first place. Hidden ones are displayed with an "X" next to them to warn you: as I often say, be careful with these, and don't use them in any code you care about, as they can cause crashes, data corruption, and who knows what else! Download the LLB below and place it in your <LabVIEW install dir>\resource\dialog\QuickDrop\plugins folder. Then press Ctrl+Space, Ctrl+S to open this dialog. Select an item from the list and click OK, and there you go. There's some interesting/strange stuff in here! EDIT: Couple things I forgot to mention. The first time you open this (and whenever you rebuild the list) it uses two private properties on the app reference, to get the list of controls and indicators in the palette. Since this is just a property read, I'm sure the worst that could happen is a crash when you try to open the dialog, but I can't make any guarantees. Also there's some false positives for hidden items, mainly with front panel controls/indicators that come in different styles. Place by Style.llb
×

Important Information

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