jgcode

Hi Ton This is because of a feature change in the 2011.0.1 release. I have added feedback here if you are interested. Cheers -Jon

Thx - that would explain it

Negative. I was working with some code calling dll's, the only difference was this popped up on my 64-bit OS install but not my 32-bit OS install (both Win7 with 32-bit LabVIEW 2009).

I had never seen this Window before until the other day. It just popped up, couldn't do much with it - I am guessing it is an internal LabVIEW thing? Anyone seen it before?

Hi Wouter - I can see it in 2011 (as well as 2009 & 2010). Anyone else having issues?

This package will be available for download through VIPM in a few days. This release and covers a request for the LabPython package to be view-able under the new 4.x Top Level Menus, and to fix a dependency issue (related to this thread). This package was tested with Python 2.5 on both Windows 7 x86 and Windows XP x86. If any developers want to continue to work on the Labpython project or any other OpenG project just PM me. Kind regards Jonathon Green OpenG Manager

NI signs the ini files but you have to be a member of the LabVIEW Project Providers group. Currently this is not a public thing however, it seems NI might be heading in that direction in the future. I would contact NI if you are interested in joining the group (David_L helps run the group).

No, but you can install the tool under <wizard> or <project> yourself and get the same effect.

If I understand correctly what you are asking... There is no such thing as a .lvproj template but why not just create the above .lvproj file once then every time you want it, copy it manually, or write some simple tool to make a copy of it?

I would have been more impressed if you posted that as a SVG instead of a jpg

Nice mirror.

This artifact was deleted. See Comments in Sourceforge for details.

It may be worth pointing out that the latest packages (4.x) do not use (hence, require) the Dynamic Palette package (as the Custom Category feature in VIPM was used). However, if you are installing older packages <4.x then the Dynamic Palette package will need to be installed. Cheers -JG

I have used DSC quite a bit, and I did I quick search on some of my pains I have documented over on the dark side: Hypertrend draws fake gap in data Enhanced RT breaks build Exe shows splash screen whilst loading Corrupt Timestamp Reg for Server Events Date Type Issue Logging Bound IO Issue Copying Control removes binding FP Security performance issues PSP LED issue Multiple Variable Editor issue Remove Process Dialog issue Writing to Citadel issue \ polyVI issue Having said that, it was still a good toolkit - just seems a bit unpolished (there seems to be some inside info as to why this may be the case - I have only read what others have posted). At the end of the day it got the job done, and there is no way I could have written app's functionality from scratch and be cost-competitive. The extra money for a RT per PC is negligible (i.e. when you compare it to the x hrs programming cost). I definitely look forward to seeing this toolkit get better with age (and even seeing some of its functionality in core LabVIEW).

I have just completed the process of taking the Open Source tool Rename LVOOP Labels from a Standard to a Silver Addon on the LabVIEW Tools Network and it was a rewarding... View the full article

Hi Olivier. That is a good point. I guess it is just inertia that sends be back to OpenG File>> option. I will follow this up with the OpenG Board regarding deprecation. Cheers -JG

Yer, I thought there would be a reason (i.e. older version) - my intention was to keep it inline and up to date with other packages. The new layout standard was designed to work the best with VIPM, so unless the project moves to VIPM 2011 etc... there is no point. Do you think that project should be deprecated?

That's correct. The 4.x package was based on the 2.5.1 code. I am not sure of any issues relating to the following and of the current state of the project: but it would be great to have this project converted to the new (VIPM) directory layout, re-compiled in LabVIEW 2009 and released using VIPM 2011 so that it is inline with other OpenG Library Packages (same for PortIO). Cheers -JG

I have updated a few OpenG Tools to LabVIEW 2009 and VIPM 2011, addressing any issues along the way. These packages will be available for download through VIPM in a few days. Rename Folder of VIs (v4.0.0.15) Note: This tool should be mass compiled (VIPM option) for use in LabVIEW 2010+ otherwise it will take a while to load due to the internal dependencies. Locate File in Project (v4.0.0.7) Compare VI To Disk (v4.0.0.9) Thanks to Danny Thomson for reporting, fixing and testing a bug relating to Application Instances. Kind regards Jonathon Green OpenG Manager

I agree, its not a replacement, its an accessory. I have iPhone which covers me for mobile email, internet, forum etc... I also have access to iPad - which is a pretty nice bit of kit. But as the phone does what I need (also acts as a modem), I find having a Windows laptop around is more handy than an iPad is.

Jason Willis, aka WireWarrior on the LAVA forums, is a CLD from Little Rock, Arkansas, USA and very keen to start helping. On behalf of the OpenG Team I would like to welcome Jason on board and look forward to his contributions! In fact, he will be chairing the Variant Config Update - haven't seen it? - check it out here! Kind Regards Jonathon Green OpenG Manager Wanna be an OpenG Developer too? PM me.

This OpenG Review is active. There are a few outstanding issues with the Variant Configuration as well as some feature requests so I thought it would be a good idea to start a summary thread to track them as well as to review all of these at the same time (in case of interactions etc...). Note: What will be implemented and when is not the point of this thread - that will be decided at a later date by the OpenG Team. If you know of an issue (link to an existing thread LAVA or OpenG), want to report something or have a new idea please post in this thread. For anything new, please create (or I will create a) new thread so that it can be discussed in detail. Please do not discuss these items in this thread - use that item's own thread. The point of this thread is to bookmark and manage these items for review I will keep this original post as up to date as possible An item with an ID link is a link to an OpenG Tracker Any item with a description link is a link to an existing thread (LAVA or OpenG) I am pretty excited to see work done on this OpenG Library as this is my favourite OpenG API. Kind Regards Jonathon Green OpenG Manager Current Items for Review: ID: 3411108 - Recursive OpenG VIs should use native recursion (if performance benefit) ID: 3409853 - Reentrancy bug in Write Key (Variant) VI? ID: 1501747 - Unnamed cluster elements cause problems ID: 1156973 - Fixed size arrays & Read/Write Panel to INI ID: 3004519 - Use custom decimal sign for floats ID: 849694 - Units in INI-files? ID: 848288 - Missing Key output ID: 3004517 - Writing to Panel deprecated issues (LabVIEW 2009) Bug: Read Key(Variant)__ogtk.vi: VI looses variant name Throw error on duplicate data Cannot load an array of classes using variantconfig

I have seen that before - could be a bad VI? I usually approach it by breaking down the exe - start building an exe using a component each time, until that error message pops up.

I really like the idea of the auto-generated forum post from an article for some of the following reasons: It synchronizes an article's comments to the forum It makes the article more visible However, I do not like how it posts an entire copy of the article with missing images etc.. Real article: Forum article: Is there a way to show a smaller snippet of the article or just a link to the article - just like theblog feature does? Cheers -JG

They are better for beginners IMHO, after that they just take up too much space. The only time I use them now are in event structures for UI elements.