User interface language

Why, why, why!?... My computer (Mac) is set with the US Input Source and keyboard.
The OS - and everything else - is in English.
Most of BC is English but few details here and there appear in Spanish, like the blog posts dates or in the category drop-down menu (Web App) instead of "All Categories" it says "Todas las Categorias".
I live in Colombia and the time zone is set to Bogotà, Colombia. But I do not want any Spanish in the site.
Is there a way to change this configuration?
thank you very much

Thank you Alex,
yes I still have the issue and I will check your suggestion
best regards
Dario

Similar Messages

HT4208 App store user interface language

Recently, the user interface language of the App Store turned from German to Japanese. How can I set it back to German?

The iTunes and App store will usually only display the language of the country you made the subscription I can only down load from Japan iTunes and sometimes they do not have Apps or what ever but someties it depends on you language prefferences too ,it is quite annoying and confusing I use Finnish and English Swedish.
Apple is not altogether internatonal because of international agreements and local protectionism that is why there is no Finnish dictionary and spell checker
we are bound by the laws of the country we live in at the present and Apple and any other company does not want us to mixit up ,but they the internationalists Capitalists can do this like make Apple pruducts in China cheap labour.
yet it took years for Chinese to get Apple products ! Apple Japan is not very popular beause Japanese do not like the translations of Japanese by Nissei Japanese who live in the US!
Look at all the language preferences in Apple OSX they do nothing I use about 5 languages and find a total mix up my keyboard does not know what I am using better to have different computers install different language.

Problem installing Windows Server 2008 R2 Service Pack 1 Multilingual User Interface Language Packs

I downloaded Windows6.1-KB2483139-x64-en-US.exe but when I ran it on my Windows Server 2008 R2 SP1 (as Administrator) it does not run properly. I noticed it created a new cabinet file named "lp" briefly, then deleted it. Nothing else
appears on the screen.
My goal is to install Chinese display fonts on my server. Please help.

Hi,
First of all, if you want Chinese display language, you need to choose chinese in the drop down list on the download page. Here's a direct link in case you need it.
http://www.microsoft.com/en-us/download/details.aspx?id=2634(chinese simplified...)
Windows6.1-KB2483139-x64-zh-CN.exe is the file name for the Chinese simplified language pack.
1. The exefile extracts the file cabinet lp.cab which is the file you need to import the language pack.
2. Start lpksetup.exe and Point out the cab-file you just extracted.
If you want to do it with cmdline, you can do it with dism in an elevated command prompt as well:
Dism /online /Add-Package /PackagePath:C:\test\lp.cab
Note that you still need to create a policy or change default language in some way for your users.
Read more on the topic on:
http://technet.microsoft.com/en-us/library/dd744278(v=ws.10).aspx (adding)
http://social.technet.microsoft.com/Forums/windowsserver/en-US/7f019a90-8e48-4bc3-a9d2-e3c531354d04/how-to-use-group-policy-to-define-terminal-users-display-language-in-2008r2-terminal-servers (creating
gpo)
Microsoft Certified Trainer
MCSE: Desktop, Server, Private Cloud, Messaging
Blog: http://365lab.net

CS5 change user-interface language

A lot of PS-actions are written in english but I have PS in dutch. Is it possible to install a second interface language in CS5 or PS5.1 ?
The problem appears mostly in the given layer-name. For example; action Select "Layer 1 copy". PS can't find this layer because in dutch the layer automaticly named:"Laag 1 kopie".
So, I need only an english interface language to run actions. Is there a possibility to download this for CS5 ?

In the new versions (Creative Cloud) there is only one way. Reinstall application via CC app. So unistall application e.g. Illustrator, then go to Creative Cloud application and in the options panel > Apps you will find application language. It will be the OS language by default. Change it and install application from this tool once more.

Easy Doc Management can support chinese in user interface language?

Hi,SAP Experts.
When I login DMS by Easy Doc Mgmt I have inputted the ZH language,but after login,still don't display chinese menu.
My OS is WinXP Pro,chinese edition.
Anybody can tell me what cause it,how solve it?

