JackDunaway

I hadn't tried that. Unfortunately, they all stay black at runtime. (Classic, Modern & System)...

You know what... you're right, I can't get it to work either with 2009 or 2010. Even with the chameleon color (d16777271). Perhaps this worked in the LV8 era, or more likely, just some strange deja vu of which I happen to remember procedural details.

Best I can offer after bum advice is crelf's product suggestion for 0px splitters.

One that will not show a line between two panes that have an image loaded in the background?

Do you get your desired effect by setting the splitter colors (FG and BG) to transparent? This must be done via property node, since the recolor tool fails to work. If I recall correctly, the splitter looks black in edit mode and actually turns transparent in run mode.

You probably mean 2011?

That date is probably December 9, 2010, not Sept 12, 2011.

Easy question that I've not been able to figure out over the years. Say I have an NI CAR number for an issue, what do I do with it?

I don't know if you've seen the new Idea about a LabVIEW Issue Tracker to facilitate this very issue; perhaps it's worth checking out.

The best way I know to check the status of a CAR is to email or call someone who can access NI's internal bug database (e.g., an NI employee). They will sometimes be able to help, especially if the information is not "classified". Word on the street is Alliance partners also have (partial?) access to this database.

I don't think the use of 'opportunity cost' is fair here

I think it's fair. NI has limited resources, and assuming they're dutifully employed, the developers working on Distribute Wires are not working on something better.

Is there an idea you wanted pushed through that is comparable in the (perceived, at least) level of complexity of wire alignment?

Not specifically.

hmmm, how did the Save-->Undo option make it in with only 64 kudos and 3 comments...

I'll be the first to admit: NumVotes is often not proportional to IdeaPowerOrUsefulness. Distributed Wires=356 versus Undo after Save=67 is a great example. I'm excited Distribute Wires is making it into the 2011 release, don't get me wrong, but it comes with the opportunity cost of any one of dozens of better Ideas.

This is a cross-post from the Dark Side - I've searched for a while without finding any definitive discussion on this topic, so please post your thoughts over there.

I have a discussion question about best practices pertaining to typedefs and class design.

Background: In terms of object composition and nested data structures, it appears that Typedefs have been deprecated by classes. I have noticed that typedef'd data members of the Private Class Data Cluster are excluded from the auto-tracked Mutation History (more about Mutation History) of the class. This leads to problems versioning persistent data, and also I have seen IDE mismatches on "Bundle/Unbundle by Name" when accessing class private data after renaming typedef'd data members.

Thus raises the question:

Is it typically a bad idea have typedefs as data members in class private data?

Hey Jack, Welcome to LAVA!

PJM

Thanks, Philippe! After lurking for three years, I finally decide to chime in for the first time with a buzzkill.

I respectfully question whether an Add-Ons Idea Exchange should branch from the LabVIEW Idea Exchange. A member of the team in charge of this division seems to agree. Feel free to post comments on that thread.