User interface documentation

I am looking for some user documentation for iTunes (Mac) that is more comprehensive than the Apple tutorials. In particular, the user interface isn't always intuitive, and I keep coming across things that take a while to figure out.
For example, I am trying to put the movements of a classical work in order in the main window so that they will play in the right order; in spite of numbering the tracks in the Info window, it still doesn't happen, and I can't find a way to do this.
A previous discussion
https://discussions.apple.com/message/7234401#7234401
(now archived) gave a reference to an article
http://docs.info.apple.com/article.html?artnum=93078
which is now not available.
Does anybody know of anything current which could help?
Thanks.

I find the iTunes Help accessed from the iTunes > Help menu to be really useful. You can browse the contents, or use the search bar at the top right to go right to what you want. For example, I searched for Edit song and CD information and found this:
To edit song or CD information:
Select the song or CD you want to edit, and choose File > Get Info (or press Command-I).
Click Info and make your changes.
Tip: If you’re changing the same information for multiple items (genre, for example), you can select all the items and change the information for all of them at the same time
Here are other ways to customize song and CD info:
You can edit information in the Info window to make it easier to find and sort items in your library. For example, you can:
Group individual movements on a classical CD into one work by indicating the movement (for example, “Piano concerto in A Minor, Op. 54”) in the Grouping field.
Group songs that are part of a compilation together in your library by clicking the Info button and selecting the “Part of a compilation” checkbox.
Identify the individual artists on a tribute album in the Artist field, and type “various” in the Album Artist field.
Create your own genre category by choosing Custom from the Genre pop-up menu.
Change the order in which tracks on a CD play by changing the numbers in the Track Number fields.
Try it. You'll find a lot of good tips.
There is also an excellent archive of 3rd party tutorials here: http://www.ilounge.com/index.php/articles/archives/tutorials

Similar Messages

Documentation Parameters for the AWT User Interface M I 7.1 NOT working?

Hi:
I found this doc: http://help.sap.com/saphelp_nwmobile71/helpdata/en/47/8baf5f1240444ba39d0bca8704003f/frameset.htm
(see "Parameters for Mobile Client for Handhelds" ---> "Parameters for the AWT User Interface" )
the parameters are persist OK in the client´s BD but it seems not to affect the layout......
Any idea?
Thanks a lot for your time on this post.
Rocío.

I don´t required any more.

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.

Error while deploying IDM 7.1 user interface file on Netweaver Java AS sys

Hi,
I am in process of installing IDM 7.1 in my landscape. I have done IC, RC in one system with windows 2003 + oracle. On other system I have Netweaver 7.0 SP14 Java AS system. I have configured as per SAP documentation.
While deploying IDM user interface 7.1 on SAP Netweaver Java system 7.0, I get following error in SDM:
Loading archive 'E:\software\IDM\DATA_UNITS\IC_UIS_710\IDMIC00_0.sca'
May 11, 2011 5:16:12 PM Error: Unresolved dependencies found for the following SDAs:
1.: development component 'tc/idm/wd/model'/'sap.com'/'MAIN_IDM710_C'/'3542284'/'0'
dependency:
name:     'tc/ddic/runtime/facade'
vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name:     'tc/wd/api'
vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name:     'engine.j2ee14.facade'
vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name:     'tc/bl/logging/api'
vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name:     'tc/wd/legacy'
vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name:     'tc/bl/exception/lib'
vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name:     'tc/aii/base/offline/facade'
vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name:     'tc/bl/jrfc/api'
vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
Deployment will be aborted.
May 12, 2011 11:04:09... Info: Loading archive 'E:\software\IDM\DATA_UNITS\IC_UIS_700\IDMIC00_0.sca'
Please advise,
Thanks,
Digesh

Hi,
SMP : http://service.sap.com/swdc -> SAP NetWeaver and complementary products" SAP NW IDENTITY MANAGEMENT" SAP NW IDENTITY MANAGEMENT 7.1
You would need to deploy the NW IDM IC 7.10 UIS FOR NW 7.00 component.
Regards,
Srikishan

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

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

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

