Ton Plomp

Good you solved it, I had a look at your program, if you reset the histogram function, why do you run the measurement twice? If you need that for some reason, but only use the histogram function at the last run, put it outside the for-loop. Ton

Okay: here it is the dynamic generation of XControl properties. This first alpha version is somewhat limited: You need a special state format (actually it needs a XCTL array of control references You need a special facade vi (see the time-out case Only creation of properties Only creation of first generation properties (eg. label.text won't work, though they are selectable) No feedback about created properties You'll only know the program is done because the mouse is normal again.... No instructions beside these... The Program: and a template XControl: disconnect from library.vi Here is a screenshot: After starting select an XControl with Select XControl, then select the controls, then select the properties. The generation is then done. You can open the XControl by using openXControl. Some Bugs: Sometimes saving everything inside the xcontrol, and closing it totally will fix the xcontrol Yes Crelf, it is not really CR ready material Ton

Michael, That was the trick. And I thought I had looked everywhere. Only this list is not alphabetically sorted..... aaaahhhhhhh :headbang: And Jim is right you should save the VI and XControl afterwards! Ton

Or more clear, you have a graph with 20 Meg of data..... you can ditch this before closing the containing vi Ton

You're right, but I wonder is there anyone who has generated lvlib's? NI is doing it so there should be a property/method to claim a VI. Ton

Make the control a typedef!: Ton

Hello, I have the following improvement suggestions for the CR: For a developer feedback is food. It would be nice if users automatically got a poll two weeks after the download asking the following: What do you think about %CR%: Looked at it, not worth trouble using Looked at it, is OK can't use it right now Use it sometime Use it regularly unmodified Use it regurlarly modified Ton

Hi Aristos, I allready solved that, with this code: So the XControl knows it is a property inside the right property folder. The problem is the VI, it doesn't know it is part of the XControl. In a way XControls behave like lvlib's (here kicks in your knowledge about classes) The library is looking for: thisXcontrol.xctl:myProperty_read.vi This is not found on the disk only myProperty_read.vi, and I have to browse to the file. When I open the item from the XControl I get the following: Does anyone have a clue to resolve this? Not that this are normal properties and methods not supersecret...... Ton

Hello, I am trying to generate properties for XControls. I know how to add them to the XControl. But when I open the Xcontrol the XControl is broken and says the property is missing. And if I open the new property VI, it needs to be updated to get linked to the XControl. To prevent this I save the property and close, add it to the XControl, save the XControl, open the property and save the property. This has not solved my issue. Does anyone know how to do this (Jeffrey?) Ton PS it is currently the only thing between inheritance for XControls

Just a status update (or what have you done in the holidays?) I can generate the first generation properties (read and write) (so just visible, label.text and othere subclasses not yet, though they are not that difficult) I can add them (in some way) into the XControl, allthough I have mayor issues with the state typedef. My vit uses another one than the xcontrol and won't accept the new one.... I cannot generate the Methods (haven't looked int it) Hopefully this friday I'll have it sorted out about the property creation into the XControl... Ton

Darn too late Well here it is: Happy New Year!!! Let the wires rule 2k7 Ton

Strange, Now it is gone, but mine worked earlier (no-one around). Just to get the idea, is this some sort of group-meeting possibility? Where you can discuss live about some topic? It would be nice if a skypecast shows up in your skype program... EDIT: OK skype 3.0 has a live tab Maybe something to plan? I only have skype at home so between 8 and 10 CET would be best.. Ton

Does anyone know how to detect the type of the inherited item? If I use a propertyitem label on a string control I get a label-reference, I haven't succeeded in determing the type using OpenG-toolkits. PJM private class generator doesn't know the classes as well. I have found out that the classID is 5 one of the low ones PJM hasn't identified. Does anyone have a clue? Ton

Good, a question for all: I have a framework where the developer can choose for which facade VI controls the inheritance should take place. Now in the XControl a folder %control1%.properties and %control1%.methods will be placed with the properties and methods. But several issues arise: How to get the facade VI control reference inside the property VI. A reference to the XControl is available but that is not easily parsable into the facade VI Should we pass the controls around via the display state? What about the inherited properties like 'Scales', 'Text' and 'Numeric'? I think we need them What do you think about these Items, esp. nr 1!!!! Basically I am looking for VI's that allow automatic property and method generation Ton

What about: resource\Framework\Providers\xi\xctl.llb\facade.vit??? Hopefully this time I have answered the right question! Thanks for asking I was kinda looking into these as well Ton

Sorry I answered the wrong question, but if you look at how the original properties/methods are implied true inheritance is used. Using the AllProps property of a string, there is no such property label.text or caption.text. Just two references of the type 'Text', Is there a way for use to mimic this? Ton

I agree, do you think it is a lot of work to read all the properties/methods of a normal control and process this into properties and methods of an XControl? with scripting off course Then if you have a XControl consisting of several controls, should you build all the controls, or just some? Ton

Hello Alameer, First forget the dynamic data type, you never use it in your code. Have the Daq assistent put out a Voltage (or better the theta, but that is another exercise). Then probe what theta comes out, is that correct? Another tip, use executed highlighting. Ton

So Michael asking questions. First the easy one: Use the description: The container state contains the reference to the xcontrol The second one looks more difficult, but fortunately not: And here is some proof: The help text is just the string, which originates from the numeric-data in a standard X Control Now, Michael what are you going to do with this. Hopefully a way to build an Xcontrol which has all the properties of normal LV controls, and this build with scripting? Ton

What if you run two copies of LabVIEW? Ton

You're welcome, For storing data on a remote drive RT has no network shares client. What you can access remote is a DB via TCP/IP (I think you should just try to run the DB toolkit, I wouldn't know why not. Another item would be FTP In order to have the RT correct running you should make two processess (typo?) one for the data reading and storing to a queue and one for communicating with the DB. But why not go with a normal PC, let's say a CompactRIO+RT costs 10k

Yes there is, use TDMS Get Properties, from the help: Ton

Recently someone from NI R&D was here, and he told us that most likely the next release had a solved issues list (or bugs) publically. Unfortunately not a known issues.... Ben: I know you are very interested in CARs and bugs, do you store and monitor them? Ton

I got feedback from NI, and they said it will be fixed in the new release (8.2.1/8.3/9.0/LVX) Ton

Oouw Martin, looks kinda bad (wel not kinda just bad), what does the debug file say after a restart? or doesn't it show up? If not look at it from MAX (or locate it with FTP). Ton