Sparkette
-
Posts
402 -
Joined
-
Last visited
-
Days Won
30
Content Type
Profiles
Forums
Downloads
Gallery
Everything posted by Sparkette
-
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?
-
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.
-
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
-
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
-
building a display calculator
Sparkette replied to qwerty3321's topic in Application Design & Architecture
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. -
Does anyone have any idea what DCO stands for? It's in the same context as DDO, which I know means Data Display Object.
-
-
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?
-
I believe, DCO stands for Data Controller Object and DDO should be Data Display Object. You might see DCOs and DDOs already with the help of Heap Peek. I didn't study DDOs much (it's either a control or an indicator), but a DCO controls how and which data is passed through a single terminal (on BD) or control/indicator (on FP). You may find any SubVI's/node's terminal w/ Heap Peek and in its properties you should find an address of DCO assigned to it. The same is doable with controls and indicators on Front Panel. On BD DCOs are called Parameters or EFN Parameters (for CLFNs) or somehow else. On FP they're called FrontPanelDataControllers. It's easy to find them using "F" button of Heap Peek. There are two internal functions in LabVIEW, which read and write from/to a DCO's (Transfer/Execution/Operate) data buffer: ReadDCOTransferData and WriteDCOTransferData. These funcs are used in Get Control Values By Index and Set Control Values By Index behind the scenes. It's even possible to call these funcs from BD directly to mimic the foresaid instruments behaviour.
-
-
Bumping this thread because I've posted a new version; see the OP.
-
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. 😛
-
Bob L? I think he prefers to go by RobertLewis.
-
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
-
- 7
-
-
-
You know it be true. How about Pr0ject411?
-
And do I really want to know? 1gn0rance1sbl1ss, after all. 😜
-
How to add a folder to build spec using VI scripting
Sparkette replied to Gribo's topic in VI Scripting
So would that be T0rchy$, or...? 😁 -
How to add a folder to build spec using VI scripting
Sparkette replied to Gribo's topic in VI Scripting
Taco deli? 😉 -
Did you post this before you started working for NI?
Seems kind of funny to see an NI employee asking the community for help with XNodes of all things 😄
-
Started working at NI in 2014 so this was after that. At the time, I was an Applications Engineer and this was a side project so I didn't really want to bother any of our developers.
I ask enough of our R&D team for work problems so I'll bug LAVA or our local user group with problems I've run into from more personal projects.
-
Ah ok. Just thought it was funny
-
-
How to add a folder to build spec using VI scripting
Sparkette replied to Gribo's topic in VI Scripting
I was trying to script something involving a build specification just yesterday. I'm pretty sure "Targets" refers to things like "My Computer", not build specifications. You can get a reference to the Build Specifications folder through the "My Computer" property of the project, IIRC. And from there you can get the Owned Items[] property, find the one you need, and use "To More Specific Class" to make it a Build Specification refnum. However, strangely, I haven't found any methods/properties that do anything specific to build specifications. Maybe I'm looking in the wrong place though. -
Wait, what about the person who already had the name Bryan?
-
Does this mean its deprecated status will be removed? Also Paul, just wondering, how did you find that property?
-
And yet all they're using is plain black lines connecting the nodes. In this thread? Really?
-
I never thought to add a license to it; as you probably guessed it's not really something that readily crosses my mind. 😛 I don't really care what you do with it; I guess I'll put it under the MIT license or something in the next revision.
-
Well that last one depends on your personal ethics on the matter, but I guess you did say "potentially" so you aren't wrong. That's a bit too off-topic to discuss much further here though; I was just making a joke
-
I could try and see how well that works. Also, NI got back to me; they said they were able to confirm the issue I mentioned and they've filed an internal bug report. (Btw hooovahh, the second quote in your signature is not entirely accurate 😛)
-
Need help creating Candy Crush type of game.
Sparkette replied to Rezar Nashoua's topic in LabVIEW General
Neat idea using LabVIEW for game programming