Hi Leo,
As of now i think you wont find such fuctions available in standard DMS, for this you need to add some enhancements/developments which can be done through Abapers.
Thank You,
Manoj
Pl. reward if useful.

Language selection as part of User Interface Template

Hi all,
I'm looking for an alternative way of letting the user select language on portal pages. Instead of including the language selection portlet on all the pages, I wonder if I can implement language selection as links in the User Interface Template used by all the pages.
Has anyone done this?
Any ideas about how this could be done?
Thank you,
Oystein Hunnes

Where are your images being used in the UI template stored? I like to place my images in directory:
<portalMidTier>/apache/apache/htdocs/img
Then from within the UI template I can relatively reference the images as /img/logo.gif
Regards,
Candace

Does the iphone 3GS support arabic language for user interface?

hello everybody
i am looking for an answer to the following question:
does the iphone 3gs include arabic language setting for user interface?
thanks

The 3GS can be updated to iOS 6.1.2 and that iOS has Arabic as one of the keyboard languages but I do not see Arabic as one of the languages for userinterface but there are some I cant read so I cant be sure. You could check by going to settings/general/international then languages

A more successful experiment in creating compositable user interfaces for Config Dialogs

A couple weeks ago I posted an experiment in creating compositable user interfaces using transparent subpanels. The approach might best be described as, "It at least was notable for being novel."
Today, I'm posting another attempt, this one along more traditional lines, and far more successful. Particularly notable: this one can do all the arbitrary composition of the last one AND it solves the TAB order problem.
This solution uses a picture control and renders N copies of a control. When the user tabs to a control or moves the mouse over the control, a real control slides into that position to be able to catch the events (update mouse over draw state, highlight for keyboard focus, handle typing, etc). When the Value Change occurs, a master array of data is updated and the picture control is updated.
This is something that has been attempted in various forms in the past, but there are two aspects of this particular implementation that make it nice:
its programmatic interface for specifying the behavior of the various objects should make it fairly easy for a user of the framework to programmatically generate their dialogs
it handles the TAB problem without flickering, something I haven't seen in other attemps
This idea spawns out of conversation about the previous experiment -- thanks to those of you who posted on various forums, e-mailed me, or, in a couple cases, showed up at my desk. That last one is not something I'm encouraging unless you work at NI... just saying. :-)
Now, this experiement has already yeilded some interesting conversation. We note that as long as controls are instantiated independent of each other -- that is, no property of one control depends upon the property of another control -- this dialog system scales nicely. But in this experiment, I implemented Radio Buttons, which interact with each other -- when one is set True, the others go False. As soon as controls start interacting with each other (such as graying out one control when a checkbox is toggled, or having expandable sections, or really complex cases like updating a graph as some options change, like happens in some Express VI config dialogs) then we start needing ways to refer to the other controls. This rapidly moves us in one of two directions: naming controls or creating references. The naming approach is definitely my preference as it fits better with dataflow and I can do some interesting effects with breaking apart some of the tree. But all of this quickly starts sounding like "Please implement a XAML parser in LabVIEW." For those of you unfamiliar with XAML, in the world of UI design, it might very well be the coolest thing since sliced bread. A XAML string would indeed fit with dataflow, and we could start building that up. I hesitate to head down this road for two reasons. One, as many have noted, there's really not a good XML parsing library written in LabVIEW that can give me a useful DOM tree. Two, that's a huge project and my gut sense is that you'd have to complete a fairly large chunk of it before you'd start seeing any return on investment. But it is worth thinking about -- I might be wrong. Wouldn't be the first time. This code that I've posted today can at least get you started on the generation side if one of you decides to become industrious.
I'm turning my attention away from this project for now... coding in G is lots of fun, and I wish I could spend more days doing it, but this has been a side project and it's time to get back to my assigned projects in text programming. Building a powerful platform for automatic UI generation in LabVIEW would be really useful -- I see lots of requests for this sort of thing, and other languages are pulling ahead of us in this domain.
[UPDATE 5/17/2012 - There is an improved version.]
Solved!
Go to Solution.
Attachments:
ConfighThroughCtrlCreation.zip ‏558 KB

