User interface elements

in the 'configure virtual form for table' part in the tutorial entitled performing inserts, updates and deletes, it's wriiten 'select the user interface elements in the table component, right click and choose Configure Virtual Forms'. but i can't find any 'user interface elements'. can anyone tell me how to get this out so that i can configure the virtual forms. thanx.

Hi,
The "user interface elements" refer to the components namely textField1, dropDown1, textField2 and textField3. Select all of these components either in the designer view or in the Outline window. Once selected right click on one of the components and you will get the option Configure Virtual Forms.
Hope this helps
Cheers
Girish

Similar Messages

  • ABAP WebDynPro User Interface Elements not shown on layout while designing

    Hi,
    When I create a new custom ABAP WedDynpro, the UI Element library is not shown on the view layout.
    I have tried a lot of options in exploring this.
    Kindly help me
    Thanks
    Sai.

    Have you followed the instructions in the online help:
    For the layout editor in the View Designer, all the services specified in Active Services in SICF for Web Dynpro ABAP must be activated. More information: SAP Notes 1009930 and 1008689
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/43/e86de5008b4d9ae10000000a155369/frameset.htm
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/46/d28dfa34bb12bee10000000a1553f7/frameset.htm
    The view designer is a web application itself and your system must be properly setup for web access for this to work.  Also look at your Fully Qualified Domain Name setup:
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/67/be9442572e1231e10000000a1550b0/frameset.htm
    Although a nice feature, the view deisgner is not required for building Web Dynpro Applications.  You can do 100% of the activities with the view designer turned off by working with the UI element tree on the right side of the page.  You can right mouse click and use the context menu to access most functions.  I'm sure that you want to get the view designer working, but until then you can still function.

  • Fundamental User Interface Refreshing Problem with Acrobat X

    After installing Acrobat X (both
    Reader and Standard) I got the problem that over time the refreshing of user interface elements stops,
    which means that Acrobat gets into a state, where you can't see parts of the toolbar (and search button) any longer.
    I'd assume that this might have to do something with my combination of operating systems, grafic chip and or the
    new user interface framwork Acrobat uses now (I guess at least it changed, but don't know details).
    Updating to the newest grafics driver didn't help.
    This problem only occurs in Acrobat X applications on my machine.
    Does anybody have the same problem?
    Does anybody have an idea what might go wrong?
    Here is my data:
    - Windows 7 Pro
    - NVIDIA Quadro NVS 135M
    BTW, it seems I can't switch back to Acrobat Std 9 because after installing Acrobat X with a new
    serial number, the old number is reported as invalid if I remove Acrobat X and try to install Acrobat 9 again.
    So, if somebody has a solution there...

    Anyone have any ideas?James

  • GRC 10 Print Version -Export to PDF in User Interface

    Hi Experts ,
    There is a functionality for getting pdf files generated for most of the reports in GRC 10 user interface elements .but in all the screens while generating the pdf via print version we are getting communication failure  as follows :
    Print Version Communication Failure : RFC Destination SALV_WD_EXPORT_PDF does not exist.
    What could be the reason, export to MS excel worked fine . We are on NW 7.02 SP08 and GRC SP05.
    Cheers ,
    Dev. Parab

    Dear Parab,
    This is a general requirement.The reason why you are getting the communication failure error  is because the print version for generating ABAP ALV is not set-up.
    The flow is : The system (GRC here)uses the RFC connection SALV_WD_EXPORT_PDF to call a portal service >the portal service uses Adobe Document Services>the system uses RFC to return the PDF document to the WD ABAP ALV
    and displays the document.
    For your NW version and SP level , please implement SNOTE  1413938 - WD ABAP ALV -creating print version.
    The  Web Service Destination for Adobe Document Services (in SAP NetWeaver
    Administrator) needs to be set-up as explained in note.
    Also see  IMG > SAP Netweaver >AS> Setup Printing for Web Dynpro ABAP ALV .
    Best Regards,
    Vishal Padiyar

  • Simple User Interface Improvement

    There is one aspect of the user interface that has always slowed my productivity in LR. The scroll bars located on the far left and right of the side panels are thinner than standard scroll panels in Windows programs. When I work with the interface at my normal operating speed, I usually miss the scroll bar 50% of the time when I try and click and drag them. I thought over time this issue would go away as I got use to this irregular aspect of the LR interface, but it has not during the years I have used LR starting with version one. Since many people have wide screen displays, it seems like having a normal width scroll bar would not sacrifice that much screen real estate and would benefit those of us with hand eye coordination that falls outside what was envisioned by the LR user interface developers. Perhaps it could be an optional setting.
    Of all of the user interface improvements possible in LR, this one simple change would be of the greatest benefit to my productivity.
    Thank you for considering it

    Ken, I agree. In general, many of the user-interface elements of LR are fussy and non-standard in their behavior.  A couple of examples: The scroll bars don't have up and down arrows at the end, making it hard in large catalogs to scroll by one line of thumbnails using the mouse.  Scrolling the Library Filter Keywords column is particularly painful when it has a thousand keywords.
    Adobe wants feedback to the product team submitted at the feedback forum:
    http://feedback.photoshop.com/photoshop_family/products/photoshop_family_photoshop_lightro om
    If you create a topic there, I'll vote for it!

  • UI (User Interface) text size and colors

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

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

  • FAQ: User Interface Guidelines for CRM 2007 are now available

    The CRM UI Concept Team has made the UI Guidelines for CRM Web Client User Interface (CRM 2007 UI) available to the BPX community:
    This document provides an overview of the on-premise as well as the off-premise versions of the SAP CRM Web Client User Interface (UI). It contains the properties and principles of the SAP CRM Web Client UI that are already committed and available. For planned features, refer to the corresponding specification documents.
    The information in the guidelines starts with general topics, followed by details. The sections are organized with high-level topics like Page Types and Navigation Schema first, followed by the consecutive sections describing which building blocks and elements of the UI populate the various pages. A section typically starts with one or more screenshots of a central UI element with a generic explanation. The subsequent sections explain the detailed aspects of each element.
    We hope that you will find this information useful.
    Enjoy the new CRM UI! [UI Guidelines for CRM Web Client User Interface (CRM 2007 UI)_ |http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf]
    Edited by: Zhaojie Liu on Jun 10, 2009 10:08 AM

    Hi,
    not sure why your download stops.. you can also try to download via this link: [http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf|http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf] (Document is 17,4MB of size)
    Here the guidelines also have been posted together with an article about the CRM 2007 Web Client UI.
    Hope this helps
    Best regards
    Ingo

  • User Interface Guidelines for CRM 2007 are now available

    The CRM UI Concept Team has made the [UI Guidelines for CRM Web Client User Interface (CRM 2007 UI)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/302d8152-002b-2b10-34bd-9ff3c712dd4b] available to the BPX community:
    This document provides an overview of the on-premise as well as the off-premise versions of the SAP CRM Web Client User Interface (UI). It contains the properties and principles of the SAP CRM Web Client UI that are already committed and available. For planned features, refer to the corresponding specification documents.
    The information in the guidelines starts with general topics, followed by details. The sections are organized with high-level topics like Page Types and Navigation Schema first, followed by the consecutive sections describing which building blocks and elements of the UI populate the various pages. A section typically starts with one or more screenshots of a central UI element with a generic explanation. The subsequent sections explain the detailed aspects of each element.
    We hope that you will find this information useful.
    Enjoy the new CRM UI!
    Feel free to provide your feedback.
    Edited by: Florian Weigmann  on Jul 17, 2008 9:14 PM

    Hi,
    not sure why your download stops.. you can also try to download via this link: [http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf|http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf] (Document is 17,4MB of size)
    Here the guidelines also have been posted together with an article about the CRM 2007 Web Client UI.
    Hope this helps
    Best regards
    Ingo

  • 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

  • How do I fix incorrect resolution for Firefox user interface on Retina display Mac?

    I have a 15" retina display Mac (roughly a year old) running Mountain Lion. A couple weeks ago the user interface in Firefox seems have switched from using the normal zoom level of every other application to the native dpi of the retina display monitor. This means that the UI elements are all extremely tiny, etc. Is there anyway to reset this without simply reinstalling or reseting the rest of my configuration?
    Currently running Firefox 27.0.

    You can try to modify the gfx.hidpi.enabled pref on the <b>about:config</b> page (<=0: disable; 1:all screens same res; >1:enable always).
    *http://kb.mozillazine.org/about:config
    Try to disable hardware acceleration in Firefox (you need to close and restart Firefox).
    *Firefox > Preferences > Advanced > General > Browsing: "Use hardware acceleration when available"
    *https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
    You can set the layout.css.devPixelsPerPx pref on the <b>about:config</b> page to 1.0 and if necessary adjust layout.css.devPixelsPerPx starting from 1.0 in 0.1 or 0.05 steps (1.1 or 0.9) to make icons show correctly.
    *http://kb.mozillazine.org/about:config
    See also:
    *https://support.mozilla.org/kb/forum-response-Zoom-feature-on-Firefox-22
    Use an extension to adjust the text size in the user interface and the page zoom in the browser window.
    You can look at this extension to adjust the font size for the user interface.
    *Theme Font & Size Changer: https://addons.mozilla.org/firefox/addon/theme-font-size-changer/
    You can look at the Default FullZoom Level or NoScript extension if web pages need to be adjusted after changing layout.css.devPixelsPerPx.
    *Default FullZoom Level: https://addons.mozilla.org/firefox/addon/default-fullzoom-level/
    *NoSquint: https://addons.mozilla.org/firefox/addon/nosquint/

  • How to use own style sheet in user interface templates to change buttons, fields look

    I want to use my own style sheet to change the appearance of buttons, form fields etc. while applying my own user interface template. I know I can create an unstructured UI template to change logos, body color etc. but how do I apply css to buttons, fields generated by the portal components form wizard ?
    If this is not possible, how do I create my own form and get the same functionalities of a wizard generated form ?
    Thanks.

    Mrinal,
    I have solved that problem fortunately.
    What I did was to create my own unstructured user interface template. In the unstructured UI template, you can use style.
    for example, in between the <head> tags, write <style> tages and create own classes for buttons, textboxes etc.
    Then write a javascript to assign those classes to the buttons. Call the javascript function on OnLoad event in <BODY> tag.
    That will do the job.
    for example you have a style class called buttonclass for buttons.
    <script langauge=javascript1.1>
    function setstyle(form) {
    for (var i=0; i<form.length; i++) {
    if (form.elements.type == 'button') {
    form.elements[i].className = "buttonclass";
    </script>
    <BODY onLoad = "setstyle(document.forms[0]);">
    hope this helps.
    Mainak

  • CS5/CS4 GUI User Interface Design

    I have always been very unimpressed with the user interface design on Adobe CS4.  It's riddled with problems and changes that make no sense and offer no advantages.
    For example, there is no longer a normal Windows title bar in many of the CS4 apps.  This makes it much more difficult to maximize/restore applications since normally a Windows user could simply throw the mouse to the top edge of the screen and double click the title bar.  In fact, doing this with CS4 apps has ZERO function (it doesn't do anything).  One would think that by moving the menu commands to the top bar of the window chrome, Adobe would make these menus accessible from the top-most edge of the screen in order to increase usability.  Unfortunately this is not so and clicking the top most edge of a maximized window does nothing.
    Two other very important parts of an application user interface are the upper left and upper right corners.  Normally when a Windows application is maximized, throwing your pointer to the upper right corner and clicking will close the application.  Throwing the pointer to the upper left corner and clicking will reveal the application window menu.  This happens in ALL applications... EXCEPT for Adobe CS4 programs.  These two extremely important application window command locations have been completely disabled in Adobe CS4 apps. Clicking the upper most corner pixels in a maximized Adobe CS4 app does nothing.
    Then there's the tabbed document window interface.  If you float a document window and maximize that, normally you would expect it to become maximized within the application window as it should.  Au contraire, in Adobe CS4, the document window maximizes itself ON TOP OF the application window, thus obscuring and disabling any access to the application window's tools/commands.  I did report that as a bug during beta, but obviously it was ignored.  Seems kind of obvious to me that the fact that a user could accidentally make the entire application completely unusable by maximizing a document window might be a problem.
    It still alludes me as to why Adobe changed the CS4 user interface to something that breaks so many Windows UI conventions.  Adobe CS3 was a practically perfect user interface design on Windows.  It was very customizable, all of the normal Windows functions were properly in place.
    What's the deal with the change?
    I thought maybe the file menu was moved in place of the title bar in order to make more room for other UI elements, but it's actually pretty much the same size as the old file menu title bar combination in CS3.
    With all these changes and with all the functionality losses, what exactly have we gained in the CS4 GUI?  Seriously, I'm asking.
    Anyway, I hope Adobe starts reading the Windows User Experience Guidelines (http://msdn.microsoft.com/en-us/library/aa511331.aspx) and brings CS5 back to the way a Windows application should behave.  Proper theme adherence would be nice too.
    Which brings me to Windows 7.  I love love love the way Windows 7 groups application document previews in one taskbar icon and allows aero-peek for open windows.  Adobe CS 4 obviously does not support this since it does not have normal document windows.  I hope CS5 does because it is a great feature.  I also hope Adobe CS5 implements the Windows 7 jumplists and maybe even a more touch/multi-touch friendly interface.  I've become pretty good at processing photos in Bridge using the touchscreen, and it's very cool, but it could use some improvements.
    For an example of great user interface design, has anyone tried Office 2010 on Windows 7 yet?  http://www.istartedsomething.com/20090512/screencaps-office-2010-technical-preview-teched- 2009-keynote/
    The faded transparent title bar and tabbed ribbon interface is absolutely gorgeous.

    @Adam:
    I agree with your comments! So well said!
    And there are other issues, too -- by the color of the app window, you don't know if the window is active or inactive (focus or not in focus). Titles of panels which are inactive, are dark text over dark background -- hardly readable at all... And many more.
    I really hope Adobe are listening...

  • Why hasn't Adobe navigation and user interface design improved as much as it could have over time?

    I haven't tried CS6. I'm sure it's great based on what i've seen alone. But as a user of adobe products for a number of years, i have to noticed there are still a lot of stagnant,awkward, stiff, irriating, slowing down elements found in the navigation and user interface on cs3-cs5, that i'm sure could have been eliminated or improved on at least from 2005 or 2007 onwards. I find some of these things inexcusable and unprogressive from bad traits that defined 1980's and 1990's general computer navigation and so on.
    CS5.5 has lessned this a bid bit and is more fluid in bits and pieces but for those using cs3-cs5 and in general, i find some things just horrid. As a graphic designer no one is supposed to admit the flaws or irrations of these programs. We must hail them as god, never critisize, and always adjust to new things which i think is a bit fascististic and silly
    The way the tools, options are laid out can be improved to be quicker, and easier to find and use. Using your voice as a commanding system would be helpful as well.
    A lot of cmds are too complex to remember, they can be simplier or resemble the name of the tool or option. Its makes a chore to follow this system and competition for the smart *** who memormized all the cmds.
    The way in which you loose floating side boxes, and the amount of tools or names hidden in the bars sometimes seem random and its always a constant search to find them incase you forget where they are.
    The inability to open cs4 or 5 files in cs3 is just beyond extremly annoying. Whey shouldn't you be able to open cs1 or 2 files or photoshop 9 files  as well? Every five years work expires as well?
    The layering system gets tricky and seems that a lot of things don't work when you normally move things. Its about going back, remembering and clicking on this or that, looking it up to make everything work. Sometimes which leaves you in a rut and wastes a good amount of time. You will always find this even after you've been using it for years.
    The use of the fill paint/airbrushing, clone tool, lasso tool, pen tool, history being two steps back can be vastly improved to be much better to use
    Masking and tools that have more complex features should find a way be automatically done or sampled. They can also have less complex steps and tha ability to be  previewed,  automatic or simpler  ( in case you can't remember how to do something or aren't getting it)
    A lot of the special effects, and blending modes are useless, outdated, super-ugly and don't resemble  true darkroom effects ( such as polarization, and bas-relief for example)  which they could much more vividly done. There also could be more options that are closer to repro cameras/CTP software for halftoning and more complex digital effects.
    Having to press or get used to pressing muliple keys or clicks for the most basic things simultaneously can be reduced to be easier
    Adjusting text, new documents, photos should have a smoother, quicker navigational experince where things a lot of room to be , clicked back, re-done, saved in the wrong place etc..
    Indesign could use more shapes, include more features that illustrator has, and possibly even photoshop to save time.
    There should be a way to remind you of features, complex things you've forgotten, other than history and daily usage/practice of the programs
    The help should resemble more of "visual -learners" guide books with voice features.
    There are a lot more
    Regarding other things:
    I think the price encorages more piracy and allows people to not have a concept of what is means to owning software.
    The loss of a manual or lessening of them for certain programs is a loss because it's always useful to  physical info you can flip through while looking at your program.
    I think adobe should make entirely better products for professionals or people in the industry rather than spoonfeeding the same software to all.
    They should also make less expensive add-ons like before for graphic software.
    What do you adobe could have improved over time and if so what do you think they could have improved on?

    You have this wishform to suggest improvements to Adobe products:
    https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
    and the Creative Suites forums are here:
    http://forums.adobe.com/community/creativesuites
    This specific forum is only for discussions on the forums themselves, so you are not very likely to get any change by posting your comments here.

  • PSE User Interface

    A year or 2 ago I tried PSE but ended up not using it based on the user interface.  Fonts, icons and elements within the interface were too small for me to see clearly with a native monitor resolution of 1920 x 1080.  At that time there were no options for the user to increase the size of fonts, icons etc. within the GUI.  I do not want to alter my monitor resolution.  Does PSE 9 have any options to increase the size of these screen elements?  I need to abandon my current image editing program (from another company) as it is so unstable.  Thanks.

    Wallace, check out this post...http://forums.adobe.com/message/3157040?tstart=0

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

Maybe you are looking for