Re: Re: quickForm : allowed memory exhausted
| From: | Markus Wolff | Date: | Sun, 25 Apr 2004 16:33:25 +0000 |
| Subject: | Re: Re: quickForm : allowed memory exhausted | ||
| References: | 1 2 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-12116@lists.php.net to get a copy of this message | ||
Tommy Ipsen wrote:
Cindy Blondeel wrote:The hierselect element doesn't really help a lot when you got 1600 possible choices - also, you'd have to be able to categorize them so that adding another selection layer makes sense at all. For elements with so many possible choices I have written myself a custom QuickForm elemnent that does nothing else but draw a selection button instead of a selectbox and places a hidden IFrame unter it. When you click on the button, the IFrame becomes visible - inside that frame, I load a script with a textbox that allows you to specify some search criteria. On submitting that box, the matching results are shown - and if you decide to click on one of them, the IFrame is closed and the ID of the object you clicked on is written into a hidden field in your original form (obviously, Javascript comes into play here). I found this to be a quite comfortable solution for picking one out of so many options. CU MarkusGood afternoon, does any of you ever get the following message while trying to create a select element (mine has 1600 elements) :Have you considered reducing the number of elements - it's hardly user friendly to confront the user with this kind of choice... Perhaps you should consider the custom "hier-select" element instead - it might help you avoid the memory issue as well as increasing the usability of your page!