Leaderboard

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.

In response to this topic, here is some scripting code I just wrote for the LVOOP Simple Accessor Hook. It formats the Data Member VI(s) to my style as follows: - Bold Control inputs (which are required by default in 2009 which is great) - I like to match the FP to the VIs help window. - Aligns all labels on the BD: Controls to the left, Indicators to the right using one of Darren's Quick Drop plugins. - Realigns controls closer to the case structure to neaten it up. I have been meaning to do this for a while. Simple bit of code, but saves me the redundancy of repeating doing it for each member VI! Maybe someone else can get some use out of it or use it as an example. Also attached is my CLSUIP_LocalizedStrings VI. Anyone have any other code for LVOOP plugins that they would wish to share? Cheers JG Custom User Scripting For New Simple Accessor VI.vi [LabVIEW 2009] CLSUIP_LocalizedStrings.vi [LabVIEW 2009]