Elijah K wrote:
Thanks for posting this Aristos. I would normally be one of those to go bug you at your desk, but in case I'm not the only one with this question... which particular flickering problem are you referring to? The act of switching tabs? In all honesty, I've never noticed...
When you move controls around on the screen, normally you try to Defer Panel Updates while you do that. But Defer Panel Updates has an effect on control's abilities to catch certain mouse clicks, so when you're trying to move a control to catch the mouse, you have to work a lot without Defer Panel Updates, so if you're adjusting captions, etc, to match the new location, you can see flicker as properties adjust. You can move the control off-screen, as long as you have already updated the picture control to reflect the changes. It took a while to catch all the ways that the flickering can crop up. I think I got 'em all.
Attached are the VIs saved for LV 2009. Actually, they're saved for LV 8.6, but it doesn't work in 8.6 because of a bug in the picture control that existed back then.
Attachments:
ComposableUI_LV2009.zip ‏391 KB

How to display the updated data from db to user interface in sruts framewor

A beginner in this area, I have been able to read a record from a
MySQL database and populate in jsp form . Now, my goal is to
allow the user to edit the contents of the form and then update the
record in MySQL and then display the same in jsp. page
The scenario in detail
1)the data is fetched from db and displayed in non-editable format
2)Next button is clicked
3)Now in the same jsp page I view the same data from db in editable format
4)The user is allowed to change the information
5)Now update button is clicked
6)the records are updated in the db -Finished doing till this step
7)But the updated info in non - editable format to be displayed in jsp page is left pending.
Here is my code for jsp,i want know how to write an action for this,tried doing the same in java and I'm successful.but what I need is how to fetch the updated information in the user interface.
I've made both editable as well as non editable info in the same page with different actions.
pl help me,I'm a newbie
<%@ taglib uri="/WEB-INF/struts-bean" prefix="bean" %>
<%@ taglib uri="/WEB-INF/struts-html" prefix="html" %>
<%@ taglib uri="/WEB-INF/struts-logic" prefix="logic" %>
<%@ page language="java" %>
<%@ page import="java.util.ArrayList,java.util.Iterator" %>
<%@ page import="com.finocus.common.container.CustomerDetailsTest;" %>
<html:html>
<head>
 <title>CUSTOMER DISPLAY</title>
</head>
<body>
 <table width="100%" bgcolor="darkkhaki">
 <tr>
 <td><table width="100%" bgcolor="indigo">
 <tr>
 <td>Display</td>
 <td>Update</td>
 <td>Verify</td>
 <td>Confirm</td>
 </tr>
 </table>
 </td>
 </tr>
<%
 //Container for holding data
 ArrayList list = (ArrayList)session.getAttribute("CUSTOMERDETAILS");
 Iterator itr=list.iterator();
 while(itr.hasNext())
 CustomerDetailsTest cust = (CustomerDetailsTest) itr.next();
 System.out.println("testGetCustomerDetails()-successed. retrieved CustomerDetailsTest="+cust.toString());
%>
<%
 //Session for checking whether edit or non-edit mode
 String pageMode = (String)session.getAttribute("CUSTOMER_PAGE_MODE");
 session.removeAttribute("CUSTOMER_PAGE_MODE");
 if(null==pageMode)
 pageMode = "EDIT";
 if(pageMode.equals("EDIT"))
 //display data in the form
 System.out.println("Editable mode");
