Leaderboard

Same name, both places. Though like many others I don't post to or read NI forums too much. Too much traffic.

The above "release the following year" is how you end up without the SSP for the bug fixes. I think this gets away from the point, though. If I release code to a customer, the bug fixes are priced in. If they come back to me in two years and say "Hey, we found a bug that matters to us", I'm going to fix it for them, gratis (and have done so). I consider it to be what professionals do. In the past, NI has released features and bug fixes commingled. Not so much, this time around, but the SSP rules haven't changed. Personally, I would prefer to buy a single version of LV and get all bug fixes for that version free forever, rather than getting the cheap upgrade the next year. Joe Z.

The voluntary Beta Program can be improved in a couple of simple ways. 1) Change the EULA that comes with the Beta to back us up if the Beta testing goes sour on us. If I try out a Beta and it steps on my machine (renders the official releases inoperative) then one of the tools I use to make a living (my mahcine) is jeopardized and according to the EULA "Tough luck Ben!". This translates as "Wait until you retire." for me so I am out of Beta test cycle on those grounds alone. 2) Use the Bug Report records to find the people that have found and reported the most bugs and offer them a resonable rate to use BETA code (with full support if something goes wrong after codding for a moth or so) in there every day work. Since neither of the two items above apply to the BETA, I wait for the "dot-zero" version where I do have support and my boss does pay me to use it and will not fire me if I do. As I find the bugs I report them. So until there is a serious change in the policies this situation will not change. Now for what may be a retorical or just a philosophical Q What other industry can expect serious product testing by people that are volunteers? Just my 2 cents, Ben

QUOTE (turbophil @ Feb 18 2009, 10:06 AM) I think you are on the right track; using CD is the way to go. Presumably you know you can have some symbols which are for the whole project, and other symbols that are per-target (it depends where you right-click). You may be able to do what you need by putting the symbol only in the RT target, so that whenever you run on the local machine, it will use a different conditional symbol case. If you need more complex behavior than that, I wrote a VI to change the symbols programmatically, which may help you switch back and forth. I was going to put this in the LAVA code repository, but I can't deal with the bureaucracy today, so here it is, attached (labview 8.6.1). Hopefully later I can submit it the right way.