Re: Explorer like user interface

Re: Explorer like user interface
You'll want to use the geometry management features in Forte.
These can be controlled using the WidthPolicy and HeightPolicy
attributes on FieldWidget (see p 160 of the Display Library manual).
You can set these in your code, or using the 'Size Policy' dialog
off the widget property sheet.
Do the following:
Create a Window class, get into the Window Workshop.
In the Window property sheet, set the Window Style to Resizable,
set Autosize Enabled.
Create your TreeView and ListView, group them into a GridField.
In the TreeView and ListView Property Sheets, under Size Policy,
set the Width Policy and the Height Policy to Parent for both
the ListView and TreeView. Also set a minimum size for each (in mils)
the minimum size will prevent you from getting too small a window.
For the GridField, also set the WidthPolicy and HeightPolicy to Parent.
You may also want top set the Column Weight to the ratio you want for
the sizing of the Tree and List, say 2:3.
Now the sizing will work. You'll just have to write the code
to get data in you TreeView and ListView. Looking at
the examples for outline field:
$FORTE_ROOT/install/examples/display/soutline.pex
is a good place to start, if you haven't done it before.
Good luck!
Thanks, -Mark
X-Originating-Ip: [40.33.1.12]
From: "Ramarao P" <[email protected]>
To: [email protected]
Subject: Explorer like user interface
Date: Fri, 19 Jun 1998 11:50:08 PDT
Sender: [email protected]
Reply-To: "Ramarao P" <[email protected]>
Hi,
I would like to design a window which is similar to Windows Explorer.
Treeview in the left side, listview in the right side. I should be
able to drag and expand the size of the treeview. How is this possible
in Forte? I tried to use STATE attribute of widgets, but did not
succeed. Could anyone suggest me how to go about it.
Thanks in advance,
Ramarao
International Business Corporation-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Just to complete, here is a little sample in R3.F.2.0 done with
Treeview and listView.
Be aware that to give the user the possibility to resize the left
part, you should manage it yourself. If you use an outlinefield
instead, you can put WidthPolicy to seleted and then use FS_ROUTE
state to enable the user to resize it. But this occurs a bug with the
resize of the window. If you try this with the treeview, it will
be converted to FS_SELECTONLY which is nonsense here.
Also, don't forget that ListView only does Ascending Sort (Microsoft
does Ascending and Descending). So you should need to manage sort
yourself too.
Hope this helps,
Daniel Nguyen
Freelance Forte Consultant
Mark Wallace wrote:
>
Re: Explorer like user interface
You'll want to use the geometry management features in Forte.
These can be controlled using the WidthPolicy and HeightPolicy
attributes on FieldWidget (see p 160 of the Display Library manual).
You can set these in your code, or using the 'Size Policy' dialog
off the widget property sheet.
Do the following:
Create a Window class, get into the Window Workshop.
In the Window property sheet, set the Window Style to Resizable,
set Autosize Enabled.
Create your TreeView and ListView, group them into a GridField.
In the TreeView and ListView Property Sheets, under Size Policy,
set the Width Policy and the Height Policy to Parent for both
the ListView and TreeView. Also set a minimum size for each (in mils)
the minimum size will prevent you from getting too small a window.
For the GridField, also set the WidthPolicy and HeightPolicy to Parent.
You may also want top set the Column Weight to the ratio you want for
the sizing of the Tree and List, say 2:3.
Now the sizing will work. You'll just have to write the code
to get data in you TreeView and ListView. Looking at
the examples for outline field:
$FORTE_ROOT/install/examples/display/soutline.pex
is a good place to start, if you haven't done it before.
Good luck!
Thanks, -Mark
X-Originating-Ip: [40.33.1.12]
From: "Ramarao P" <[email protected]>
To: [email protected]
Subject: Explorer like user interface
Date: Fri, 19 Jun 1998 11:50:08 PDT
Sender: [email protected]
Reply-To: "Ramarao P" <[email protected]>
Hi,
I would like to design a window which is similar to Windows Explorer.
Treeview in the left side, listview in the right side. I should be
able to drag and expand the size of the treeview. How is this possible
in Forte? I tried to use STATE attribute of widgets, but did not
succeed. Could anyone suggest me how to go about it.
Thanks in advance,
Ramarao
International Business Corporation-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Similar Messages

  • Explorer like user interface

    Hi,
    I would like to design a window which is similar to Windows Explorer.
    Treeview in the left side, listview in the right side. I should be
    able to drag and expand the size of the treeview. How is this possible
    in Forte? I tried to use STATE attribute of widgets, but did not
    succeed. Could anyone suggest me how to go about it.
    Thanks in advance,
    Ramarao
    International Business Corporation
    Get Your Private, Free Email at http://www.hotmail.com
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    Hi,
    I would like to design a window which is similar to Windows Explorer.
    Treeview in the left side, listview in the right side. I should be
    able to drag and expand the size of the treeview. How is this possible
    in Forte? I tried to use STATE attribute of widgets, but did not
    succeed. Could anyone suggest me how to go about it.
    Thanks in advance,
    Ramarao
    International Business Corporation
    Get Your Private, Free Email at http://www.hotmail.com
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

  • The new ribbon user interface in Win 8.1 should display appropriate buttons depending on the currently displayed folder within the explorer.exe window.

    To begin with, in file-explorer (.\system32\explorer.exe) normally, the new ribbon user interface in Win 8.1 does indeed display appropriate buttons depending on the currently displayed folder within the explorer.exe window. 
    But when one re-parents the explorer window handle to any window handle other than 0000 (desktop's window handle), then the UIRibbon fails to do so.
    You might ask 'Who does that ?' and I would say no-one usually, however I use BrightExplorer which
    is a great little app that  gives me a tabbed file-explorer experience.
    Now, this app works fine since Windows 7, but with Windows 8 the file explorer introduced the new UIRibbon in its UI. It's that new UIRibbon that gets confused by what I think may be be caused by the re-parenting that BrightExplorer does
    to pull a file explorer session into its tabbed control.
    This phenomenon relates to Windows 8 + and is observed only by doing the following steps:
    Download BrightExplorer from BrightNewWorlds.com by going here: BrightExplorer,
    In the address bar go to This PC,
    then go to any other folder and note that the UIRibbon is not keeping track of the changing folder selections.
    Does anyone out there feel that they can do something about this, or have advise?
    Kind regards,
    Robert van der Meijden

    To begin with, in file-explorer (.\system32\explorer.exe) normally, the new ribbon user interface in Win 8.1 does indeed display appropriate buttons depending on the currently displayed folder within the explorer.exe window. 
    But when one re-parents the explorer window handle to any window handle other than 0000 (desktop's window handle), then the UIRibbon fails to do so.
    You might ask 'Who does that ?' and I would say no-one usually, however I use BrightExplorer which
    is a great little app that  gives me a tabbed file-explorer experience.
    Now, this app works fine since Windows 7, but with Windows 8 the file explorer introduced the new UIRibbon in its UI. It's that new UIRibbon that gets confused by what I think may be be caused by the re-parenting that BrightExplorer does
    to pull a file explorer session into its tabbed control.
    This phenomenon relates to Windows 8 + and is observed only by doing the following steps:
    Download BrightExplorer from BrightNewWorlds.com by going here: BrightExplorer,
    In the address bar go to This PC,
    then go to any other folder and note that the UIRibbon is not keeping track of the changing folder selections.
    Does anyone out there feel that they can do something about this, or have advise?
    Kind regards,
    Robert van der Meijden

  • Photoshop CS6: Dark user interface style [UI skin] like Premiere Pro or Lightroom?

    For Photoshop CS6, how about add option to set a dark user interface style [UI skin]  like Premiere Pro or Lightroom?  It's very helpful to be able to work on images in a dark interface because it enhances our eyes' perception of color.  Can this be possible in CS6?

    Actually, there is some value in changing the background color.
    Contrast of the image with surrounding gray values does affect your perception of tone and saturation in the image.
    So you want to view the image with a surround that comes close to the value that the final result will be viewed in.
    For print, that means a 50% gray or lighter surround (mimicking the world).
    For video that means something darker but not really black.
    And for movies you want a nearly black surround.
    Unfortunately, OS controls/widgets aren't designed to do that.  Premiere and AE managed it by creating all their own controls and not using OS controls.

  • Just started using firefox seriously. my user interface does not look like the one in the 'tour'. please help

    i downloaded firefox a long time ago but havent used it extensively because i liked chrome. but recently chrome is just too difficult and if there is an issue i cant speak to anyone. so i am trying firefox. i went to take the user interface tour and there is suppose to be a button on the right hand side to help with bookmarks but my 'version' doesnt have that. was wondering how i get that and if i may have the wrong version.
    also....i cant seem to find where to turn autofill on and right now its not working except with the occasional email address.
    and one more thing....all streaming videos...tv, utube, art instruction..trailers...all get chunked up. nothing ever runs smoothly. and i am paying to get good download speed.
    i would appreciate any help on these three issues.
    thank you

    About the bookmark button:
    *[https://support.mozilla.org/en-US/kb/customize-firefox-controls-buttons-and-toolbars Customize toolbars]
    About versions of Firefox:
    *[http://www.mozilla.org/en-US/firefox/new/ Last Firefox Version]
    About the videos:
    Try disabling graphics hardware acceleration. Since this feature was added to Firefox, it has gradually improved, but there still are a few glitches.
    You might need to restart Firefox in order for this to take effect, so save all work first (e.g., mail you are composing, online documents you're editing, etc.).
    Then perform these steps:
    *Click the orange Firefox button at the top left, then select the "Options" button, or, if there is no Firefox button at the top, go to Tools > Options.
    *In the Firefox options window click the ''Advanced'' tab, then select "General".
    *In the settings list, you should find the ''Use hardware acceleration when available'' checkbox. Uncheck this checkbox.
    *Now, restart Firefox and see if the problems persist.
    Additionally, please check for updates for your graphics driver by following the steps mentioned in the following Knowledge base articles:
    * [[Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems]]
    * [[Upgrade your graphics drivers to use hardware acceleration and WebGL]]
    Did this fix your problems? Please report back to us!
    Thank you.

  • Import Pdf (No User Interface)

    Hi All,
    I need a script to import selected pdf in new document.
    I search forum, most of the scripts are done by using user interface or myDialog (i.e., MultiPageImporter2.5-CS5.jsx, PDF Multipage Import.jsx etc...)
    Selected pdf import in 1st page of Indesign files with x axis = 0; y axis = 0
    Trying script is:
    var myFile = File.openDialog("Select the PDF file you want to place","PDF Files (*.pdf):*.pdf");
    if(myFile == null)
        alert("Please select a PDF file and then try again.");
        exit();
    if(myFile != null)
        //Get the Number Of PdfPages.
        var pdfPages = getNumberOfPdfPages(myFile);
    alert(pdfPages)
    function getNumberOfPdfPages(pdfFile){
        pdfFile.resolve();
        pdfFile.open("r", "TEXT", "");
        oneLine = pdfFile.readln();
        while (oneLine.indexOf("/N ") < 0){
            oneLine = pdfFile.readln();
            slashN = oneLine.indexOf("/N ");
            nextSlash = oneLine.indexOf("/" , slashN+1);
            pdfP = oneLine.substring(slashN+3 , nextSlash);
        return(parseInt(pdfP));
    Thanks in advance
    BEGINNER

    Hi Georg Scholz,
    Thanks for posting here.
    the Server Explorer of Visual Studio 2012 supports connections to SQL Azure Databse servers. But you can also use the free
    SQL Server Express Management Studio 2008 R2 (or newer) to connect to SQL Azure or even use the designer in the SQL Server Management Portal.
    Edit:
    I see you would like to have a designer UI. as far as I know but Visual Studio 2012 does support this feature. If you don't want to switch to VS2012 you still can user the UI from the SQL Azure Management portal.
    Visual Studio 2012
    SQL Azure Management Portal
    Also check out the SSDT (SQL Server Data Tool) which shipped along with SQL Server 2012 and integrated with VS2012. It support GUI for SQL Server as well as SQL Azure.
    http://msdn.microsoft.com/en-us/data/tools.aspx
    http://blogs.shaunxu.me/archive/2012/04/28/ssdt-ndash-makes-sql-azure-development-easy.aspx
    Hope this helps you.
    Girish Prajwal

  • Why oh why was it fixed when it wasn't broken..the user interface

    This is a serious error on Apples part to alter the way this critical program operates
    its like taking away critical controls from an automobile...like the steering wheel
    Its that bad its at the level like Microsoft would have done.
    It may operate with all the same features...but where are they...not on the iTunes desktop
    where one could surf iTunes to look at, get, explore
    big mistake & an even bigger one not to listen to customers...
    Bruce L. Farrar

    Steve
    Sorry I just cant see how you can compare iTunes 10.7 &  iTunes 11 - yuo are in the minority  !!
    Everyone I speak to has the same view on this:
    That 11 hasnt the same user interface & controlability.For me this is fundamental in the way I used iTunes to "surf" what was available from what I already had.I find the way I have to go through things in a list poor to unusable. OK Apple may want to have the same interface accrooss the whole product platform - but why the capability of a Mac with a omplete keyboard & larger screen allows for more possibilities than say an iPhone which I reackong any user will realise & accept...basically the iTunes on mac platform has been dumbed down & is now far less capable
    The search "engine" that hasnt got fields to select to narrow down or focus a search is just riduculous & it doesnt work that well as whats comes back has to be searched through again.
    Using iTunes 10.7 & before was an "adventure" into music or material you knew & you found things you didnt know about & to do this was easy & enjoyable. Ifound previosly I could find a single track out there quickly & also explore.
    Whats happened is fundamentally bad - lets give a comparison - say if the whole user interface of the MacOS or write was altered, made significantly different...everyday tasks that you could do before had to be re learnt or just couldnt be done.
    Even Microsoft are carefull about making changes to the way things work & the way that a user interfaces with this...one carefull step at a time OK Microsoft "things" have to recieve this type of carefull scrutiny & adjustment - but Microsoft onthe whole take thier customers with them. Learning point that Apple have yet to realise & learn from
    Previous to this from Lion to Mountain Lion there was Frontrow a simple little program that gave a feature that me for one used (& enjoyed) regularly.....on the Mac doing something important...take a break, relax & enjoy some music...one press of the remote & you had all you music & videos there to be used...like a big iPod...really ver good. Finished relaxing or taking a break get back to work just where you left off, an impressive feature that was taken awy & replaced with NOTHING.
    So for me at least the usability & functionallity of the Apple experience has deteriorated...for no appreciable gain....for just a commonality of controls accross the products.
    Its called "change for changes sake" & in this case the customers werent consulted they were totally ignored in being left with something that is retrograde.
    The very fact that I am here with others making comment is proof postive that the situation is a definate backwards step. I just hope that for Apple its a "blip" i.e. an error that will realised & corrected...
    I have been using Apple products from 1989...I am not a Microsoft refugeee or reluctant convert who is throwing mud..just the opposite in my family we have:
    4 Macbook Pros,
    an iMac,
    4 iPods,
    4 iPhones
    Apple TV
    all backed up ona time capsule.
    We have lived through the bad times & good...I realise that Steve Jobs cant come back...but I am sure he would have listed & then gone back to the teams & forced the change backs through.

  • Error while creating a callable object - User Interface

    Hello,
    When i'm trying to create a callable object - User Interface in the guided procedure design time. i'm getting an error. An internal server error. This is happening while i'm trying to create a guided procedure with webdynpro's.
    Is there any body who allready had somthing like this.
    Greetings
    Kurt

    Hi Raja Akella,
    I allready had the roles and my portal version is upgraded until SP8 and all the possible patches.
    I get an internal server error when i want to create a callable object. specially when i want to create a webdynpro ( ABAP / JAVA).
    In the visual administrator i get the following  errors.
    <b>Error 1</b>
    Exception occured during processing of a Web Dynpro application: "com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.".
    [EXCEPTION]
    com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
         at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
         at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
         at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
         at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
         at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
         at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
         at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
         at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
         at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
         ... 39 more
    Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
         ... 52 more
    Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
         at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
         at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
         at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
         at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
         ... 53 more
    <b>error 2</b>
    Processing HTTP request to servlet [dispatcher] finished with error. The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
         at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
         at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
         at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
         at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
         at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
         at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
         at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
         at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
         at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
         ... 39 more
    Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
         ... 52 more
    Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
         at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
         at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
         at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
         at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
         ... 53 more
    <b>error 3</b>
    Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
    Exception id: [00505691431B006F0000003E00000FE800041B45B87F7617]
    thanks in advance
    Kurt

  • User Interface Template for Interactive Report Region

    In 3.2, where do we set the user interface template for Interactive Reports region?
    No matter what out of the box theme I switch to, the Interactive Reports region shows the same. What and where do I change the template so that alternating rows use two different colors?

    There is no template for Interactive Reports like for a "normal" report. You need to modify the CSS and supply your own for this to happen.
    I believe most things are tagged with #apexir - firebug with Firebox is invaluable. This thread may help:
    Re: changing the look and feel of interactive report.

  • Unable to load the user interface-please reinstall the application-Audigy 2 zs Platinum

    unable to load the user interface-please reinstall the application---this is the message I get when my pc starts------Someone messing around with my computer tried to delete creative media source player 3 when they saw I had both 3 and 5 in folder and i get this error message every time I start my pc. In addition to this I have lost my EAX and THX consoles and my speaker settings are gone so I cannot adjust my 5. system at all. After I delete that error message when I click on the creative icon is sys tray instead of opening up the creative media player I get the error message--unable to load needed componants. Please reinstall the application. this is media player 3[version 3.32.]. I dont know why during the auto?updates through the last couple of years I have media player 3 in sys tray and if I need version 5 it is in file with 3--start-all programs-creative--any way my pc is a Cyberpower AMD FX-53 using win xp pro-32 bit-- and of course its a OEM product so they tell me the only way to get it to work is use the restoration cd they gave me when I bought the pc and it will revert back to its original state as when purchased. I would lose all my games, music, pictures?ect and would have to start from scratch.[ OR of course back everything up on a portable hard dri've]?It seems like there should be an easier way --hell I might as well buy a new soundcard and it would make it easier. If anyone?has an answer for someone who is not a tech head so I can understand please help !!--thank you in advance for any assistance as it is greatly appreciated. Sorry this message is so long winded, just irritating to have spen so much for a pc and not have the original installation disc.-tried moving to another slot and the fixes I saw posted here with no luck---thank you folks again--Tom

    All the issues you guys are talking about have been reported in beta stage of these new drivers. I would say none of them has been fixed yet. The only solution for now is to use previous drivers which work fine or use some modified drivers which fixes some issues, but not all. Your choice.
    [url="http://connect.creativelabs.com/windows/Lists/Audigy%20Issues/AllItems.aspx">Bug List[/url]
    Message Edited by ronon0 on 08-07-2008 :47 AM

  • After Effects not starting at all, stops at "initializing user interface"

    I installed CS5 master collection trial version on W7 64 bit machine.
    After Effects  doesn't load at all (it stops at "initializing user interface") and it's  even impossible to kill the  process in windows (never had this problem with any app). I can shut down all  the other processes, like dynamiclinkmanager.exe  or Adobe QT32  Server.exe, but aftereffects.exe  just won't stop and I need to restart my PC.
    Also  Premier crashes after I click 'new project', or try to open something,  but the application starts and I do see the whole GUI.
    I updated Quicktime, as well as my video card  drivers. All  other apps in the master collection seem to work fine. Uninstalled the  whole thing twice (with the remove preferences option), cleaned the registry with a comodo system clean up utility,  reinstalled also twice- nothing. Tried with the firewall turned off and  quick time completly uninstalled - nothing changed.

    can you rename or delete "C:\Users\xxxxx\AppData\Roaming\Adobe\After Effects\10.0"
    can you rename or delete for max 11
    "C:\Users\xxxxx\AppData\Local\Autodesk\3dsmax\2011 - 64bit\enu"

  • One user interface for multiple VIs

    I searched and searched for an answer to this so if it's out there please direct me to it.
    I have an application that has roughly 10 different VIs.  These VIs are virtually the same.  All they are doing is monitoring data for the operator for instance: Temperatures, Pressures, Vibrations, etc.,.  I would like to implement a user interface where the operator could click on a button at the bottom of the screen that would take them to the temperature screen.  Once the temperature screen is displayed, I would like to be able to click on a different button that goes to the Pressure screen.  In other words, I want the operator to be able to access any screen they want from any screen they are currently viewing.  So all the buttons would be at the bottom of every screen.  And any screen would be able to access any other screen.  I just have not found a good way to do this.  Every thing I've tried always ends up coming back to a "main.vi".  
    Multiple answers are welcome!  Thanks.  

    Ben wrote:
    DSC has a feature that lets you assign protection levels to each FP control.
    Good to know, having never used DSC. Maybe something to add to my "toolbox" in the future.
    CLA, LabVIEW Versions 2010-2013

  • 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 add a new Field to the WEB User Interface in CRM 2007

    Dear experts,
    I have been struggling to add a new field to the (CRM 2007) user interface from available fields for a specific view.
    I have maintained settings in BS__WD_CMPWBàRuntime Repository editoràComponentàViewàConfigurationàNew ConfigurationàAvailable FieldsàField Propertiesàand save.
    But the field is only appearing in display mode in the Web UI, which doesnu2019t allows any user input.
    I need your help to resolve the issue, I would be grateful if you could provide step-by-step documentation with screenshots or any other kind of documentation.
    Each suggestion will be appreciated.
    Best regards,
    Raghu ram.

    Hi Raghu Ram,
    I think you added a new custom field using some method like EEWB etc.,
    Then, you are adding the field onto the UI using UI Configuration Tool .. right ?
    These are the steps to diagnose:
    Method 1.Check the field properties in the model browser first.
      It should be showing 'C' i.e., CHANGEABLE. If it is showing as 'R', it is only READABLE.
      In such a case you need to find a BADI to change the field properties.
      For example, in Marketing Applications OBJ BADI has a method CHANGE FIELD PROPERTIES for this purpose.
    Method 2. Debug and check what is the value coming for RV_DISABLED parameter in the GET_I method in BSP_WD_CMPWB. This should be FALSE.
    Method 3. Check what are the field properties in the UI Configuration tool.
    Make sure it is not a display only field.
    Regards,
    Masood Imrani S.

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

Maybe you are looking for

  • Sharing iPhoto library over network between two Macs

    I would like to edit/create albums via sharing. I can easily share photos between my two Macs via sharing, but I can't move photos between albums, can't create new albums, etc. (I would like to be able to use my laptop in our home network to modify t

  • Failure to install Windows XP Mode under Win7

    After (apparently successful) installation of 500-megabyte "Windows XP Mode," installation of 10-megabyte "Windows Virtual PC," after reboot, reports "Failure configuring Windows updates / Reverting changes." Event viewer shows "Package KB958559 fail

  • Error in ARE 1 Output- Excise Exempt

    Hi Experts, after carrying out the transaction code J1IA101 for the excise exempt invoice. We are not getting any value in the value column. The excise duty percentage is also not coming. There are no remarks printed although the same is maintained i

  • How to know on which time dimension level we are ?

    Hello, I would like to know is there a variable or a mean to know dynamically on which time dimension level we are in order to use that in a CASE WHEN clause ? By using a sort of aggregation tables in which one of the column contains the name of the

  • Displaying HTML code/document within a SIEBEL applet

    Dear All, I have a new requirement which is to integrate an external html document/code within a Siebel's applet in my Home Screen/View. This HTML code is DYNAMIC and it will change depending the user connected. It will give general informations. I t