04-24-2012 09:10 AM
04-24-2012 10:53 AM
I haven't tried yet, but probably you can create a "control array" with all the controls you need, then duplicate the control array.
Control array have been introduced in CVI 2010 if I'm right
04-24-2012 01:06 PM
I have used all these methods and must admit that every one of them has some disadvantage. I like the DuplicateCtrl method as it is fast and relatively simple to handle when I have only a few controls to replicate. In a situation like yours I'd probably go the child panel way, since you have very different controls to accomodate on the screen. Additionally, I can handle all controls with a single array of panel handles, thus obtaining a simpler program structure.
The table way is indeed the simplest method but it's limited to the small set of values table cells can have (you cannot embed a graph in cell, for example). Additionally, tha "table-style" aspect the GUI assumes is not the best I can think of when designing the user interface.
I'm afraid I have no real trick to offer that you have not already mentioned.
04-25-2012 05:40 AM
04-26-2012 01:12 AM
As far as I can understand, control arrays simply handling of controls at runtime but do not modify the design of the UIR: you will still need to programmatically duplicate controls next you will need to add new controls to the array. It will be a little bit easies to address the controls from this moment on.
Control arrays can hold controls of different type: in this respect they can ease up your life while programming, provided they are well designed and documented.
As per the user interface browser, you cannot miss it: it shows to the right of the user interface editor. It consumes lots of space too, and on laptop screens this can be a problem. I have posted an idea for adding a panel preview exactly for this reason, which you may feel free to kudos.
04-26-2012 06:27 AM - edited 04-26-2012 06:29 AM
Custom controls, both the so called "toolslib controls" and DAQmx controls, are documented in the tools library chapter in the online help. There are also sample programs for almost all of them, and some are distributed with the code so that you can understand how they work and personalize them further if you want to.
I forgot to mention in my previous post that the user interface browser (as well as control arrays) was introduced with CVI2010: you cannot find it in any previous version of the product.
04-26-2012 08:40 AM
04-26-2012 01:59 PM
Back in 2003, when CVI changed from a top-level window layout to an integrated window lay-out, it retained the optional use of the top-level windows ("classic view") for those users who had a strong preference for the previous style. The expectation was that, over time, the number of users using classic view would diminish. For a while now this option has been considered a legacy option, and thus it's likely that it will continue having fewer and fewer features, relative to the integrated layout.
In this case, the user interface browser and the attribute browser are really features of the workspace window, which kick in when the user interface editor is visible within the workspace window.
Out of curiosity, what is the main reason that you prefer using classic view?