%>
 <html:form action="/nonedit">
 <tr>
 <td><table width="100%" bgcolor="darkkhaki">
 <tr>
 <td><bean:message key="label.id"/></td>
 <td><%=cust.getCusId()%></td>
 </tr> 
 <td>
 
 <bean:message key="label.Company"/>
 </td> 
 <tr>
 <td><bean:message key="label.cname"/></td>
 <td><html:text property="name" value="<%=cust.getCname()%>"/></td>
 <td><bean:message key="label.cphone"/></td>
 <td><html:text property="phone" value="<%=cust.getCphone()%>"/></td>
 </tr> 
 <tr>
 <td><bean:message key="label.caddr1"/></td>
 <td><html:text property="address1" value="<%=cust.getCaddress1()%>"/></td>
 <td><bean:message key="label.cemail"/></td>
 <td><html:text property="email" value="<%=cust.getCemail()%>"/></td>
 </tr> 
 <tr>
 <td><bean:message key="label.caddr2"/></td>
 <td><html:text property="address2" value="<%=cust.getCaddress2()%>"/></td>
 <td><bean:message key="label.cfax"/></td>
 <td><html:text property="fax" value="<%=cust.getCfax()%>"/></td>
 </tr> 
 <tr>
 <td><bean:message key="label.ccity"/></td>
 <td><html:text property="city" value="<%=cust.getCcity()%>"/></td>
 <td><bean:message key="label.czip"/></td>
 <td><html:text property="zip" value="<%=cust.getZip()%>"/></td>
 </tr> 
 <tr>
 <td><bean:message key="label.cstate"/></td>
 <td><html:text property="state" value="<%=cust.getCstate()%>"/></td>
 </tr> 
 <td>
 
 <bean:message key="label.Admin"/>
 </td> 
 <tr>
 <td><bean:message key="label.AAname"/></td>
 <td><html:text property="adminname" value="<%=cust.getAname()%>"/></td>
 </tr> 
 <tr>
 <td><bean:message key="label.AAemail"/></td>
 <td><html:text property="adminemail" value="<%=cust.getAemail()%>"/></td>
 </tr> 
 <tr>
 <td><bean:message key="label.AAphone"/></td>
 <td><html:text property="adminphone" value="<%=cust.getAphone()%>"/></td>
 </tr> 
 <td>
 
 <bean:message key="label.User"/>
 </td> 
 <tr>
 <td><bean:message key="label.AUname"/></td>
 <td><html:text property="adminusername" value="<%=cust.getUname()%>"/></td>
 </tr> 
 <tr>
 <td><bean:message key="label.AUemail"/></td>
 <td><html:text property="adminuseremail" value="<%=cust.getUemail()%>"/></td>
 </tr> 
 <tr align="center">
 <td><html:cancel value="Cancel"/>
 <html:submit value="Next"/></td>
 </tr>
 </html:form>
<%
 }else
 //display data in the text
 System.out.println("Non-Editable mode");
%>
 <html:form action="/edit">
 <tr>
 <td><table width="100%" bgcolor="darkkhaki">
 <tr>
 <td><bean:message key="label.id"/></td>
 <td><%=cust.getCusId()%></td>
 <td><bean:message key="label.status"/></td>
 <td><%=cust.getStatus() %></td>
 </tr> 
 <td>
 
 <bean:message key="label.Company"/>
 </td> 
 <tr>
 <td><bean:message key="label.cname"/></td>
 <td><%=cust.getCname()%></td>
 <td><bean:message key="label.cphone"/></td>
 <td><%=cust.getCphone()%></td>
 </tr> 
 <tr>
 <td><bean:message key="label.caddr1"/></td>
 <td><%=cust.getCaddress1()%></td>
 <td><bean:message key="label.cemail"/></td>
 <td><%=cust.getCemail()%></td>
 </tr> 
 <tr>
 <td><bean:message key="label.caddr2"/></td>
 <td><%=cust.getCaddress2()%></td>
 <td><bean:message key="label.cfax"/></td>
 <td><%=cust.getCfax()%></td>
 </tr> 
 <tr>
 <td><bean:message key="label.ccity"/></td>
 <td><%=cust.getCcity()%></td>
 <td><bean:message key="label.czip"/></td>
 <td><%=cust.getZip()%></td>
 </tr> 
 <tr>
 <td><bean:message key="label.cstate"/></td>
 <td><%=cust.getCstate()%></td>
 </tr> 
 <td>
 
 <bean:message key="label.Admin"/>
 </td> 
 <tr>
 <td><bean:message key="label.AAname"/></td>
 <td><%=cust.getAname()%></td>
 </tr> 
 <tr>
 <td><bean:message key="label.AAemail"/></td>
 <td><%=cust.getAemail()%></td>
 </tr> 
 <tr>
 <td><bean:message key="label.AAphone"/></td>
 <td><%=cust.getAphone()%></td>
 </tr> 
 <td>
 
 <bean:message key="label.User"/>
 </td> 
 <tr>
 <td><bean:message key="label.AUname"/></td>
 <td><%=cust.getUname()%></td>
 </tr> 
 <tr>
 <td><bean:message key="label.AUemail"/></td>
 <td><%=cust.getUemail()%></td>
 </tr> 
 <tr align="center">
 <td><html:submit value="Update"/></td>
 </tr>
 </html:form>