How to get the user interface in english ?

Hello
I have installed SQLdevelopper 1.5.5. The user interface is in french (probably because my PC is in french). I would like to switch in English; How to do ?
Thank you !
Christian

-K- (!),
I followed your suggestions and it works well now. Do you know why I prefer to see the UI in english ? Because the help and everything else (documentation) is in english making very difficult to find in the french UI what is referred to in the english on-line help.
Merci de votre aide !
Christian

How to get to learn using TestStand User Interfaces

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

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

Labwindows/CVI 7.1 Remote user Interface using Enterprise Connectivity Toolkit

I have an application programmed in Labwindows/CVI 7.1 controlling an Electromagnetic Instrument.
Now am interested in extending its usability by adding remote user interface.The goal is to have the application available to be accessed
to remote users through website,with multiple users viewing it but one user controlling the instrument remotely at any given point.
Since the possible methods would be 1.ActiveX 2.TCP/IP 3.DLL
Which is the best technique to implement this with out having to manipulate much of my code also do we have any documentation available ?
Thank you
Solved!
Go to Solution.

Hi Mutha,
This functionality was a part of the orignal Internet Toolkit for CVI. However, the web server part of this was removed and isn't included in the Enterprise Connectivity Toolkit. You might consider using LabVIEW with the Remote Front Panel feature.
Cheers,

Flex User Interfaces

I'm new to Flex. I've seen some great apps with great user
interfaces done in it. I have this question:
Is there ANYWHERE that helps one think about appropriately
laying out the Flex user interface? A book, a PDF, a style guide,
etc.? This would include, particularly, when to use container type
X vs container type Y, etc. Even a description of the best use of
all the containers and controls would be useful.

Katie, I see what you mean, something in this vein but for
Flex:
Apple Human Interface Styleguide
http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuidelines/OSXHIGu idelines.pdf
Let's ask guys at Adobe and Adobe Consulting to write such a
document.

User Interfaces: Is the ain~ui~mobile Package in AII 2.1 still available?

Hello!
During my studies on the outbound scenario script, I found out that there must exist an ainuimobile WebDynPro application for tagging and packing via mobile reader.
This application is mentioned nowhere in the documentation. Just the obviously older process script uses a link to this application. I didn't found an entry for ainuimobile in the Web Dynpro Content Administrator screen. There is just the ainsodesktop package available. When I try the /MobileReaderApplication on the ainuimobile package, I get a lot of errors. Even when I try the /MobileReaderApplication on the ainsodesktop package, I get errors.
My question is: Is the ainuimobile package or something similar in AII 2.1 available? Has it been removed from 2.0 to 2.1? If this ships with AII 2.1, why isn't it installed with the standard installation?
Thanks in advance,
Johannes

Hi Haakon,
single component export/import is only supported for application which are identical on the source and target system. It relies on the fact that other referenced components (for example user interface, templates, ...) use the same IDs on body systems.
Because of the APEX 4.2 upgrade, that's not the case anymore. As part of the upgrade, several new components had to be created on the fly which do now have different IDs on dev and prod. That's why the single component export/import doesn't work anymore.
If the single component export/import is used to patch applications, it's recommended to do a full export of the app on dev and import it into prod after upgrading to a newer version of APEX to make sure that body systems are using the same component IDs. After that your single component deployment should work as before.
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Introduction of User Interfaces in SAP CRM

Can someone tell the progression on how the SAP CRM User interfaces (UI) were launched? for example, which CRM versions supported which UIs (PCUI, WEBUI etc)
Thanks
or else, is there a documentation that provides differences and commonalities between CRM UIs

Hi,
concerning CRM User Interfaces it is very simple:
1. WebClient UI: is the only supported User Interface for Users since CRM 5.1 and this is also the way forward from SAP point-of-view. SAP keeps investing in improving the WebClient UI for CRM in the coming releases.
2. SAP GUI: is only used for Adminstrative tasks, customizing and developments in CRM.
3. PCUI: is no longer supported since CRM 5.1
Kind regards,
Carl

