Muse CC User Interface Theme läßt sich nicht auswählen

Hallo,
ich habe bei Adobe TV gesehen das man Muse CC auch mit einem dunklen User-Interface nutzen kann.
So habe ich es ja auch bei Photoshop CC oder InDesign CC ...
Habe auf eine Hilfe website gelesen, dass ich das auswählen kann unter "Bearbeiten" dann "Voreinstellungen".
In diesem Fenster ist laut der Anleitung eine Auswahl zu sehen, wo ich aus verschiedenen Themes (Grautönen) wählen kann.
Das ganze ist der 1. Eintrag in diesem Fenster, dann folgt der Eintrag "Sprache Einstellen".
Mein Problem ist:
In diesem Fenster fehlt diese Auswahlmöglichkeit komplett, bei mir ist der 1. Eintrag das mit der Sprache ...
Ich habe nachgesehen das ich auch wirklich die Version "CC" nutze, und in der Creative Clous Anwendung ist Muse auch als Aktuell eingestuft.
Habe ein 32-Bit System mit Win 8.1 Update 1
Gruß Peter

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

Similar Messages

  • Index in erweiterter Suche läßt sich nicht auswählen

    stattdessen erscheint die Auswahl:
    "derzeit ausgewählte Indexe" (Grrr, was für eine Pluralbildung).
    Ich kann also nicht auf den erstellten Index in der erweiterten Suche zugreifen. Adobe acrobat x pro, Version 10.1.0
    Weiß jemand wie ich jetzt im Index trotzdem suchen kann oder wie der Fehler behoben werden kann? Ich habe schon die Funktion "Acrobat-Installation reparieren" erfolglos angewandt.
    Herzlichen Dank im voraus
    A.J.

    Hallo A.J.,
    hast Du die Indiz(c)es (übrigens Indexe ist erlaubt)auf diese Art und Weise erstellt:
    http://help.adobe.com/de_DE/acrobat/pro/using/WSC28D4DBB-6A78-4027-9E04-F50FE411CFB9.w.htm l
    und sie versucht so auszuwählen:
    http://help.adobe.com/de_DE/acrobat/pro/using/WS58a04a822e3e50102bd615109794195ff-7c3d.w.h tml?
    Hans-Günter

  • InDesign CS3, Objekte lassen sich nicht auswählen

    Hallo,
    ich habe ein Problem mit einem frisch in InDesign CS3 5.0.4 (Windows Vista) erstelltem Dokument. Ich kann plötzlich kein einziges Objekt auswählen. Als ob etwa alle gesperrt werden, was aber nicht der Fall ist. Auch alle Ebenen sind frei für die Bearbeitung gegeben.
    Ich kann aber neue Objekte platzieren/erstellen. Nach abspeichern, beenden und wider öffnen ist nur das neue Objekt editierbar.
    In dem Dokument sind Textrahmen, platzierte Fotos sowie zwei Indesign CS3 Dokumente die um 90 Grad gedreht sind.
    Woran es liegen kann?
    Vielen Dank

    Hallo Christoph,
    vielen Dank für die Antwort.
    Aber die Meldung zum resetten ist gekommen?
    Dochdoch, InDesign ist zurückgesetzt worden.
    Mal sehen. Sollte das Problem wieder einmal auftreten, kann ich ja das eine oder andere unter dem von Dir angegebenen Link ausprobieren.
    ...und ansonsten gibt es ja das BackUp (was mich in diesem Falle ein weiteres mal vor Stress bewahrt hat).
    Cheers
    Joe(chim)

  • 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

  • Colorsync lässt sich nicht abwählen

    Guten Morgen!
    Ich habe gestern versucht aus Lightroom 5 mit dem Epson 3000 fineart Papier von Hahnemühle mit eigenem Profil zu drucken. Nur, leider konnte ich unter "Druckeinstellungen..." nicht colorsync abwählen. Was kann ich tun? Über Google bin ich nicht fündig geworden.
    Vielen Dank für eure Hilfe!

    bei mir ist das auch so

  • Muse 2014.3 update has an over-sized user interface.

    The Adobe UI Scaling bug has reared its head again, this time with Muse (like with previous versions of PS, AI and ID before it).  See screen grab that makes my 22" HD look like an old 12" monitor (see pasted at half resolution below).
    I don't see anyone else with this issue posting, but I'm sure it's just a matter of time. Any suggestions? Do I have to go back to the Windows Environment settings again? I set it to =1 to fix one of the other applications a while back.

    Sounds like your Win machine is set to run at 125% scaling (or thereabouts), is that right? Or do you have multiple monitors with different native resolutions, and the "one resolution to rule them all" setting engaged?
    Previous versions of Muse would ignore the 125% scale factor and run at 100%.
    The new release of Muse (2014.3) also does not support running at 125%, but can run at 150% and 200% scale factors. Muse 2014.3 chooses to run at 150% in this case. For many people with vision impairment or eye strain issues 150% is a better choice than staying at 100%, but we understand it may not be best for everyone. At 150% the cursors will be oversized as you describe (using 2x cursor artwork), but everything else will be drawn crisply at 150% scale.
    In the short term, we can add support for an environment variable override similar to what InDesign and Illustrator used (see Application user interface too large | Windows). Would that address the problem for you?
    One question, would it be better for you if Muse, InDesign and Illustrator all obeyed the same environment variable override, or would it be better if Muse used a different one? Now that ID and AI have exposed a user preference setting for UI Scaling (see InDesign's below), it might be better if Muse used a different environment variable so as not to override the user preference in AI and ID.
    We will aim to add a similar Win-only user preference for the next release of Muse.
    DaveB

  • Acrobat DC User Interface: Way to Change Theme? (Too Bright)

    Just installed Acrobat Pro DC -- an first thing I notice compared to my typical darker themes (Windows, Office, and even previous Adobe product versions) is that the user interface is extremely bright. It's like surfing bright webpages, and hard on the eyes.
    Is there any way to darken the UI (Themes, etc.) ?

    I have to add my name to this series of complaints...
    The new design is appalling. As others have said, it is way too bright with no contrast between documents and interface and no way to skin the UI the way you would like to. Not only that but it fails to remember where you last stored docs, instead featuring an annoying pop up asking me what I want to do next. Coming from the top design software suppliers in the world ( I thought ), you wonder why the team that designed this was not forced to lie on the floor while the rest of the Adobe designers laughed at them.
    Seriously, was this designed for a 10 year old occasional user? Take that back a 10 year old would have moved on....
    And that ghastly menu which takes up all that space with no contrast. And I know my name, you dont have to include it on the top right.
    I really thought XI was a great tool and nice to use. This is a real step back.
    Please give us some or all of the following:
    A customisable interface
    An option to choose an "old-style" Adobe Acrobat XI option if we prefer
    The ability to remove annoying features in a proper preferences setting (such as my name - did I mention, I know who I am)
    The ability to alter contrast
    Advanced settings
    etc etc - Everything anyone has said above
    And please - if anyone at Adobe actually listens, do NOT take this design and transfer it to your other software.

  • I do not see the user interface for the Logic software instruments. I can hear them play through my midi keyboard but I cannot see them to adjust parameters. Please advise.

    I do not see the user interface for the Logic Pro software instruments. I can hear them play through my midi keyboard but cannot see them to adjust the parameters. Please advise.

    Couple of things - you can open the interface for any instrument or plug-in by double-clicking its insert slot on the channel strip. You can configure Logic to automatically open the interface for a plug-in when you first instantiate it in the preferences. Go to Logic Pro > Preferences > Display > Mixer, and check the box for "Open plug-in window on insertion".

  • 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

  • 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

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

  • What is the best way to get data to a user interface?

    Hi,
    I'm using labview 6i. I have an application with a handful of "core" vi's that actually run my application, doing the data acquisition, analysis, and control. I am currently using these same vi's for my user interface. I also have a number of vi's that contain menu's for configuring the "core" vi's. My questions is, what is the best way to seperate the "core" vi's from the user interface vi's. Global's, data socket, control references, others?
    Thanks for the help.

    Hi Sal,
    I have been a strong advocate of control refnums ever since LV 6i hit the streets. I recomend you look into using them to provide this conectivity.
    You could accomplish this by using a variation on the following.
    In your UI, create refnums for each of the controls or indicators that must be monitored or updated. Pass the appropriate refnums to each of the "core.i's" at program init time. Inside each of the core.vi's, use property nodes to read the control's values when appropriate and similarly for display purposes. (Note: Not all boolean mechanical actions are compatible with this technique. In those case you will have to explicitly write false values after find the control to be true or vise versa).
    By using this technique, you can keep the UI diagrams clea
    n. Depending on your app. the UI diagram could consist of the init's I mentioned above, and a while loop that watches if it's time to exit.
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

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

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

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

  • Dynamic user interfaces

    Hello,
    here's a little teaser for user interface experts out there:
    I wonder what kind of techniques ABAP offers for creating dynamic user interfaces.
    When talking of 'dynamic' I imagine something like an arbitrary number of 'containers' where other programs (classes f.ex.) can draw their own user interface into.
    In Java this could be realized with the container concept in swing.
    I have done some research on this topic and the results are so far:
    a plain dynpro: seems to have no dynamic at all -> not an option
    a plain dynpro with a tabstrip: in case the number of tabs CAN be set at runtime AND the subscreens CAN be drawn from inside separate classes -> a definite option otherwise not an option
    any kind of web-frontend (BSP, JSP etc.): web-frontends are not allowed by company restrictions -> not an option
    dynamic documents: I could not find many information on these yet (also not on sdn). In case that an arbitrary number of parts of the dynamic document can be created from inside separate classes -> an option otherwise not an option
    I will be happy about any further information on this topic.
    Best regards,
    Patrick Baer

    I spent some time today doing research on BSP's and built a "BSP-Viewer" embedded into the SAP-GUI. Though I like the concept of BSP's a lot (like I did already with JSP's) but company restricitions are too strict. So BSP's are out of the play.
    After the discussion I started to play around with the different containers and basically I'm quite pleased with them and the "cl_gui_container_bar" allows an arbirtary number of "subscreens" which matches my requirements.
    But as usual there's still a downside:
    I found no option to built text labels and text fields into a container. Unless this is possible I can't give this approach a chance. I already found some postings which seemed to confirm that this is in fact not possible but I can't really believe it. At least from what it looks like it seems to me that the object navigator utilizes both: splitters, containers and all the stuff AS WELL AS the "classical" elements like text boxes, labels and so on.
    Any ideas on how to combine the container concept with text fields, labels maybe whole dynpros or subscreens ?
    Best regards,
    Patrick Baer

Maybe you are looking for