[JS] User Interface to Choose Layer Color (Get List of UIColors)

I know how to set layer color with UIColors so I am not somewhat familiar with how it works. I want to create a dialog (which I know how to do) that has a menu that lets a user choose their layer color. So I want to get a list of all the UIColors and present that as a menu to the user. I cannot figure out how to get this list of colors. I know how to access them individually, but I'd think it would act similar to an array. I can't figure out the code to access the list to use it in a menu. Is this possible and if so how?
P.S. I am supporting InDesign CS2 and CS3.
Thanks in advance.
Dan

Thanks for all the help everyone. We finally have the answer. Here's the following code that I'll be using. While Kasyan's works, I went ahead and made the menu a little nicer to read (like InDesign's actual menu is). My first array is for the dialog's menu, the second array contains the proper code I need later for setting the menu color. Again, thanks for all the input. Doing this in just CS3 was so much easier, but I also need to support CS2, so this works just fine (in both CS2 and CS3).
myLayerColorMenuArray = [ "Light Blue" ,
     "Red" ,
     "Green" ,
     "Blue" ,
     "Yellow" ,
     "Magenta" ,
     "Cyan" ,
     "Gray" ,
     "Black" ,
     "Orange" ,
     "Dark Green" ,
     "Teal" ,
     "Tan" ,
     "Brown" ,
     "Violet" ,
     "Gold" ,
     "Dark Blue" ,
     "Pink" ,
     "Lavender" ,
     "Brick Red" ,
     "Olive Green" ,
     "Peach" ,
     "Burgundy" ,
     "Grass Green" ,
     "Ochre" ,
     "Purple" ,
     "Light Gray" ,
     "Charcoal" ,
     "Grid Blue" ,
     "Grid Orange" ,
     "Fiesta" ,
     "Light Olive" ,
     "Lipstick" ,
     "Cute Teal" ,
     "Sulphur" ,
     "Grid Green" ,
     "White" ]
myInDesignUIColorArray = [ "lightBlue" ,
     "red" ,
     "green" ,
     "blue" ,
     "yellow" ,
     "magenta" ,
     "cyan" ,
     "gray" ,
     "black" ,
     "orange" ,
     "darkGreen" ,
     "teal" ,
     "tan" ,
     "brown" ,
     "violet" ,
     "gold" ,
     "darkBlue" ,
     "pink" ,
     "lavender" ,
     "brickRed" ,
     "oliveGreen" ,
     "peach" ,
     "burgundy" ,
     "grassGreen" ,
     "ochre" ,
     "purple" ,
     "lightGray" ,
     "charcoal" ,
     "gridBlue" ,
     "gridOrange" ,
     "fiesta" ,
     "lightOlive" ,
     "lipstick" ,
     "cuteTeal" ,
     "sulphur" ,
     "gridGreen" ,
     "white" ]
