Search Path Field Height

We have a large LV developer user base and our users are getting confused by the limitations on the search path fields. The lowercase q really looks like a q (see below), any ideas on how to change this to make it more clear?
Thanks!
Using LabVIEW2012 32bit

Ironically, in your message both characters "lowercase g and looks like a q" they both look the same. I understand, looking at the image that you are saying lowercase G and lowercase Q look the same, apparently because the field height clips the image?
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

Similar Messages

  • Search Forum field height - Apple Support Forums

    Anyone notice the Search Forum field on this support site is annoyingly
    too short in height? When typing into the field, you really can't see
    what you are typing. Didn't know where to post this one,
    but on all browsers on all my devices: iPhone 4 Safari,
    iPad Safari, 3 Macs Safari, Firefox, and Chrome.

    Hey Everyone,
    Firstly, thanks for the replies. I made a mistake.
    Mac's are fine. I'm only having his issue on Safari on my mobile devices (iPhone's and iPads). I believe it's the font size that is purposed
    In the field just under "more options" section.
    Does anyone see what I'm seeing?
    I would assume it's on iPods as well.

  • Searching a Field In Source or Target Message in Message Mapping

    Hey Guys,
                      I  came accross this peculiar behaviour and it keeps bugging me , I could search any field in source or target message in message mapping in PI 7.0 by copying the path( /ns1:MaestroAcreedores/Acreedores/ClaveDeGrupo or any idoc field /FIDCCP02/IDOC/E1FIKPF/BUDAT  ) but in PI 7.1 i cant , its giving me an error String /ns1:MaestroAcreedores/Acreedores/ClaveDeGrupo not found  , i can only search the field independently.Can anyone please help me out in this.

    Hi
    I am not sure whether it worked in 7.0 or not, but having checked myself i can confirm that it is not working in 7.1 in my system also.
    For alternative, you can check by changing into source text view where it will display as xml.  Here when you search the keyword, it would display you the hierarchy better than normal view.
    I dont think there is any other alternative. although I would say in the worst case scenario you would not have more than 10-15 occurrences of same element in an idoc.
    Regards
    Krish

  • Reader X Search doesn't differentiate cached search paths for reselection

    I use the Search quite a bit (or did).
    Specifically the "All PDF Documents in" option, where  the paths of locations that have previously been browsed to are presented for  reuse.
    Previous Reader versions shortened long paths so as  to display the last part of the pathname, which is normally sufficient to  identify the path required.
    X does not, so, with no Tooltip either, it is  now impossible to differentiate paths with common starting paths longer than  that displayed. Update  FAIL.
    Widening the whole search panel does not widen the  field. Update FAIL.
    AND when you start the search you STILL don't get to  actually see what path is being search due to truncation. Again widening the  panel does not widen the fields. Update  FAIL.
    And why can't we have the normal search term field in  the toolbar for seraching the curent document? Although as it took me too long  (I think) to even work out how to get any search button on the toolbar, maybe I  mssed that. Update FAIL (x2).
    And all my old search paths from the previous version  have been binned. Update FAIL again.
    So much for ease of use, do developers actually test  sw "in use" rather than some neatly defined functionallity test scrpit - make  the developers use the product is always a good way to fix this I  find.
    Honestly, if there wasn't enough resource available  in Adobe to sort out this kind of trivial ease-of-use functionallity (that I found in just 5 mins use) then how  can anyone have faith that the serious stuff has been properly  tersted?
    Not a good start for 5 mins use. And I see the  downgrading doesn't work. Stuffed again.

    Any ideas on how I get Quicktime to work that does not include disks?
    Pacifist does not require an optical drive for use. Simply "drag 'n drop" the downloaded "QuickTime769_Leopard.pkg" installer file as downloaded from Apple or the OldApps.com site to the Pacifist Window, select the "QuickTime Player App under the "Applications" entry, and tell Pacifist to extract the app. Then it is simply a matter of dragging the app to your root "Applications" folder.

  • Search Help Field

    Hi,
    I have included a parameter(CHAR 50), say field X in a search help for field Y (Y shud be selected based on X).
    I have attached a search help to X's data element, for providing a drop down.This search help's selection method is a text table for X.
    When I select a value from the dropdown for X in the search help, only the first 19 characters are passed to the search help's screen field.
    Is there any restriction on the length of the value that can be passed to a search help selection?
    Pls let me know.
    Thanks in advance,
    Arthi.

    Hi
    Herewith i am giving some points about Search Help and the Data Element.
    ATTACHING SEARCH HELP TO A DATA ELEMENT ->
    The search help can be used by all screen fields that refer to the  data element. All the fields with the same meaning therefore have an identical input help.
    When the search help is attached to a data element, an export parameter of the search help must be assigned to the data element. If the user selects a line of the hit list in the input help, the contents of this parameter are returned to the corresponding screen field. It is not possible to return several values when the search help is attached to a data element.
    If the parameter assigned to the data element is also an import parameter of the search help, the contents of the search field are used for the value selection if they contain a pattern. Other import parameters of the search field cannot be taken into consideration when the search help is attached to a data element.
    Assign a search help=> You can assign the data element a  search help. This search help is offered on all the screen fields referring to this data element when the input help (F4 help) is called . To assign the search help, you must specify its Name in the data element maintenance screen and an export parameter of the search help in the Parameter field.
    Search Helps =>
    The input help (F4 help) is a standard function of the R/3 System. The user can display the list of all possible input values for a screen field with
    There are two types of search help:
    Elementary search helps describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).
    Collective search helps combine several elementary search helps. A collective search help thus can offer several alternative search paths.
    Screen Display =>
    I think you r talking about the 255 character that a screen lengh can take,but more than 255 character also we can dispaly in a screen.
    go through this link
    http://www.allsaplinks.com/files/using_table_in_screen.pdf
    I hope this will help you to solve your problem.
    Thanks
    Mrutyunjaya Tripathy

  • Office 2013 with Service Pack 1 installation error about "search path"

    I have an automated installation technique that has worked fine with Office 2010 Pro Plus (32-bit), incorporating the latest Service Pack into the network administrative installation point (under \updates), adding 10 foreign languages to the network administrative
    installation point, creating a custom .msp with the OCT (that goes into \updates too), editing the config.xml files, and then running setup.exe from that network administrative installation point. This works on 32-bit Windows XP clients and on 32- and 64-bit
    Windows 7 clients.
    For Office 2013 Pro Plus, I have built the network administrative installation point exactly the same way (original DVD files + languages + SP1 updates + config.xml updates), but the installation is failing with every type of client, all with
    the same error message. The network administrative installation point is readable by the normal installing account, but I even get the same error when I login as me and initiate setup.exe manually, and I have all rights to this point.
    Here's the critical point from a log file:
    2014/03/11 11:53:49:691::[2372] DistributionPoint parsed.  The distribution point is now set to: \\archive.ads.college.edu\archive\KBOXalt\Office2013
    2014/03/11 11:53:49:691::[2372] COMPANYNAME specified in config.xml.
    2014/03/11 11:53:49:691::[2372] USERNAME specified in config.xml.
    2014/03/11 11:53:49:800::[2372] Setupexe Resiliency Mode is set to [PerformIfApplicable]; thus Resiliency is [disabled] for the [InstallExecutionMode]
    2014/03/11 11:53:49:910::[2372] Searching for default versions of resource files under the folder [\\archive.ads.college.edu\archive\KBOXalt\Office2013].
    2014/03/11 11:53:50:019::[2372] Error: GetDirectories: search path \\archive.ads.college.edu\archive\KBOXalt\Office2013 does not exist
    ErrorCode: 0(0x0). Failed final attempt to load a setupexe resource file.
    2014/03/11 11:53:50:019::[2372] Error: GetDirectories: search path \\archive.ads.college.edu\archive\KBOXalt\Office2013 does not exist
    Type: 34::InvalidDirectory.
    2014/03/11 11:53:50:019::[2372] WER element [SuppressModal] is set to value [true]
    2014/03/11 11:53:50:019::[2372] WER element [P4] is set to value [InvalidDirectory]
    2014/03/11 11:53:50:019::[2372] Catalyst execution finished: 03/11/2014 11:53:50.  Return code: 30034.  Exception caught: InvalidDirectory.
    2014/03/11 11:53:50:019::[2372] PERF: TickCount=894821 Name=RunSetup Description=End function
    I cannot find any references to this exact error anywhere on the Internet. Can anyone tell me what this means, and how I fix it?

    As automated, the utility that runs setup.exe maps a drive letter to
    \\archive.ads.college.edu\archive\KBOXalt using a kboxmap AD account, which has read access to the whole \KBOXalt tree. I used that same kboxmap AD account manually to simulate what the utility does, and hit the same problem. But here's what's
    odd: right next to that
    \\archive.ads.college.edu\archive\KBOXalt\Office2013 directory is an
    \\archive.ads.college.edu\archive\KBOXalt\Office2010 directory, both created the same way, and the Office 2010 installation has always worked perfectly using the kboxmap AD account. I don't understand why Office 2013 is only working for an account with
    read/write access, where Office 2010 worked fine for an account with only read access. Especially when the Office 2013 resource kit documentation clearly states that the account running the installation should only have read access, nothing more. (All this
    KBOX stuff comes from the fact that our deployment environment is a Dell KACE KBOX 1000. However, that plays no part in the problem: ignoring the KBOX 1000, I can manually recreate the problem every time.)

  • VI Search Path not working in LV2011 for VI Server Plug-ins with exe

    I have found what seems to be a problem with the search path when a LabVIEW 2011 built executable calls a Plug-in VI. 
    When the plug-in VI has subVI’s from vi.lib on its diagram the executable has to know where to find them.  Not all VI’s in vi.lib are part of the run time engine or the dll’s that may get generated as part of the build. The things you have to do to make plug-ins work for an executable are explained in several Developer Zone articles.   The article titled “How Can I Change or Set the VI Search Path for LabVIEW Executables” describes the ini file setting  viSearchPath.  When this is set to the vi.lib directory I have not encountered problems with previous versions up to and including LabVIEW 2010.
    I have come across an example in LabVIEW 2011 where it doesn’t work.  I have attached an example (I am using LV2011 SP1).  It demonstrates the basic plug-in architecture. Everything works in the development environment.  But it doesn’t work from a built exe.  I haven’t included the actual built exe in the zip file in case that causes a problem downloading it.  If you run the build spec from the src directory project file the exe should get generated in the bld directory.  The problem appears to occur when certain VIs from the analysis library are in the Plug-in.  In the example attached, the Plug-in VI is very simple but I have placed the troublesome SubVI on the diagram.  The VI in this example where there is a problem finding it is the Butterworth Filter VI.  I have placed it on the diagram in a conditional disable structure so it is easy to enable and disable.  When enabled and you run the test Plug-in VI the error 1003 is raised, meaning a subVI cannot be found in the dynamically called VI (for example see this post).  Note that a way round this may be to incorporate the Plug-in VI into the built exe but this shouldn't be necessary.  It’s not a problem with this specific filter VI, as it occurs for other VIs I try on the diagram.  However if you place an FFT VI on the diagram there is no problem.  I suspect that one is built into the Run-Time Engine.
    I also note I am running Win7 64 bit and 32 bit LabVIEW (note the relevant viSearchPath in the ini file – you may need to change if you are on different version of Windows).  If the example is converted to LabVIEW 2010 everything works as expected for the built exe.  I tried that on a colleague’s computer running XP and 2010 but I am pretty sure in still also works on Win 7.
    Things I am suspicious of are that the analysis VI’s are part of a LabVIEW library (lvlib)  and perhaps something has changed there?  I understand there is a problem with OOP in LabVIEW 2011.  Perhaps it is related to that as that seems to be an issue in 2011 (see this Discussion Forum post).  Perhaps it is related to OS version?
    I also tried generating a Source Distribution to extract out all the vi.lib VI’s and place them directly in the Plug-in directory.  That didn’t help.
    Interested in whether anyone else reproduces this behaviour.  In any case something is different in 2011.
    Attachments:
    LV 2011 test Plug-in.zip ‏42 KB

    I found some more out about this issue working with my local NI rep here in Australia.  Apparently something has changed in the compiler between LabVIEW 2010 and 2011.  Using the viSearchPath token in the ini file, as described in various Developer Zone articles, now guarantees that the Plug-in will not work.  The only way to make it work appears to be to create a Source Distribution.  I noted in my original post that I had already tried this and it would not work.  It turns out that having the viSearchPath token in the ini file when using a Source Distribution causes the error 1003 to occur.  When the token is taken out of the ini file the Plug-in (containing an analysis VI) with a Source Distribution works - in the simple example I posted.
    Well I then found its a bit more complicated than this.  It all worked for the simple example I posted.  Recall we found the error when there was an analysis VI in the Plug-in VI.  In our actual application (which is a large one) that calls Plug-ins - we still got the error 1003.  By trial and error I found a workaround.  There are certain Build Spec settings for the calling exe that I set and found worked.  On the Additional Exclusions page I found that I had to make sure that I left unchecked "Modify Project Library File after removing unused members".  I've always had trouble understanding the need for this setting.  In the Build Spec Help on that page it notes that the build will take longer.  In most builds you remove polymorphic VI instances, remove unused members of Project libraries and also Modify the project library file after removing the instances (this is a sub setting of the previous).  This makes the exe smaller in size and a quicker build time. Obviously modifying the project library caused a problem.  In the big application exe calling Plug-in, I probably have the same analysis VI on the diagram (I haven't actually checked and also whether it is the same polymorphic instance) and in the simple example I posted I definitely did not have VI in the calling exe example - so there may be some clue there.  I should try putting the same analysis VI on the calling exe diagram in the simple example to see what happens but I'm running out of energy on this one :-(
    So none of this gives me much confidence and I wish I could get a better explanation from NI regarding this behaviour to be sure I am not going to encounter a different problem for different calling exe and Plug-ins.  I was advised that a CAR would be issued.  Perhaps this is now expected behaviour for 2011 but it would helpful if some definitive explanation could be given about what has changed from LV2010.  And an update of Developer Zone articles on the subject would be helpful.

  • Can't include a reset button/process that cleans a search text field

    Hi all
    Using apex 3.0.1 on a XE edition
    In my app there's a report that displays a lot of records.
    I included an text field item, where user can type a search criteria, then i added a button called "search" which, when submitted, display the records where search criteria is included.
    Now, my problem is that i can't put a "reset" button, which, when submmitted, is supposed to clear the search text field, so the report display all records.
    I tried adding a branch that triggers when reset buttos is pressed, clearing cache of search text field. It didn't worked, search string keeps on showing on text field.
    Then i changed the process, instead of clearing cache, setting search text field item with a value of null. Didnt work either...
    Does anyone have a good example of thjis type of reset button???
    tnks in advance....
    Fernando

    yes Earl, i know it's pretty standard...but i got some trouble... anyway, i think it was just a "lapsus brutus" o' mine... It's solved now and here's what i did:
    I created a text field button (where search string will be typed), a "submit as Go" button, and a "submit as reset" button. Then i created an uncondicional branch to same page, then i created a Clear Cache for Item process, where the text field cache is cleared, conditioned when "submit as reset" button is pressed.
    That solved the problem, thnx very much for your help
    fernando

  • Wine + idtech3 = faulty search path?

    i was trying some games installed on W7 (dual boot) via Wine. now, the majority of them work, but here are some exceptions: every game based on the idtech3 engine. i know they're all compatible with Wine (also know there are linux versions of them, but that's beside the point), but for some odd reason, the engine fails to recognize the actual search path for their base folder/cfg file when i try to wine the .exe. the funny thing is, i am able to play those games (base folder found), if i use the Wine Windows Program Launcher on the .exe, which is a half solution only as i need to optirun it (optimus).
    vblank_mode=0 optirun -b primus wine ~/.../alice.exe
    American McGee's Alice win-x86 Nov 13 2000
    ----- FS_Startup -----
    Current search path:
    H:\/base
    ----- CL_Shutdown -----
    Couldn't load default.cfg
    anyone met this before or have some hints for a solution?
    Last edited by wootsgoinon (2013-11-27 21:52:04)

    Fixed it. ran winetricks 2005 and winetricks 2008.
    Last edited by canuckkat (2011-10-05 01:40:43)

  • TestStand 4.1.1 vi search path

        This is so low-level I'm almost embarassed to ask.  I'm using TestStand 4.1.1 over LabView 8.6, both of which are licensed as full development systems.
        In order for our organization to make better use of (non-NI or Labview) source control, we've created a common directory structure for several developers over several large TestStand/LabView projects.  This includes areas for "common VIs" that are reused across projects.  So I'm in the process of migrating a rather complex project into a new directory structure.  The sequences and VIs in question were working perfectly under TestStand 4.0/LabView 8.5 prior to this attempted migration.
       My test sequences (and sub-sequences) can't seem to find needed VIs, even though they exist in directories that are included in the search paths I configured.  (An annoying sub-problem is that TestStand appears to "hang" while the LabView interface underneath the TestStand window is prompting for a VI's location.  I have to click the LabView item in the Windows menu bar to get LabView "on top" and see what the problem is.)
       I've already added several paths to both the LabView and TestStand VI search paths, and I've even checked the "search subdirectories" box, but the items are not being found.  It's going to take weeks to lead TestStand and LabView by the nose to find all this stuff.
       I can't believe this would really be a bug.  I tried searching the forums for an answer and had no luck.  I can't be the first one with such a problem, so help me out with some search terms so I don't have to clutter the forum with such basic stuff.  Thanks.
    -M

    trosier, Neurotika,
    It appears as if LabVIEW is having trouble finding your VIs, not TestStand.  When TestStand loads the VI you have designated as a code module into memory, if you have the LabVIEW development environment designated in the LabVIEW adapter settings, we tell LabVIEW to load the VI via its ActiveX interface. 
    If TestStand is unable to find the top-level VI, you will see a dialog like this:
    If LabVIEW is unable to find a sub-VI, you will see a dialog like this:
    Notice that the TestStand dialog has an additional checkbox at the bottom that allows you to select an absolute path.  Also notice that TestStand specifies what file its looking for in the Files of Type box while LabVIEW allows you to choose All LabVIEW Files. Which dialog are you seeing?
    Another way to test this is to try to open one of your VIs from disk (by double-clicking on it).  If you get a Searching for SubVIs dialog, then it is LabVIEW that can not find the dependencies. 
    Or if you open the specify module pane of the sequence editor, if TestStand cannot find the top-level VI, you will see a file not found warning like this: 
    If TestStand can find the file, but LabVIEW cannot find a sub-VI, then you will not get a warning or error until the VI is loaded.
    The reason that this matters is that TestStand and LabVIEW do not share their search directory lists.  If you have moved files, you will need to know which application cannot find its files. 
    Message Edited by Josh W. on 04-23-2009 11:27 AM
    Josh W.
    Certified TestStand Architect
    Formerly blue
    Attachments:
    subVI not found by LabVIEW.JPG ‏31 KB
    TestStand file not found.JPG ‏7 KB
    VI not found by TestStand.JPG ‏31 KB

  • Labview doesn not care about "vi search path "?

    We've had some problems with labview taking sub vi's from other library files than wanted. To clean up the mess once and for all I wanted to include the path to the active library files, and remove the <foundvi> from vi search path.
    The added path is something like "\\acanova5\common\...", also tried the version "\\192.168.0.50\common\..."
    So far so good, but when I open a vi that need sub vis (before located in now deleted lib files) LV don't find them. When then manually point to the lib file and point to the vi it is ok, but why doesn't it work as I expect?
    I looked in labview.ini, and my path is the first in "vi search path" list.
    Ola

    We've had some problems with labview taking sub vi's from other library files than wanted. To clean up the mess once and for all I wanted to include the path to the active library files, and remove the <foundvi> from vi search path.
    The added path is something like "\\acanova5\common\...", also tried the version "\\192.168.0.50\common\..."
    So far so good, but when I open a vi that need sub vis (before located in now deleted lib files) LV don't find them. When then manually point to the lib file and point to the vi it is ok, but why doesn't it work as I expect?
    I looked in labview.ini, and my path is the first in "vi search path" list.
    Ola

  • Vi search path

    Hello all,
    I have a problem with "vi search path" in Labview.
    First, here are information about our directories architecture to understand the problem.
    We are using the following architecture for our developments:
    Each project is located in a specific directory.
    ex: Project 1 is located in D:\Data\PRJ1
    Project 2 is located in D:\Data\PRJ2
    In the project directory, there is a subdirectory called "TestTools".
    All Labview developments for a given project are located in this directory
    and its subdirectories.
    ex: D:\Data\PRJ1\TestTools
    In the TestTools directory, there are subdirectories:
    --> ...\TestTools\Tests : containing test VIs (top level)
    ex: D:\Data\PRJ1\TestTools\Tests\Test1.vi
    D:\Data\PRJ2\TestTools\Tests\Test45.vi
    --> ...\TestTools\Utils : containing sub-vi for the tests.
    ex: D:\Data\PRJ1\TestTools\Utils\HF\HF_cfg.vi
    D:\Data\PRJ2\TestTools\Utils\CAN\CAN_start.vi
    If I add "[topvi]/*" in the "vi search path" menu, Labview will search
    the sub-VIs for my application in the directory of the toplevel VI (and its sub-directories).
    ex: if I open "D:\Data\PRJ1\TestTools\Tests\Test1.vi", Labview will search the sub-VIs
    in the following directory: "D:\Data\PRJ1\TestTools\Tests".
    Labview will not be able to find the sub-VI called "HF_cfg.vi" which is
    located in "D:\Data\PRJ1\TestTools\Utils".
    I can add "D:\Data\PRJ1\*" in the "vi search path" menu but It will work only for Project 1,
    and it will not work for Project 2.
    I must replace it by "D:\Data\PRJ2\*" to work with Project 2.
    If I don't do that, Labview will not find sub-VIs for the tests of Project 2.
    (or it will find wrong sub-VIs located in the directory of Project 1 !!)
    This is a problem because we often switch from one project to another.
    We close and re-open Labview when we switch from one project to the other to be sure
    that Labview is not using VIs already loaded in memory, but we still have problems
    with "VI search path".
    Is there a way to configure Labview to search sub-VIs from an upper directory
    that the topvi directory?
    Something like that: "[Topvi]\..\*"
    (the parent directory of the topvi directory, and all its sub-directories).
    I tried "[Topvi]\..\*" but Labview does not support this type of directory.
    Someone suggested me to use "Source code control".
    I am using Labview Full Dev (not Labview Professional) so I can't use "Source Code Control".
    Is there another solution for my problem?
    Thanks for your support.
    NLu

    Dear NLU,
    the behaviour is somehow strange. I have projects with some similar folder layout in which sub-VIs are located under ..\..\DMS\sub.vi relative path from the toplevel VI. The search path is set to default. These VIs are really sub VIs not dynamically loaded. The toplevel VI holds the relative path to its sub VIs if they are on the the same drive and the absolut path if the drive is different. This is a least true from LV 3.0.1 to LV 7.1 under all Windows OS I have used (95 and ME I haven't used).
    Unloading LabVIEW when changing the project is absolutly neccessary since LV holds a list of all folders where it have found VIs during a session. If you switch from PROJ1 to PROJ2 LV will load VIs with the same name in PROJ1 and PROJ2 but with different paths from the path used during working with PROJ1. Unfotunatly there is no menu entry for "Empty VI found list".
    The solution provided by Evan can be made simplier. Create a shortcut to LabVIEW and use the command line parameter -pref to load the desired preference file. Look in the help under "LabVIEW-Defined Command-Line Arguments" for the exact usage.
    Waldemar
    Waldemar
    Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
    Don't forget to give Kudos to good answers and/or questions

  • Controlling criteria in Advanced Search 'Add Fields'

    Hi all,
    Jdev Version: Studio Edition Version 11.1.1.7.0
    Background
    I have two VOs described as below -
    TaskVO - Fetches a list of tasks
    TaskUserVO - Fetches the list of users of tasks - Users may be assignees or owners identified by value in column 'USER_SOURCE_TYPE'.
    A view link relates TaskVO & TaskUserVO by the TASK_ID (primary key of TaskVO).
    I have a view criteria for displaying a search by assignee and search by owner as criteria in my search query region. For this, I have used 2 inline view criteria in my view criteria defined in TaskVO. Both inline view criteria are on TaskUserVO (one for Owner & other for Assignee) and each takes 2 bind variables -
    i. USER_SOURCE_TYPE - This can either be ASSIGNEE or OWNER
    ii. NAME - This is the name of the assignee or owner.
    Issue Description
    The issue I face is in Advanced Search - Add fields. Since the same inline view criteria (TaskUserVO) is added twice (once for Owner & other for Assignee), the Add fields shows 'Name' twice in the list.
    I need to show the Add field label name as 'Assignee' corresponding to the Assignee inline VC and name as 'Owner' for Owner inline VC. How can I achieve this?
    In general, I am also looking for ways to pro-grammatically modify the 'Add field' list (I understand that the Queriable flag controls this list declaratively). Any suggestions on this?
    Could QueryModel/QueryDescriptor help in achieving this?
    Thanks,
    Srini

    Any thoughts on this one?

  • Since Firefox updated yesterday, it won't respond to addresses in the url field or search terms in the search engine field. I can only go to addresses already in my bookmarks.

    When I type an address into the url field the browser will not load the page...it just sits there as though waiting for me to press enter. Also it won't respond to the recently used addresses that show in the dropdown menu. It will also not respond when I try to use the search engine field (google). This started yesterday after Firefox automatically updated to version 3.5.9. I don't get an error message, just no response at all.

    Start Firefox in [[Safe Mode]] to check if one of the add-ons is causing the problem (switch to the DEFAULT theme: Tools > Add-ons > Themes).
    * Don't make any changes on the Safe mode start window.
    See:
    * [[Troubleshooting extensions and themes]]
    * [[Troubleshooting plugins]]
    If it does work in Safe-mode then disable all extensions and then try to find which is causing it by enabling one at a time until the problem reappears.
    * Use "Disable all add-ons" on the [[Safe mode]] start window to disable all extensions.
    * Close and restart Firefox after each change via "File > Exit" (Mac: "Firefox > Quit"; Linux: "File > Quit")
    This can also be a problem with the file places.sqlite that stores the bookmarks and the history.
    * http://kb.mozillazine.org/Bookmarks_history_and_toolbar_buttons_not_working_-_Firefox

  • How to create search path for the file on the desktop..

    hello experts..
          I have used gui_upload module to upload the data from flatfile to the internal table, in that how can i create search path for the file selection in the selection screen, also please help me the code to update the ztable.
    thanks

    HI
      If iam not wrong you want to select a file from a location that you don't know so if this is ur problem then use the function module
    F4_FILENAME
    this FM helps to locate and select the desired file from the system.
    Sample code that you can check is
    How to get windows filename
    PARAMETERS: lv_file LIKE rlgrap-filename.
    Method 1
        CALL FUNCTION u2019KD_GET_FILENAME_ON_F4u2019
        EXPORTING
        MASK = u2019,.txt,.*u2019
        STATIC = u2019Xu2019
        CHANGING
        FILE_NAME = LV_FILE.
    Method 2
    CALL FUNCTION u2019F4_FILENAMEu2019
    EXPORTING
             program_name = syst-cprog
             dynpro_number = syst-dynnr
             field_name  = u2019 u2019
         IMPORTING
             file_name   = LV_FILE.
    Regards
    Pavan

Maybe you are looking for