<%
%>
<%
%>
 </table>
 </td>
 </tr>
 </table>
</body>
</html:html>

u r using action classes. so after calling the insert method in Action Class to a dao... the next statement should be retrieve statement. so at the time of updating first it will get updated.. the next statement it will execute is retrieve and then set these details in VO or FORM and show it on JSP
Message was edited by:
leo_michael

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.
==============================================

Issue in the user interface of ICSS application

Hi Experts,
Please find the below description of the issue.
Ours is a migration project of ICSS application from one landscape to another landscape. Both the landscapes are in CRM 7.0 with the same patch levels.
For this migration we have copied the existing track A to the new track B and mapped to the new CRM 7.0 B system.
The XCM setting has maintained in the new B system exactly the same way like the A system
All the related backend code like FMs, Data Dictionary objects etc in CRM 7.0 A system has been moved to the CRM 7.0 B System.
   After this when we tried to run the application B, we are not seeing the same user interface like in application A.
   We are seeing only black font with white background. The color combination, fonts, styles etc like in application A are not visible in application B.
There are no CSS files in the XCM settings in A system. So I have also not maintained in B system.
We have not done any changes in the track. So we have not deployed the application.
I have created the projects for both the tracks A and B and compared the code manually. Everything is same.
Question:
   Please let me know what needs to be done additionally to get the same user interface.
   Is Shopadmin settings has to be maintained. Is this mandatory.
   Thanks in advance.
Thanks and Regards,
Raghu

Hello Waldemar,
Thank you for contacting National Instruments. I would like to apologize for the delay in responding to your support request. We have been on holiday for the past few days due to Thanksgiving.
From the information you have provided here, it sounds like you are on the right track with getting your application up and running with a chinese font interface. I would like to point out an extremely helpful KnowledgeBase that you might use for reference now and any other time you need to localize your user interface:
http://digital.ni.com/public.nsf/websearch/5987FCAFE3FBE8B98625693B0052EBD9?OpenDocument
(This KB was written for LabVIEW 6.0, but is still relevant for LabVIEW 7.0.) Based on this document, you only need "an MBCS-enabled operating s
ystem with an IME for the corresponding language." All 32-bit Windows operating systems are MBCS-enabled. Please see these links from the Microsoft website for more information:
http://search.microsoft.com/search/results.aspx?View=msdn&st=a&qu=mbcs&c=4&s=2
You may also find this tutorial describing localization procedures useful:
http://zone.ni.com/devzone/conceptd.nsf/2d17d611efb58b22862567a9006ffe76/6d94f90fc9b93aad862568a7007cd4c0?OpenDocument
I would recommend that you go ahead and install the Chinese fonts to your OS (if you have not already), and develop your user interface using the new font. This application should have no problem on any other machine with the Chinese font enabled.
I hope this helps! Let me know if there is anything else I can help with or clarify. Have a great day!
Liz Fausak
National Instruments

Coldfusion dev installer wont work - "installer user interface mode not supported..."

