Jeffrey Habets

Hi,

The latest version (2010) of TestStand supports LV classes.. See also here: http://zone.ni.com/devzone/cda/tut/p/id/8848#toc3

The knowledgebase article you pointed to refers to an older TestStand version.

Allow us to force a reload of system locale settings

GOOP3 -> GOOP4 conversion is available in version 4.1, which I think is about to be released...

A single plot can not have multiple colors for different datapoints.

I think the easiest way to achieve this is to use two plots, one colored for data within the limits and one for data outside of the limits.

You will have to split your data up into two sets of equal length where you put NaN's in the elements you don't want displayed for a certain plot.

Images say more than a thousand words, so here's an example:

Btw. I think this topic is in the wrong forum, because it has nothing to do with scripting. Maybe one of the mods can move it?

LVOOP is new ground for me but I am starting to understand it much better thanks to these forums. So the only thing you need the message name for is so that you can wire it into a case selector right?

This has me thinking of an idea for the idea exchange. What if you could wire the object right into the case selector? It would behave like a typedef with the ability to add a case for every value (child) and break if there is no default and you don't have a case for every value.

Would anyone out there kudo an idea like that?

I'd definitely kudo that.. Add to the idea that the internal connection of the case-selector returns the specific-child class wire, so we don't have to do the cast anymore and we're complete.

Congratulations Omar and Merry Christmas!

Thanks guys, for verifying this.. Workarounds seem to work.

Any of you reported this to NI already?

Hi,

I'm gearing up to start development of our next two projects in LV2010 and noticed I'm unable to create properties and methods on XControls (either new ones or existing ones from earlier LV versions). I checked this on LV2010f2 32bit version as well as on LV2010 64bit version. See what happens in the vid linked below.

http://screencast.com/t/IOBg5ir4y

Same happens for method creation.. LV then creates a 'normal' VI instead of a method VI.

I was unable to find any info or reports on this here and on the dark side..Maybe, I'm missing something here, but if this is a bug, it's quite a showstopper for me. We'll have to stay on 2009 then.

Anyone else noticed this weird behaviour?

On my PC, when update speed is less than 50, memory increase. When it's more than 50, memory decrease and stay to the same amount.

There is something strange, if it was a "simple" memory leak the memory shouldn't decrease.

I think we need the lights of NI engineers.

Seems something is being Queued up there..

I'd say no..

My basic motto is: don't close what you didn't explicitly open.

The owning VI is still in memory, even after this call to the facade finishes, so a close will probably be a nop.

The one responsible for actually closing the ref (and thus cleaning up the VI object) is it's initial creator, a specific application instance.

The one thing that's left is the memory location that holds the refnum (pointer to the VI object) and that should be taken care of by the garbage collector as it is for all wires that at some point on the diagram stop and their value is of nu use anymore.

100% sure? I sure hope to be close, otherwise I'm going to have to file a bug report.

I guess the class icons get stripped when building an exe. They seem an unneeded resource at runtime.

Nice menubar btw. :-)

Want your SCC actions and add-on tools accessible via shortcuts in #LabVIEW ? Vote for this idea:

Let's have the ability to assign shortcut keys to ALL items in the LV menus

and/or this similar idea

Allow Keyboard Shortcuts for User Items in Tools Menu

Another option you could use (that doesnt need opening references etc) is to have the parent class VI return an error code (ie a "method not implemented" error) - that way, any override VIs will execute normally, but any classes that do not provide this functionality will error in a known way that you can catch and handle appropriately, etc.

That's more or less what I did to have an indication of forgotten-to-implement overrides before we had the must-override option for methods. But for the use-case I have here this is not an option, since I'd have to call the method. In my use-case I need to know if it exists without actually calling it.

The open/close ref does the trick here and for my use-case it's not to much overhead.

Seems the one who was missing something was me..

But no worries I've got a vacation coming up.. All should be well after that.

Thanks!

Hi,

I'll illustrate my question with my use-case. While implementing a variant of the command pattern I want to have commands that are optionally undoable.

For this the command will have an Execute method that is a must-override and an Undo method that can optionally be overriden.

What I'm looking for is a way to check at runtime (from the parent) if the child on the wire has implemented the Undo method, without calling it ofcourse.

Just curious if this is possible.

I know my ways to work around this, e.g. have attribute Undoable in baseclass, or introduce a CommandUndoable class (which is a child of Command) to be inherited from by undoable commands.

I stayed at the Radisson the last couple of times. This year NIWeek rate was $115,-. Only a 5-10 min walk from the convention centre.

They have Starbucks and T.G.I. Fridays.. Wifi in the room is $9,95/day, but if you ask for a code to use the free wifi in the lobby, this just might work in your room too. :-)

I probably missed your first post.

For what it's still worth.. That's how I usually do it too..

Another way would be to have just one constructor and tell it how to construct using e.g. an enum parameter (the Report Generation VI's class does this), but this requires you to have all possible parameters for all construction actions. I wouldn't recommend that.

This sounds like the job for your basic list-based observer pattern:

Each interested subscriber (observer) registers itself with the subject. When the subject needs to 'send the event' to its subscribers, it calls the Notify method which in turn calls the Update method on all registered subscribers.

I'm in the Radisson from Sat-Fri and will attend most (if not all ) events..

So some developers jumped ship from Endevo/Simbio to start AddQ, took the GDS sourcecode, repackaged it as their own and added a few bells and whistles to it, without your permission. The crazy thing is that if anyone wants to add OOP farmeworks into GDS all you have to do is contribute, and if you have ideas or sugestions on new features to GDS then Mikael would love to hear it.

I'll keep using GDS, it Rocks, and I'm looking foward to contributing more.

Amen to that.. Go GDS!

Reading the @eyesonvis last blog entry about splitterbars reminded me off two Ideas about wanting to be able to use them also in tab pages.

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/quot-Fit-to-pane-quot-for-tabpages-Tabpages-handled-as-panes/idi-p/1098417

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Tab-Controls-with-Splitter-Bars/idi-p/990693

Basically both ideas say: tab-pages should be panes!

I.m.h.o I don't see enough LAVA in the kudos list, so I though I'd just give it a plug here.

I've got my ticket in too (Euhh, I lost money through paypal, I guess that counts as a ticket in. )

Transportion would be nice indeed, it seems like quite a walk.

I like the Idea! This is something that has always been on my mind to do internally, but time never permits. Making it a group effort is a good idea.

I'll be happy to throw in my where-ever I can, as time permits.

I'll be at NIWeek this year btw.

This is pre-LV2009 behaviour.. You probably should check this setting in your build specification:

It should be unchecked.

You are correct that now only new topics are posted to the RSS. I'm trying this for a while. How do you like it? Isn't it better than getting the entire thread posted every time? No more RSS bombs.

I like it very much.. Now the RSS feed is usable again in Firefox!