Cat

I've been staff for awhile now, and this has just started. It's kinda annoying because I'm used to the big dark button above my post being "Add Reply" and now it's something else. Everyone remember this when you're changing your GUI designs... Oh well, in the scheme of things this is pretty trivial!

This sounds like when I can't trust my daughter not to eat a whole bag of M&Ms so I have to just give her a few at a time. In other words, I don't believe she is mature enough, or smart enough to make the right decisions, so I limit her options. When you're talking about a 14 year old, that's reasonable. When you're talking about all adults over the age of 18 in the USofA, it sounds a bit patronizing. All of this being said, the majority of voters are for term limits (or have been in the past). "We The People" have voted to limit ourselves. And if/when "We" decide "We" are mature enough to handle it, "We" can vote to remove term limits. That's what democracy is all about. Of course this isn't going to happen any time soon, since most of us as individuals think "We The People" are just an unruly mob who can't be trusted to vote the "Right Way" (as I can't trust my daughter in the M&M example). I personally think that term limits should be abolished whenever MY party of choice is in power and reinstated otherwise.

A couple things: 1) Why, when I create/reply to a post, is there now a line above it saying "Topic Poll" and a button saying "Manage Topic Poll"? And the "Post New Topic"/"Add Reply" and "Preview" buttons are missing from where they have been conveniently placed above the post. 2) My "View Unread Content" is often not updating after I read a post. This may be my browser (IE7), but it's worked fine in the past.

Gee. Thanks... I'm sure I'll need it. Up one side and down the other. I'm very anal-retentive about backing up; it's the only way I've survived so far.

I know! #4 has been my real excuse. I guess I should wander around this subforum and see what might work well for a single developer...

My apps are more interwined than I remembered, so just moving directories is taking longer than I expected. I haven't started moving common code to the Shared directory yet. I do not have a "scc system". That's part of the problem, eh? It's just me writing code, so it really hasn't been an issue in the past.

I've got 8.6.1 (I'll probably get permission to upgrade to those 2009 disks sometime in 2011). I started the process of reorganizing yesterday, and so far it's been going okay. Of course I copied EVERYTHING off to an external drive first. Which was good, since I did end up having to pull a few files off of it when old versions snuck into the new directories. Today I'll take a deep breath and start moving stuff to the Shared directory. And then I get to figure out what to do with my executables tree. But that will be for another thread. I've hijacked this one long enough.

This is pretty much the road I've started down. I've got a Shared directory, but haven't had the nerve to move much in there due to the linking issue. So that takes care of Big Project and all it's various tools applications. But it's still internal to the Big Project tree. I guess I have to be really gutsy and put it external to any project. While maintaining the links to about 3000 vis in 20 different apps... Thanks! This has been really helpful.

Oh. Crud. Why didn't you mention that before?!?

So, I ranted yet again to my boss about this topic and (finally!) should have VIPM on order momentarily.

Hmm. Interesting solution. I could apply that to my generic reuse code... I keep generic reuse code in my user.lib (which I guess is passe now, too). I have a few hundred functions I've written over the years in there (many of which were eventually supplanted by OpenG functions ). An example of my problem is this: I have the Big Project (BP) that stores data is certain file formats. A New Project (NP) comes along and wants to be able to use the tools that I've written for BP to analyze its data, so it needs to have its data stored in the BP file format. Not wanting to rewrite code for the NP, I reuse BP-specific functions/typedefs/etc. Or, I come up with a better way to do something in NP and want to use it in BP. Or when I started using queues instead of GVs to get data from my buffer to my analyzer in BP and it broke various NPs. So how do I organize this? Does code that gets used over and over in BP, and one time in NP, get moved to a "reuse" directory? Am I just being old-fashioned in thinking of things as going in "directories" in the first place? I've spent some time on the NI website reading documents about the Project Paradigm, but I have not found anything that really answers how to best utilize Projects when you've got multiple large overlapping applications. That, BTW, all have to be turned into executables at some point, so I really don't have the option to just ignore Projects and manage it all how I used to. Ehh. Sorry about the rant. This is just something that I feel is very important to get under control before I do some damage that it takes some real time and effort to recover from.

