Ton Plomp

Hi James,

Could you fork the repo at bitbucket, add the fix to your fork, and request a Pull request. It woul be great if it can be supplied in LV2009 format.

Regards,

Ton

Why don't you let the VI itself open it's FP?

And if you have a large case structure, it's wise to add a piece of code after CS that inserts the case selecter info into the error data.

TOn

Our company is in a 17025 certified measurement institute, however we are facing issues with the calibration of acceleration sensors, official we need to calibrate them in the whole measurement range. However we weren't able to locate a calibration institute that calibrate up to 60 G with a 17025 compliant certificate.

Does anyone have pointers?

Regards,

Ton

Unless you enable debugging!

Ton

Yes, it's a valid option (IMHO), for the plugins in the Code Capture Tool we have used this method, and we even use the icon!

Only downside is that you need to load the VI into memory to get this info. What surprises me is that you didn't choose an OO implementation with specific methods.

Ton

Hi Mike,

did the LabVIEW wiki help (esp. the page on the Facade ability)?

Ton

You could look at the wiki page: http://www.LabVIEW wiki.org/xcontrol where I have added a lot of information

You can use the following code with two examples:

in the upper method you'll only need to remove the padded string.

Ton

Could you post your code? without code it's hard to identify issues.

Ton

Filed as issue  #22

Fixed in version 3.2.1, that is available at SourceForge and the Lava Code repository. Should go live shortly on the LabVIEW Tools Network.

It's fixed by placing the Mouse VIs in a conditional case structure that's only run for Windows and Linux.

Ton

Hi Antoine,

Yair is right that code is used for the panning/zooming using the scroll wheel. I always thought that code was OS generic.

Can you place the whole while loop + init/close VI inside a conditional structure, to see if it is fixed then?

If so we can easily create a platform limited code for Mac/Linux.

Apparently this code is only available on Win/Linux.

Ton

One additional follow up.

The issue is with the LabVIEW code creation tool.

When I create manually a VI that is identical to the NI created tool I get no 'Save' message

Ton

At first I could not replicate your issue. But I used the Symbio toolkit to change the inheritance and generate the new override VI.

Then I used the standard procedure and I had to resave the VI. The main difference is that the Symbio toolkit does not insert 'Call Parent method'

Ton

I suspect that the file date is changed.

One thing that has always stumped me with a 'get lock' SCC regime is that you need the server to edit the file.

I understand that there's a bug in LabVIEW. A no-op save. But that should not cause any problems. Using the 'read-only' flag is a bad method (IMHO) to control the state of a file. Merge tools are getting better (and NIs LabVIEW merge tool is reasonably good), so one should not rely on the file-date to control the contents of the file.

Ton

Can you inspect what is changed in the saved lvclass file?

Ton

I think AQ means this site: https://sine.ni.com/srm/app/myServiceRequests

Ton

Do you have a binary representation of the BLOB? It might help you to identify the file type.

TOn

Don't forget to set the decimal seperator (%.; ) if you think your program will ever come to a decent part of the world.

Ton

How (and WHY) do you call the VI dynamically? And what exactly do you mean by contents?

You can remove the block diagram (or lock it with a password) to hide the code.

Removing the block diagram means that you need to keep a source copy.

Using a password is not a very strong lock.

Ton

A

Thanks for the pitfall warning.

Ton

Thanks for the pitfall warning.

Ton

I can use the OpenG function 'Class name'  to find the qualified name of the class.

Since I will run this on the default value it will most likely not cost a lot of resources.

Questioning the class via a method is a maintenance nightmare for the class creator.

Ton

Yes that's correct a project is a manager of files while a library/class manages code

Ton

No it's not about scripting. 

I want to create a plugin class hierarchy and have a generic config GUI. If a class overrides a specific method I will enable a button that allows to open a class specific config GUI.

I don't think I make the assumption of the path relationship between the method and the class.

Ton

Well a VI does not know if it belongs to a project (it might even belong to several projects, which is bad), so I guess the best you can do is the following:

This will look in the folder of the VI for a project file, if one match is found that is returned, otherwise it will look to the folder above the VI project, untill the root of the filesystem is found.

If more than one file is found you need an algorithm to find the best match. One option would be the Levenshtein distance

Ton