When i add menu bar in my user interface gives me error that this handle is not a panel handle(return value -42)

i have 3 panels in my application and parent panel is displayed first then i display other two panels which come to the front then on entering correct password i discard the child panel and then you can see parent panel , but there is an issue when i add menu to my parent panel i dont know whats wrong when i add menu bar in my user interface (parent panel) gives me error that this handle is not a panel handle(return value -42) for a child panel. when i dont open and display child panel then its fine , and even without menu added to my parent panel all my panels and my application works perfactly

Hello smartprogrammer,
some more informations are needed in order to properlu help you in this situation:
- Are you adding menus dynamically at runtime or in the UIR editor? If dynamically: how are you loading the menu bar?
- Are you dynamically tailoring the menu bar at runtime (adding or deleting menu items, dimming / undimming some of them or checking / unchecking)?
- Can you post the code where you are getting the error, documenting variables and scope (local to the function, global to the source file, global to the project)?
You can look at uirview.prj example that ships with CVI for an example of LoadMenuBar (the exampl eis in <CVI samples>\userint folder): in that project, the menu bar is shown as a context menu when you right-click on a tree element (see DeferredMenuCB callback).

Generate Interface Documentation

Hello all,
could you tell me where i can find information regarding with SAP PI Interface Documentation. How can i generate reports of created objects, interfaces, scenarios if i have documented them in IR and ID? Is there any guide i can use to document my interfaces? Can this documentation be published as a HTML resource?
Thank you in advance.

Are you talking about the technical + functional document that we prepare for an interface developed in SAP XI/ PI? If yes, then have a look at this section:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/86bdc490-0201-0010-b9a2-b98373ea4dc4
Normally such documents are hosted in a server which has a user interface....this user interface has a link which refers to the actual document.....a search kind of functionality.
May be a search on SDN can help you further.
Regards,
Abhishek.

Improve ControlExecFlow user subproperty documentation

The TestStand documentation describes the ControlExecFlow user subproperty as follows:
"User can control the flow of execution by setting breakpoints, single-stepping, and using the Set Next Step command. User can use the Run Mode command in a user interface. User can use the Run Mode command in the TestStand Sequence Editor but only if the EditSequenceFiles subproperty is also True."
This description should be amended to include the fact that the value of this subproperty also enables or disables options in run-time error dialogs (Retry, Ignore, Abort, and Break). TestStand users will see run-time error dialogs with different options based on the value of this subproperty.
NOTE: The ControlExecFlow user subproperty description can be found in the online help under NI TestStand Environment Reference Help>>TestStand Sequence Editor Menus, Panes, and Windows>>Windows>>User Manager Window>>User and Group Privileges.

We have two different types of support offerings for NetBeans and until recently, both included 'Standard Subscription' in their title and hence the possible miscommunication. One is for developer support in using the tool and the other is for production support.
I checked the queue for the developer support offering but did not find a match with your user name....please advise how your service request was submitted.

Sybase Unwired Platform - User Interface Validations

Hi,
Does the Sybase Unwired Platform have a mechanism that enables the developer to integrate User Interface Validations?
Apple provides a standard way to validate user interfact items: http://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/UIValidation/UIValidation.pdf
Is there an inherent mechanism that is a part of the Sybase Unwired platform that triggers client-side validations to prevent unncessary round-trips for simple validations that can be processed by the client itself?
Regards,
Namrata

Hi,
For simple validations there is an in-built option in SUP. We can assign rule validations to edit box, this is well explained in [Sybase Infocenter|http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01284.0152/doc/html/vhu1232730866978.html]. Or else we can also do some custom coding and achieve user interface validations. This is also well explained in the [tutorial for blackerry application development using Device Application Designer|http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01210.0152/doc/html/vhu1272906484682.html].
Regards,
Rahul Muraleedharan.

User interface documentation

Similar Messages

Maybe you are looking for