i just downloaded the os x version of coldfusion 7 mx
developer edition (for the thrid time making sure the download
wasn't corrupt) and extracted the zip and launched the installer by
double-clicking it. the install screen pops up where it lets you
choose what language and i press ok. almost instantly i get an
error message to pop up that says... "Installer user interface mode
not supported. Unable to load and to prepare the installer in GUI
mode."
umm... what?!
does anyone have any idea what's going on and why the
installer is misbehaving?! thanks!
: : michael

and the answer for others stuck on this...
the problems is an installanywhere bug where if the anything
in the directory path contains special characters like "!" or "#" ,
it causes problems with the install. in my case, the directory path
had a "!" in it... hope this helps someone else out!
: : michael

Unable to change user interface theme

hallo
I want to change the color of the user interface in adobe muse from light gray to dark gray.
on the adobe help page I've read that I must click "Edit" and then "Preferences" to open the "Preferences" window. there is then the first entry the possibility to change the color theme.
with my muse, however, lacks this selection option in the window, there is the choice of language appears as the first.
I use a windows pc 32bit and have Adobe Muse CC 2014

Hallo Brad,
thanks a lot for your answer ...
i checkt my Muse version, see screenshot:
After this, i uninstall my Muse and download Muse new time. take a look of this screenshot of creative cloud application:
i can make what ever i want ... my creative cloud application load the version "CC" not "CC2014" !
What can i do?
Is it possible, my membership subsription ist education/student & teacher ?
many greetings

Is it possible to have English as the interface language, but use (and develope for) any other language/locale?

Before installing Firefox, I need to clarify the following:
The use of locales: I am a developer and my preferable language, for the interface, is English (though, it is not my mother tongue). But, I would like to be able to use any other language (including, the use of any dictionary) and develop for any language or locale. So, does the English version let me do the above mentioned?
Or, eg, do I need to install the Hebrew locale, if I want to use the Hebrew dictionary?
Or, is it possible to install different locales on the same computer (and for the same user, in Win XP)?

You can install any dictionary is every locale, so that shouldn't be a problem if you use the English locale.
If you want to check out the user interface or how the browser acts with an RTL locale like Hebrew then you need to install the language pack and switch to that locale.
You can install additional language packs in any Firefox version.
* http://kb.mozillazine.org/Language_packs
* Locale Switcher: https://addons.mozilla.org/firefox/addon/locale-switcher/
* http://releases.mozilla.org/pub/mozilla.org/firefox/releases/latest/win32/xpi/

Pages User Interface

Does any one else find Pages (08) user interface a pain to use? I have used Word for a long time and am used to having most of the functions clearly displayed up front in the icon bar.
Pages hides functions under multiple menus in the Inspector menu. It took me hours to find the paragraph and line feed markings (the "invisibles"). Apple used the paragraph icon to represent two different things - the slide out styles drawer and the pull down menu - neither of which show the formatting marks. It took me another 1/2 hour to figure out how to "unindent" a paragraph (reset the style to free form).
It seems Apple tried to change the word processing language, icons, and placement of things just to be different from MS. Well, MS adopted them from WordPerfect and Apple should too, since they are standard.
I know Pages has a strong set of commands and is much more stable than Word, but I give them an F for the UI.

Cosman wrote:
Does any one else find Pages (08) user interface a pain to use? I have used Word for a long time and am used to having most of the functions clearly displayed up front in the icon bar.
Pages hides functions under multiple menus in the Inspector menu. It took me hours to find the paragraph and line feed markings (the "invisibles"). Apple used the paragraph icon to represent two different things - the slide out styles drawer and the pull down menu - neither of which show the formatting marks. It took me another 1/2 hour to figure out how to "unindent" a paragraph (reset the style to free form).
Would have been more useful to spend these hours reading the well done 'Pages User Guide' which describe these "burried" features.
But you are free to spent your time as you want
Yvan KOENIG (from FRANCE lundi 22 juin 2009 21:50:36)

User interface language

Similar Messages

Maybe you are looking for