jgcode

[LV2009] I can script Protected folders into a Library. Bug? -JG

Sweet, that will be a great release. Playing with your example now. Kudos!

This is some cool stuff, and I look forward to the above. However, I am wondering how it is going to be distributed so we could use it in an application? All the called code sits under Resources\Dialog which is not a symbolic path in LabVIEW. This means that when you move your source code around all the linking will break (had the same issue with the Icon Editor API for LV2009) - I even had to relink the example. I guess you could namespace and re-install all the existing Resources\Dialog libraries/code into <user.lib>/<vi.lib>?

Me too (sort of) the corrupt class (if it is the issue) inherits from a reusable component which I think may be the actual issue. It did build previously ages ago, so I have no idea why its doing all this now. The only reason I caught it is that I did a build on an integration VI as the Main VI in the build, and the Front Panel shows Class inputs as "Question Marks". Need to investigate further tho.

Did it get fixed somehow? This one is really weird - I think something has gone haywire with the IDE, contemplating reinstall.

I think this has come up before, with the answer being you had to poll. You can Register for Events from Tasks, but I too would be interested to know if there is an Event Driven mechanism for device notification.

At least I know I am not alone This one is killing me. 2 days and I *think* I may have narrowed down a class that seems to be corrupting the build at the close of business today. Still not sure, back on the grind tomorrow... hopefully have it sorted soon? Branching out into the third day - haven't had a build issue take this long (last time was 2 days). Serves me right I guess, I wasn't incrementally building on this project either (for what ever excuse reason) Would not want to be 400 deep with this one

Here is a cool build message:

On a side note anyone seen things like this before: I have isolated my application where if I disable this VI it doesn't break, if I enable this VI it breaks (keeping in mind I have a whole bunch of other stuff disabled too). The application loads a splash screen show me all the VIs loading too (which is not what ever want!) Building the components by themselves in this VI creates an executable that is not broken so I am unsure why toggling between disable/enable would be an issue. I am wondering if Error 6 - path length error, exceeds 255 character, would cause this? Wondering whether it is happening but the report is not telling me? I am building in C:\a tho, as close as I can get to the root. Still, scratching my head over this one.

This is what the Application Splash Screen looks like:

Thanks Mikael I just checked, it is set for English.

I thought I wasn't, but will have to look closely at the code and cross-check the KB. But this did definitely fix that issue.

This is a ByVal pattern I use a lot and normally I don't find the workarounds that bad for the way you have mentioned implementing it: For point 1. I create an interface class for that algorithm. To get around point 2. if I want, I can leave a parent interface method empty, so if it is not overridden - no dramas - it runs but nothing happens. Mikael H also posted a ByRef implementation too on LAVA.

Thanks Paul It was DSC related and I was able to resolve it simply by selecting the Enhanced checkbox in the build spec the rebuilding. I was more having a whine about broke builds and error messaging - I think it could have been handled better and I commented on this in another thread: There is info on ni.com here about the how the different Run Times are handled if anyone is interested.

** Please note the term Author is misleading - this is the Packager field info. I take no credit for the code, only the fact I packaged it ** Hi drmase I am not sure why it won't install on your system - below is a screengrab of me installing it into LabVIEW 2010 using VIPM 2010 on Win 7. As you can see from the Info Page, the package settings supports all OS and LabVIEW 8.5+ I have installed it on a few PCs - so it should be ok. Can anyone else you downloaded it give feedback? Cheers -JG

Did you find a fix? Yes, it is a build application (didn't use an installer, just an built the executable as I was testing) All languages were ticked, but its not the build spec I think, as this builds fine on another PC without the above issue. Not sure when my LabVIEW flipped, but one day it was working and the next I got the above issue!

I have repackaged this code so its easy to find under the Tools menu (I got tired of looking for it on my HDD whenever I wanted it). Saludos to Aitor. jgcode_rpk_lava_scripting_workbench-1.0-1.ogp [LV 8.5]

No, please, suggest away - I do stupid stuff all the time Unfortunately its not related (the last one was DSC-related) - I was more complaining about the lack of error messaging. (Why does not it just say you need to include Enhanced DSC Support?, or automatically do it for me in the build, or warn me at build time?) Anyways, the above is happening on my PC but works fine on another PC I just tested so I am confused at the moment. That was another build where I was testing some code as I have a worse issue at the moment - my app code works in Dev Environment but not in Run Time, it is broken - and I hate those ones! So generally I have been rather angry today.

I am getting the above RTM from a build - I have never seen those characters before in the RTM. All I am doing is a basic build - new project, single VI with a single control, no custom RTM, EXE build spec with default settings. Have tried reboot PC, but still the same - it looks like something has become corrupt? I have no idea ! Cheers -JG

<gripe> Sweet! - Just build an application then I get these two messages when I run it, then.... ...nothing. </gripe>

Hi Antoine If you search for Silent Install on ni.com you will see that you can customise the installation of the NI components using switches including forcing a reboot. For example the LabVIEW Run Time I don't know if this will fit into your workflow? But I was playing with this (via batch files) recently and thought it was worth a mention. Cheers -JG

Given NI's new annual software release schedule, I for one am more than happy with hearing this news. This is one large feature that affects my everyday work flow - so its great that time and resources will be focused on this area.

Yes well done and thank you too. Don't ever stop posting

Out-perform? Well it depends in what area: The point is that the Windows target is not deterministic - if you have system requirements where you need to minimize jitter then you are going to want to use a Real Time target. Additionally you may have environmental considerations whereby a PC will not cut it, and you require the ruggedness and toughness that a PLC/PAC will deliver. You may need to run a system headless. You may also want to make use of the FPGA for re-configurable IO. The list goes on... At the end of the day the choice will be application specific.