var myDoc = app.activeDocument;
var myDialog = app.dialogs.add({name:"Select Color"});
with(myDialog.dialogColumns.add()){
   staticTexts.add({staticLabel:"Choose a color for the active layer."});
   var myDropdown = dropdowns.add( {stringList:myLayerColorMenuArray, selectedIndex:0} )
var myResult = myDialog.show();
var myIndex = myDropdown.selectedIndex;
if(myResult == true){
   myDoc.layoutWindows[0].activeLayer.layerColor = eval('UIColors.' + myInDesignUIColorArray[myIndex]);
else{
   alert("You clicked the Cancel button.");
myDialog.destroy();

Similar Messages

  • UI (User Interface) text size and colors

    Recent versions of Elements (7, 8, 9) have changed to a user interface which is predominantly shades of gray and black with few if any user options for color or font. The font size cannot be altered because Adobe use their own pixel-based font which is not compatible with Windows Desktop settings. So on many flat screens with high resolutions the font becomes almost unreadable. The upper case 'E' in the menu bar Edit for example, is a mere 2.03mm high on a 22" display at 1920x1080 resolution.
    This has been mentioned a number of times over these releases to no avail, but at last there may be a change on the way for PSE 10 (later later this year?).
    So if you feel the gray/black UI needs attention I suggest you visit
    http://feedback.photoshop.com/photoshop_family/topics/my_eyes_need_help_with_photoshop
    where there are a number of comments. This is monitored by Adobe so may influence the next release. The more request there are I suspect the more likely some action. Adobe have already commented: "The amount of conversation that this thread has generated among Elements customers was unanticipated." on the thread.
    If you wish to place a comment you will need a Photoshop Account and to be logged in. If you didn't create an account when you installed the product then just click Create Account at the top of the link above.

    Font sizes are hard-coded in teh apps and there is no way to change that. The new CC versiosn support high-DPI displays and resolve those issues (mostly).
    Mylenium

  • User Interface bug when renaming tracks in list views

    When renaming tracks in the list views, there is a user interface bug that makes it impossible to see what you're doing.  When you select a track in the list view, this is what it looks like:
    Note how the text is white on the darker blue background.  When you click again, to open the inline text editor to rename, this is what you get:
    The background color of the text editor is white, just like the text, so when you type, you can't see what you're typing, nor can you see where in the original text your text insertion cursor is located.
    Thanks!
    Steve.

    I'm frustrated with this same problem. In my case this happens only in my 10.5 macbook air and not in my 10.4 macbook pro. I've been renaming files in the same way in 10.2/10.3 and this never happened. Should be a bug. I've been searching for this issue and found this post at last - I really wonder why there aren't so many people mentioning this.

  • User interface for choosing movies.

    Folks,
    My wife and I get movies from Apple TV about once a week. One thing that annoys us is how long it takes to browse through the movies looking for something interesting to watch.
    Having to scroll through all of the DVD "box covers" takes way too long. The covers take up so much of the screen that you have to page dozens of times to get from A to Z.
    In addition it is sometimes hard to tell what the movie is from the cover. In many cases due to the design of the cover the movie title is hard to read. In these cases we have to move the "cursor" to the movie in order to be able to see the title as it "lights up" underneath the "dvd box".
    This makes browsing take even longer.
    My suggestion would be for the interface to be reversed. That is show only the names of the movies in rows and columns and pop up the box cover of the selected movie (the one the cursor is on) in the top, bottom, right or left margin.
    Let me know what you think,
    KW

    The grid does seem to waste space. I liked the movie trailers section pretty good when you could see the cover art as you scroll down the list on the right. It just made it alot quicker to see if a new trailer was out or not. It would be nice if browsing movies was easier. I think the grid layout sort of resembles a video store shelf and maybe that was what they were going for... something that looks like a video store.
    But if you think about it more logically, when a person is browsing titles in a video store, they look at each one individually (even for a split second) and process the cover art and the title and move on until they find what they want. The column list provides this level of interaction for me. Its faster because I only have to move in one direction to see all the movies.
    On my 50" tv I cant even see the covers good enough to avoid scrolling all over the place, burning up my remote battery! (its a conspiracy to sell more batteries! )
    I think it should be a preference for each menu set, grid or column list.
    Anybody else want to be able to customize at the very least the views for these types of things? They could put it at the top of each screen grid or column. Maybe even use those little view selector icons they use in iTunes...

  • Freeze problem in user interface initiatilisation after all NVDIA update and 8.0.1

    I just received Pre 8 and installed it
    When starting the various modules
    - Organiser works more or less fine (it crash when it looks at my folders with 28000 pictures), but it works when doing import folder by folder
    - but when I am starting a new project
    I never get to the user interface of the software
    I get a small red dot and when clicking problem with your driver
    I have already looked at the forum
    updated at NVidia site
    I am running a
    Dell Inspiron 1720
    Windows 7 , 64 bits, French
    4 GB RAM
    NVIDIA 8600 M GT
    latest NVIDIA driver from July 2010 (version 258.96)
    Installed PrE 8 French from the DVD
    upgraded to 8.0.1 from the Adobe website
    I can not use any of the software function as the screen is fully black and I only see the top level menus
    theoptions are availalbe but non of them is working
    and the message atbottowlefttays at user interface initialisation
    Thanks

    I've never set Portuguese, so I really don't know what to tell you. It would be my presumption, though, that this sort of feature would be handled in the World-Ready Composers, but clearly there is either a bug or I'm mistaken, or both.
    I would suggest you file a bug report at Adobe - Feature Request/Bug Report Form, though I doubt there will be a fix.

  • OCS Content services web user interface

    Greeting all,
    Is Oracle drive client required to perform the edit feature when attempting to select edit under the web based content services on a file. When I select edit from the web based user interface on a file I get a error saying that oracle drive is not installed.

    I reinstalled with the newer version as the upgrade from the previous version was not to smooth, and I was left over with to many broken pieces after the upgrade attempt.
    I suspect that I'm going to find out that the file versioning and check in and check out features are going to require oracle drive installed as well. This is not a option for us, as our remote clients need to use a pure web type interface/connection. It seems as if oracle still has some work to do to get the content services Web UI to were we need this to go.

  • How to get list of classes in classpath?

    Hi.
    I need to get list of classes in CLASSPATH which implements the some interface.
    How i can get list of classnames from CLASSPATH ?
    TIA

    What you want to do is not that trivial.Its not trivial, but its not really all that hard either.
    I this thing quite a bit in JUnit tests (e.g, all SomeInterface implementations are expected to be serializable - lets hunt them out and check we can actually serialize them. Turned out to do that I needed a generic yet fairly intellegent object creator / populator: That was significantly less trivial than the other task).

  • Why do I get -18001 Errors using Customised TestStand User Interface

    Hi all
    I have a problem when attempting to run my application on my host NT PC. I have a customised operator interface to TestStand written using Labview 5.1.1 and built using the LabVIEW application builder. I am running the TestStand Development (Run-Time) System on my host PC.
    The problem is that as soon as I go to run my sequence of vis (mass compiled using the same version of LabVIEW and assembled for run-time distribution) I receive the error '-18001 VI Not Executable.'
    I think this is probably to do with how I've included the ActiveX server in my LabVIEW User Interface application, but knowing very little about ActiveX I'm not sure exactly what the problem is.
    If anyone
    has any ideas, I would be extremely grateful for any assistance you could offer. My TS version is 1.0.1
    Thanks
    Dave

    David,
    I would like to add to Richard's input. The typical reasons a VI cannot be executed that cause this message are:
    1) There is an error in the VI such that the run arrow of the VI is broken when the VI is open in the LV development environment. This problem is usually easy to debug because you should get the error (shown below) when running your sequence in the sequence editor using the default "LabVIEW" ActiveX server provided by the LV development environment (not the LV ActiveX server provided by your operator interface which is by default named "TestStandLVGUIRTS" ).
    An error occurred in the 'MyVIStep' step of the 'MainSequence' sequence in 'MySequence.seq'.
    LabVIEW : VI is not executable.
    An error occurred accessing the LabVIEW ActiveX automation server. Error Code: -18001
    2) The same error will occur when
    a. you are using any LV ActiveX server other than the "LabVIEW" server provided by the LV development environment, AND
    b. at least one of the called VI was not assembled for distribution properly. This means that not all test VIs and their *entire* hierarchy were distributed.
    I am not sure exactly what you have done so have compiled some information that I think will help. Below I have included the document, Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter, which will appear in the NIDZ shortly. Another useful document is the NIDZ document Distributing LabVIEW Test VIs, which you can obtain from our website. Read these documents before preceding with the steps immediately below, which give you an example process for distributing. This may help provide a better understanding and guidance in the distribution process. We are working to simplify this process in future versions of TestStand.
    For the following example distribution I recommend that you are use default shipping code so that the problem is not complicated with potential errors added through customizations you have made.
    Building The Operator Interface
    The following are steps if you are using a LabVIEW operator interface.
    1) Copy the contents of \OperatorInterfaces\NI\LV to \OperatorInterfaces\User\LV.
    2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
    3) In LabVIEW Select Tools>>Build Application or Shared Library
    4) In the builder click the Load button and load \OperatorInterfaces\User\LV\testexec.bld. This build script is configured to create testexec.exe that contains the LV ActiveX server with the name of TestStandLVGUIRTS (see the Application tab of the builder).
    5) In the builder click Build.
    6) Once the application testexec.exe is built, run it once so that the server TestStandLVGUIRTS is automatically registered. You do not need to run a sequence. Close texec.exe.
    Creating a LabVIEW Run-time Server
    If you are using the LabVIEW operator interface then skip this section. The following steps are meant for those who use an operator interface written in a ADE other than LabVIEW. They provide you with a LabVIEW run-time server that is used by TS to run your VIs.
    1) Copy the contents of \Components\NI\RuntimeServers to \Components\User\RuntimeServers.
    2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
    3) In LabVIEW Select Tools>>Build Application or Shared Library
    4) In the builder click the Load button and load \Components\User\RuntimeServers\LabVIEW\TestStandLVRTS.bld. This build script is configured to create TestStandLVRTS.exe that contains the LV ActiveX server with the name of TestStandLVRTS (see the Application tab of the builder).
    5) In the builder click Build.
    6) Once the application TestStandLVRTS.exe is built, run it once so that the server TestStandLVRTS is automatically registered on your development machine. Close TestStandLVRTS.exe.
    Assembling the Test VIs for Run-Time Distribution
    This distribution process uses one of the shipping TS examples that calls LV VIs.
    1) From LV mass compile all VIs in the directory \Examples\AccessingArrays\UsingLabVIEW\. Please make sure that there were no error messages in the Status tab of the Mass Compile dialog box.
    2) In the sequence editor open \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq
    3) Confirm that the sequence runs without problem.
    4) In the sequence editor select Tools>>Assemble Test VIs for Run-time Distribution.
    5) If you are using TestStand 2.0 select \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq as the file from which the VIs should be assembled.
    6) Set the target directory to be something distinct like C:\temp\AssblVIs.
    7) If you are using TestStand 2.0 skip adding Dynamic VIs
    8) Save with or without diagrams. Its your choice.
    Change Search Directories
    Once the VIs are assembled successfully, you must add the new target directory to the TS search directories.
    1) In the sequence editor select Configure>>Search Directories.
    2) Add your target search directory (e.g. C:\temp\AssblVIs) to the search directories.
    3) Close the Edit Search Directories dialog box.
    4) Confirm that your sequence steps now reference the assembled VIs. Right click on a step in the sequence and select Specify Module.
    5) The dialog should show that the code module is found in the target directory (e.g. C:\temp\AssblVIs) that you just added to the search directories.
    6) Run the sequence. This is the initial test to see if the VIs are assembled properly.
    Switch the LV Adapter to use the TestStandLVRTS server or TestStandLVGUIRTS
    1) In the sequence editor select Configure>>Adpaters.
    2) In the Configurable Adapters control select the LabVIEW Standard Prototype Adapter and then click the Configure button.
    3a) If you are not using the LV operator interface then switch the ActiveX server to TestStandLVRTS.
    3b)If you are using the LV operator interface then switch the ActiveX server to TestStandLVGUIRTS.
    4) Close the adapter configuration dialog boxes. You will get a couple of questions boxes. Just click OK each time.
    5) Now run your sequence. If successful you are no longer using the LV development environment to run your VIs. This shows that the VIs were assembled correctly, the LV ActiveX server is working properly and that the search directories are configured properly.
    You can now try and run the sequence using your operator interface on you development computer. If this test works it means that you have also confirmed that your operator interface is working correctly with all the other components. Now it is just a matter of moving all the component correctly to the target machine.
    Distributing Components
    -To distribute your operator interface use the distribution tool of the application development environment (ADE) in which you built your operator interface.
    -To distribute the TS engine using the Run Engine Installation Wizard tool. This tool is typically not used for distributing your sequences and VIs, which you will probably distribute more frequently than the TS engine. It does distribute and register your LV run-time server (if you are using one) as long as you have stored it in \Components\User\RuntimeServers. It also distributes other TS components that you have stored under the directory \Components\User\.
    -You can use whatever distribution system you like to distribute your VIs and sequence files (e.g. ZIP and network transfer are popular) . Ensure that you distribute the assembled VIs and not the development VIs. Also ensure that the location of the VIs on the target machine is one of the TS search directories.
    Hope this helps.
    Regards,
    Kitt
    =========================================
    Title:
    Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter
    The general outline of the components to be distributed and the actions to take are followed by a more detailed description.
    Components that need to be distributed:
    TS engine
    Operator interface
    LabVIEW executable that will act as a LabVIEW ActiveX automation server (If the operator interfaces is written in LabVIEW, it can function as the LabVIEW ActiveX automation server.).
    LabVIEW run-time engine
    LabVIEW test VIs
    Test sequence files
    Actions before distributing:
    It is recommended that you test the distribution components on the development machine before you distribute them to your target machine. In this manner you can more easily debug errors that you may encounter
    Create the executable that will serve as your LabVIEW ActiveX server on the target machine (components 2 or 3 above).
    Assemble the test VIs for distribution.
    Update the TestStand search directories so that the sequences reference the assembled VIs.
    Configure the LabVIEW Standard Prototype Adapter to use the LabVIEW ActiveX server that you will install on the target machine.
    Test the distribution components on the development machine.
    Enter section headings, separating each section with a line break:
    TS Engine Component
    Operator Interface Component
    LabVIEW ActiveX Server
    Configuring the LabVIEW Standard Prototype Adapter
    LabVIEW Run-time Engine Component
    Assembling your Test VIs for Distribution
    Note
    TS Engine Component
    With any TestStand distribution you must install the TestStand runtime engine on the target machine. The Run Engine Installation Wizard tool, found under Tools menu of the Sequence Editor, facilitates this process. The wizard tool will create two files, SetupTSEngine.exe and TSEngine.cab. Move the two files to your target machine and run SetupTSEngine.exe to install the TestStand engine.
    These installation files include the current configuration settings that exist in the Sequence Editor at the time the tool is invoked. It also includes all process models, TestStand types and step type modules. If you have customized components of TestStand and saved them under the directory TestStand\Components\User, then the components will also be included with the engine installation.
    You must purchase at least a base deployment or debug deployment license for each machine on which you install the TestStand engine.
    Operator Interface Component
    You will also need to install an operator interface executable on the target machine. This program acts as a client to the TS runtime engine, controlling the execution of sequences and displaying their progress. TestStand ships with several versions of TestStand operator interfaces, which are written in different application development environments (ADE). For distributing the operator interface executable, refer to the application development environment in which it was created.
    LabVIEW ActiveX Server
    You must have a LabVIEW ActiveX server on the target machine. TestStand uses the LabVIEW ActiveX server to run VIs using either the LabVIEW development environment or the LabVIEW runtime engine. The LabVIEW ActiveX server is provided by either LabVIEW development environment or by any LabVIEW executable that has been built with �Enable ActiveX Server� selected. This setting can be accessed in the LabVIEW Application Builder during the build process. When this preference is enabled, you must enter a server name. You will use the server name to configure the LabVIEW Standard Prototype adapter in TestStand.
    If your operator interface is written in LabVIEW, then it can act as the LabVIEW ActiveX server on your target machine. TestStand ships with two operator interfaces written in LabVIEW. The standard LabVIEW operator interface is located in TestStand\OperatorInterfaces\NI\LV, while a simplified version is located in TestStand\Examples\OperatorInterfaces\Simple LV. LabVIEW buildscripts are provided for these applications to facilitate building an operator interface in the latest version of LabVIEW. The settings of these buildscripts are such that the applications are LabVIEW ActiveX servers with the server names of TestStandLVGUIRTS for the standard operator interface, and TestStandSimpleLVGUIRTS for the simple operator interface. The applications register the servers the first time they are executed. If you want to manually register or unregister one of the servers, you can invoke the executable with the /RegServer and /UnregServer command-line arguments respectively.
    If your operator interface is programmed in a language other than LabVIEW, then you will need a separate LabVIEW executable to provide the LabVIEW ActiveX server on your target machine. For this purpose, TestStand ships with a LabVIEW run-time server application located in TestStand\Components\NI\RuntimeServers\LabVIEW. A LabVIEW buildscript is provided for this application to facilitate building a run-time server in the latest version of LabVIEW. The settings of this buildscript are such that the application is a LabVIEW ActiveX server with the server name of TestStandLVRTS.
    Note: When an ActiveX executable server is accessed, the executable is launched automatically if it is not already executing.
    Configuring the LabVIEW Standard Prototype Adapter
    When TestStand runs a VI using the LabVIEW Standard Prototype adapter, it does so using a LabVIEW ActiveX server. By default the adapter is configured to use the �LabVIEW� server, which is provided by the LabVIEW development environment. If you do not have the LabVIEW development environment on your target machine then you must configure the LabVIEW Standard Prototype adapter within TestStand to use a different server (e.g. TestStandLVGUIRTS, TestStandLVRTS, or TestStandSimpleLVGUIRTS).
    To configure your LabVIEW Standard Prototype adapter, select Configure>>Adapters from the menu. In the Adapter Configuration dialog box that appears, select the LabVIEW Standard Prototype Adapter in the Configurable Adapters section. Click the Configure button. You can select or type a server name in the Select or Type Which LabVIEW ActiveX Server to User control. If your server name is not in the list you will need to type it.
    As explained in the LabVIEW ActiveX Server section above, TestStand ships with LabVIEW buildscripts to build a LabVIEW operator interface and a LabVIEW run-time server application. These applications are LabVIEW ActiveX servers with server names TestStandLVGUIRTS and TestStandLVGRTS, respectively. You can configure you LabVIEW Standard Prototype adapter to use one of these servers.
    LabVIEW Run-time Engine Component
    If any of your sequence steps use the LabVIEW adapter or if your operator interface is written in LabVIEW, then you must install the LabVIEW runtime engine on the target machine. It is important that your LabVIEW run-time engine is the same version as the VIs that TestStand executes.
    You can find installation files for the LABVIEW 5.1 run-time engine in the LabVIEW installation directory, Labview\APPLIBS\installs\RunTime. In addition, you can choose to automatically distribute and install the LabVIEW run-time engine with the distribution of a LabVIEW executable. Refer to LabVIEW documentation.
    Assembling your Test VIs for Distribution
    After distributing TestStand, you must ensure that your sequences are able to locate the VIs they call, and the VIs must be able to locate their required resources.
    One common mistake is to simply copy the original VIs from the development machine to the target machine. Once you have configured your LabVIEW Standard Prototype adapter to use a LabVIEW ActiveX server other than LabVIEW, your sequence will not be able to execute your original test VIs that your sequences call.
    TestStand provides the Assemble Test VIs for Distribution tool, which gathers test VIs and their required resources, and places them in a common location for distribution. You can then modify your TestStand search directories so that your sequences reference the assembled VIs. These topics are covered in the NIDZ document Distributing LabVIEW Test VIs.
    Links: See Distributing LabVIEW Test VIs below
    Note
    Remember to test your distribution components on your TestStand development system before distributing TestStand. If the execution does not work on the development system it is not going to work on your target machine. On your development machine you have more ability to debug problems you may encounter.
    Note: One common problem of testing distribution components on your TestStand development system is that your sequences reference the original Test VIs instead of the assembled test VIs. Refer to the NIDZ document Distributing LabVIEW Test VIs for assistance.
    Once the components work on your development machine, you are ready to install them on your target machine. The order in which you install these components on the target machine is irrelevant.
    ==============================================

  • How to get to learn using TestStand User Interfaces

    I am starting to work with TestStand and I was looking into using the User Interface.  I know that a couple of examples are provided and that there is a couple of sections of literature on the subject, but there does not appear to be a very helpful (get started from scratch) type of documentation that I can find.  Does such a thing exist?  If not, what is the best way to get started?
    Solved!
    Go to Solution.

    You can currently do this in the Full-Featured UI without any modifications.  It's kind of a hack though:
    So assume that an execution is running.  The user clicks the Break button and wants to rerun a step with different parameters.  So now your execution is paused somewhere below the step.  Right click the step and select: Set Next Step to Cursor.  Now in the Variable window look for the variable that is being passed as a parameter to that step.  Say for instance Locals.Foo is being passed to your VI.  Change the value of it and click the Resume button.  This also assumes that you are passing either Locals or FileGlobals to your VI.  You may have to have Administrator privileges to do this.
    If this isn't good enough then there are ways to accomplish what you want in a cleaner manner.
    One way is to build your sequence file such that if a certain condition occurs then retry with new values or values from a file which can be changed by the user.  This is what I would recommend because it will be the cleanest and the easiest.
    Another way is to build into your UI like you are asking about.  The problem with this is at a certain point the user will click Break or a Stop button that you have put on there.  This will stop the execution at some point (who knows exactly what point unless you write code to specify a point).  Then they would have a pop up or something that would allow them to select a step.  Then for each step you'll have to have some code or a parser or something that will determine the parameters and valid values they can be and ask the user for those.  This is all doable but would be quite a task.  You will have a long ways to go in understanding the TestStand API in order to accomplish this.  In fact there would be so many API calls with numerous ways to attack this problem. 
    Whichever way you choose to go you will always have the TestStand forums or NI support.
    jigg
    CTA, CLA
    teststandhelp.com
    ~Will work for kudos and/or BBQ~

  • Getting the value from a StationGlobal reference variable in TestExec User Interface Editor Mode.

    Hi,
    I am using the TestExec User Interface editor mode, in the SequenceFileLoad callback from my sequence an instance is made from a C# code module
    (the code module is located in another dll) , this reference is stored into a station global variable.
    Now I want to retrieve the reference from the station global variable in my TestExec User Interface code.
    So, is it possible to get this reference back from the station global variable?
    Best regards

    Reading the StationGlobal is not a problem. But the problem maybe that your reference contained in your StationGlobal is probably not valid once the SequenceFileLoad has completed its execution which it will have done once the SequenceFile has loaded.
    Any references you wish to pickup are best down via one of the ProcessModel callbacks such as ProcessSetup. 
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • How to get the value of the global variable of test stand in labview User interface?

    Hi.
     Can anyone Please share examples and tell me to how access the test stand global variable using labview user interface.
    Solved!
    Go to Solution.

    I'm not surprised that what you are doing doesn't work.  The Start Execution UI Message is triggered when the user clicks a button to start an execution.  Realize that most executions go through a process model.  So you could be looking at the sequence context of the process model and not your client sequence file.
    I recommend reading that link I posted above.  UI Messages are your best bet but you cannot just piggy back on an existing UI Message like this.  They may not be getting sent at the time you need them to be.  The only way to ensure you get what you want is to trigger one yourself at the right time.
    Regards,
    jigg
    CTA, CLA
    teststandhelp.com
    ~Will work for kudos and/or BBQ~

  • Enable user to choose pick color from color palette

    hello, i have a program that uses the color-matching function. when the program runs, i want to allow the user to choose a color from a color pallete and then this color should be matched
    with the colors in images. i use "imaq setup match color pattern" and  "imaq color pattern" functions which use templates  as an input and these templates have to be manually assigned before run.
    is there a way to allow the color palette to act as a templete input???
    thankyou 

    Sure,  Put a color box control on the front panel.  It is located in the numeric palette.

  • Get overall Pass/Fail from custom User Interface

    Hi Guys
    I’m working on a custom user interface for operators and I would like to check and display the overall Pass/Fail result of the test at certain time intervals during execution.
    I added a sequence called ‘GetOverallResult’ to the ‘FrontEndCallbacks.seq’ which checks the Pass/Fail status of the sequence and I’m calling it form a SubVI within the User Interface written in LabVIEW (Check status.vi).
    The problem is that I’m getting the Pass/Fail status of the CallBack sequence not the test sequence I’m running.
    Could anyone please help me in this?
    Attachments:
    Check status.vi ‏17 KB
    FrontEndCallbacks.seq ‏5 KB

    Hi Attila,
    Have you instead tried reading the value directly from the main sequence? Have a look at the attached VI; pass the sequence context in and the Get Property Value VI will read the sequence's state.
    Is this suitable for what you had in mind?
    Regards,
    Tom
    Applications Engineering, NI UK
    Attachments:
    check.vi ‏10 KB

  • Background color of TestStand 2012 User Interface Reverts Back to Default After Changing

    I changed the background color and other properties of the Execution and Sequence TestStand Controls in the TestStand 2012 User Interface example code. When I execute the Top Level.vi the TestStand User Controls revert back to their default colors/properties. I saw this problem in the list of TestStand 2010 known issues, is it also a known problem in 2012?

    Hey kelsayd,
    I just tried changing the color of the user interface controls in my user interface (from TestStand 2012) and saw the same behavior. I believe this is because the controls are ActiveX controls and do not permit the same level of customization as LabVIEW controls. I did find this KnowledgeBase article, which mentions the issue and gives one possible solution to the issue: http://digital.ni.com/public.nsf/allkb/4E40FA5AEAF3937B86256E89007C74C4?OpenDocument
    Hopefully that will help show how you can set this up, and let us know if you have any further questions about it!
    Daniel E.
    TestStand Product Support Engineer
    National Instruments

  • Changing user interface colors

    Hi all,
    we are suing oracle 10g and we also use headstart template,
    How can I change the user interface color scheme my users really do not like the default green colors.
    Please help.
    Thanks

    This can be done in foemsweb.cfg ColorScheme

Maybe you are looking for

  • CCM Publisher issue

    wh have CCM version5.1 and the publisher keeps on rebooting. Any idea why this could be happening or has anyone come across this problem before

  • ESYU: R12 - OM 화면에서 Item LOV를 control 하는 parameter나 Profile?

    Purpose R12의 Sales Order find 화면의 Item LOV를 control 하는 parameter나 Profile은 무엇인지 알아본다. Solution R12에서는 System Parameter에 있는 'Item Validation Org' 값이 Item LOV 값을 control 한다. Navigation: 1. Using Order Management Super User responsibility 2. Setup > Sys

  • Question on using tab navigation

    Hi all -- We have a very large (500+ pages) reporting application which is currently using a list (DHTML Menu with Sublist template) as the navigation means. The problem is that there is so much out there the navigation menus have become very large a

  • ITunes 7 - Just found a new bug

    Can somebody else please confirm if this is actually a new glitch, or if it is happening just with me? If you narrow down your search in iTunes Library or within any Playlist to 1 song only and then play this song, the song will stop at 0.1 sec from

  • How do I retrieve my notes back

    how do I retrieve my notes back pls