02-10-2010 12:32 PM
Hey, I am getting the hang of this... thought it would be alot harder, but five minutes later I got it working. The trick is to set the access scope using a method from LVClassLibrary.
This then creates the following..
Again, thanks for all the help
02-10-2010 12:38 PM
Hi WireJunky,
I think you have license to mark your reply as the solution (unless you want to mark corny's )
Ben
02-10-2010 01:04 PM
cool. Using the name of the object in memory to add it to the project! didnt know that was possible - learned something new
Perhaps even the LVClassLibrary(Name) prop. node can be avoided since you already know the name? (will try this, and ofcourse see what will happen with more items with the same name (if thats a identifier, it should give an error?)
02-10-2010 01:14 PM
Hi corny,
I just put the class name property in there because I was lazy ,
you need to add the item using its full name -for the newly created class this would be "Test.lvclass"
02-10-2010 01:18 PM - edited 02-10-2010 01:21 PM
hehe, thanks. And to inform, it does give out an error:
Error 43 occurred at Invoke Node in Untitled 1
Possible reason(s):
LabVIEW: Operation cancelled by user.
Method Name: LabVIEW Class:Create
with more than one classes with the same name. (dont ask me why its error 43 tho). Edit: The error only happends if one of the objects properties have been read, or written to, before creating a new one with the same name.
02-10-2010 01:31 PM
Trying to think if there exists a situation where you would want or would have two classes with the same name...
cant think of any, but I could be wrong. Now I wonder if it isn't possible to create some override vi's programmaticly.
The first step would be setting the parent of the newly created class and then... somehow create those override vis
02-10-2010 01:43 PM
02-10-2010 02:14 PM
Think Ive hit the end of the road with this endeavor, there are no methods or properties that set the parent of the created class.
There is a property to get the parent, but not to set it. Anyway, was worth a try.... - hope someone can prove me wrong.
At least Ill be able now to create a empty class skeleton with some commonly used virtual folders to organize things nicely