I need a tool that slaps me severely if I try to alter code I've used in some other application. I used to do just fine keeping track of all that, and then LabVIEW switched me to the Project Paradigm. I've had more than one really big boo-boo since then. Or maybe it's just that I've just finally hit the critical threshold of brain cell loss from too much .

Maybe it's just me, but wouldn't it be just as easy to right-click on the case structure and select "Add Case After" or "Duplicate Case"?? I must be missing something here...

Program usage I get from eyeballing how much memory just running the program takes up in Task Manager. Then I throw in a couple hundred MB because LV has a bad habit of grabbing memory and not letting it go (even if you use the "anxious deallocation" function). This all should be a fairly constant value, depending on your program. For my program that's about 750MB. Like I said, this is Bad Programming and not how I would like to be doing it if there's a better solution out there. I have a set of Windows API llbs that I've had so long that I don't remember where they came from. Available Physical Memory is in winsys.llb\System Information.vi Windows API.zip

Welcome to my world... I love LabVIEW dearly and will defend it as a great all-around programming language, except in one area -- memory management. And that's a killer for those of us who have to manipulate/display large data files. My (rather vague) understanding of the problem is that LV generally wants to grab *contiguous* memory. So while you may have plenty of free memory, if it's broken up, LV can't necessarily use it. (I'm sure if I'm wrong someone more knowledgable will jump in here...) My workaround for this is to read the available physical memory, subtract off about 750MB for what I label "LV inefficiencies" and divide the remainder by a "memory loss" value. Trial and error with this has left me with a value of 4 for memory loss. (Available memory - program usage) / memory loss = #bytes of hopefully contiguous memory out there somewhere This is a cludge and isn't really determining what I need to know (available contiguous memory) and I hate it. But it works, most of the time. If anyone else has a better way to do this, I would love to hear it.

I realize that the other forum members can stand up for themselves, but he *did* post this in the "Help me with this LabVIEW code I want to write" section of the forum, and not the "I've got a small job for a LabVIEW programmer" section. And then proceeded to accept free suggestions. Or rather proceeded to respond negatively to free suggestions. Definitely sending mixed messages. I agree, he and his chosen contractor should take this offline. Tho, I must admit, I definitely applaud Mark Balla's attempts to supplement the LAVA beer fund.

Absolutely. I've printed it out and am going to save it as inspiration for next time we're looking to hire someone.

That's the answer, then.

Is there such thing as "virtual arm-wrestling"?

I want this job!! If only it didn't mean leaving behind my daughter, my cats, and my SO. Of course, my daughter is in China, my SO is under the deep blue sea, and one of my cats presented me with a fur ball this morning. If I just snuck off, no one would notice for quite some time...

If you don't get any answers here, try over at Info-LabVIEW . There are (or atleast used to be) quite a few LV/Mac experts there.

You've stepped into a religious war. I think that (as usual) AQ has the best response to this issue. As he stated in the thread you were pointed to: "Sequence structures are to LabVIEW what sentence fragments are to English. Both are so problematic that we have to teach newbies "never use these" and then later we can say, "ok, now you can use them because you now understand how they work with relation to the rest of the grammer." Sequence structures have value, but new users to LV tend to over use them gratuitously and thus end up killing the performance of their code. Similar with sentence fragments. ;-) " Bottom line, only use a sequence structure if it's the *best* way to get the job done. Not just when it's the easiest way. A lot of beginning LV programmers don't have enough experience to know the difference. (Hmm, I think I used a sentence fragment in the above paragraph. )

This thread is cracking me up. There's a "LAVA fund"??

Turning our lovely logo on its side makes it look like either a tube of toothpaste or a dead fish.

Well, I have been playing with using tabs for the 3 main types of plots. The resizing of 1-4 plots on one page seems to work fine. Plus it's a nice fit programmatically. If I can't get the visible/invisible thing to work with 19 plots on 3 pages, I'll take a look at putting them all on their own page. Thanks for the idea! Here's my little nugget I've learned about resizing: It works best if I only do it in either the horizontal or the vertical direction at one time. If I use the corner and do both at the same time, the FP objects get very misaligned very quickly. The other part of this challenge is that the Users also want another FP control (multicolumn listbox) to appear either to the side of the plots or below them. I've been thinking having some sort of floating window might be the best bet for that. Your approach looks very interesting. Thanks!