I'm very interested in xCE configuration Editor.
I'd like to personalize the xCE in order to have the possibility to change programmatically some attributes of the node as for example description and movable. I need to save this "modification" to the xml file in order to have the possibility to load them again.
I've done some test with the Description attribute and everything works well: I change the description at run time, saved the xml and when I load it again and the description was present.
I've done exactly the same think with the Removable attribute, but the change is not been saved in the xml file and so not loaded.
Effectively the xml file doesn’t contain all xCEData Node attributes. Is there a possible workaround.
Probably solved modifying:
including also the Removable attributes.
This reference design looks very usefull to me!
I was wondering if a getting started guide/walkthroug is available. (Cannot find it in the source.zip)
Thank you for this xCE library. I have used it to make a sCE (Simulation Configuration Editor). Defining, ordering and running some simulation modules in the UI. It works very well.
I would like to access the variant variable "key-value pairs" in "LabVIEW 2015\vi.lib\NI\Configuration Framework\serializable configuration\NISE_CEF_serializable configuration.lvclass". I would like to have an accessor method for the variable itself to read the complete configuration (generically) without knowing the keys. Right know I'm forced to use a workaround with the functions "to string.vi" and parse (similar like within the function "from string.vi") the output "data" to get (and display) all the key-value pairs.
Please find attached the snippet of the "workaround".
Hi Qsi, I created the issue for this in github:
It will be included in the next build of CEF, which we will update this week or next. I created a property for read only and gives you the key value pair as a 2d Array.
Also the forum thread for CEF is: http://forums.ni.com/t5/Development-and-Deployment/Configuration-Editor-Framework-CEF/td-p/2730619. The link pointing to this tread in the whitepaper was wrong, and I just updated it.