Basically the following issue describes exactly my problem:
http://code.google.com/p/primefaces/issues/detail?id=5247
It is marked as "fixed" for Primefaces 5.1 which I'm using. Sadly I cannot see how this is fixed or should be used now.
The problem in my own words:
I'm using a <p:selectOneMenu> for a (long) list of countries. When the component is selected you can navigate by typing on your keyboard.
Let's say you want to find "Nicaragua" and start typing. After typing "n" "New Zealand" is displayed. Then you type "i" and expect to find entries starting with "Ni...". Instead the "i" leads to display "India".
So everytime a new character is typed, the search starts from the beginning.
I would like to customize/use any kind of settings or parameters.
Using <h:selectOneMenu> (which works as desired) is not an option for design/css reasons.
Any help or suggestions to improve the question appreciated!
Try to use filterMatchMode="contains". It can helps. Just add to the <p:selectOneMenu filterMatchMode="contains">.
Related
when I select a widget say a Text widget in android studio, I hit on alt and enter to generate a code. For example, you can wrap a widget inside a column with this combination but in my case, this combination suggests me things like : generate getter and setter or toString() method which definitely come from java. Now you might say, you have to change your key binding then but that is the problem, on keyboard shortcuts section, I see only one section where I can assign a combination. But then this happens where I only get code suggestions for java. How could I possibly change that?
Alright, so I found the solution, when you check the keyboard shortcuts, you gotta find show context actions and assign a key binding to it, then it is fixed.
I hava a java project that works with jsf and has many rich:suggestionbox. They are working good but I need them work after I enter 4. character to inputbox. The list that retrieved is too long and waiting too much. Do you have a solution for this issue?
Set minChars="4" to your suggestion box.
I have been using insert mode auto-completion for some time now in vim, and I am very pleased with the results. However, I find it annoying (and unnecessary) that the popup menu contains the full path of the dictionary being used.
Is there a way to hide the dictionary path from the menu, or at least modify it in some way?
I ended up using a workaround by defining my own 'completefunc' which gets its values from the specified dictionary file. But if there are any better solutions, please let me know!
My code for this solution is in this question thread.
I've found a strange behaviour using rich:tabPanel in RichFaces 3.3.0.GA and Facelets 1.1.14
The problem occurs when I try to nest a tabPanel in a rich:panel, simpleTogglePanel, or h:panelGrid. The panel is in sever mode.
It suddenly switch to first tab. It's not that easy to reproduce:
If I've got three tabs:
click on 1
click on 2
click on 3
click on 2
click on 3
Sometimes (random) it goes to the first tab, instead of going to the third tab.
The tabs are not generated dynamically, but they are written in xml page.
I've got some custom tags in a taglib in another project (referenced via jar). This happens when I try to insert a rich:tabPanel between my custom tags using
In my tags there are no forms (a4j:form o h:form)
Any idea on how to solve this issue? I may start debugging richFaces, but it's a little hard to do, and I'm not even sure that the problem is in that (it may be in Facelets, for instance).
Thank you very much.
Tabs are controlled by Javascript. Start with debugging JS. Firebug has an excellent JS debugger.
Good luck.
Have two questions.
Make the search filter form non modal.
Allow searching by pressing enter key instead of having to press the Find button.
thanks.
sachin,
Your question seems to be more of a statement, but if you're looking for various options for jqgrid, take a look at:
http://www.trirand.com/jqgrid/jqgrid.html#
New in Version 3.5 > Integrated Search Toolbar
This allows you to interactively search and it respects the Enter key.
However, you lose operators... but I suppose you could modify the code that's given to add something similar back in (or bundle your operator in with the text....ie, user enters "> 400" rather than "400", but this poses security risks)