Is it possible to add new value on the fly with this code.
I'm not sure I understand your question - do you mean add values to the component via code rather than user interaction? if this is the case, then Yes absolutely - this is demonstrated on the examples.
Note. There are still a few small refactorings that I would like to do, but I'm primarily concerned with getting bug reports and some feedback on the remote functionality as I work towards releasing the current features as a stable version 1 release.
Hello to developer,
Demo looks very good as previous comments sad many times before, i`m just looking it but have a little problem. If you use button BasicForm.getValues() you could see the resulted parameters which are multiple values for one variable. If I should have an advice, please create another parameter generating solution which generates the parameter list with leading "[]" after all items, because the currently available list in PHP interprets as a single value rather than an array of values.
For example:
Current version returned with: states=AL&states=AR&states=FL
My advice is: states[]=AL&states[]=AR&states[]=FL
Thank you for your time, sorry for my english,
AdHoc PHP Framework developer, permanent ExtJS fan
Prometheus, when developing with PHP, you must append square brackets to the name of form fields being submitted as Arrays - this component is no different:
Added 'clear' event.
Added a 'record' param to the addItem and removeItem events.
Added 'supressClearValueRemoveEvents' config.
Added fix to escape internal regexp.
Added new 'supressEvents' param to clearValue method.
Removed docs for removeAllItems method - clearValue should be used instead.
Added addItems method.
Fixed scope issue in getValueEx method.
Fix to provide an originalValue (and fix reset) when remote store used.
I've updated the first post here with a new version containing the following changes:
Fix to work around Ext 3.0.0 bug - store load event not providing params to callback.
Fix to allow store to be provided as an xtype.
Fix to clean up after prevention of 'remove' events during clearValue.
Fix to prevent submission of empty value when doing a raw form submit.
Fix for IE8 error during transform.
Inclusion of superboxselect-gray-extend.css from the extended gray theme (Thanks Galdaka)
I'm trying to use the SuperBoxSelect as a grid cell editor. Besides the basic data transformations, does anyone know what needs to be done (general approach) for getting the editor to render properly in the cell? For example, currently it will display but selected items aren't visible in the editor and once you've used it once, the dropdown button disappears. It does allow you to select values however. But you just don't see them until you're done editing.
I'm sure a little customization is required of the control but I'm not sure even where to start. Any guidance greatly appreciated!
I'm trying to use the SuperBoxSelect as a grid cell editor. Besides the basic data transformations, does anyone know what needs to be done (general approach) for getting the editor to render properly in the cell? For example, currently it will display but selected items aren't visible in the editor and once you've used it once, the dropdown button disappears. It does allow you to select values however. But you just don't see them until you're done editing.
I'm sure a little customization is required of the control but I'm not sure even where to start. Any guidance greatly appreciated!
Sorry mathec, it's not something I've done.
I think it would require more than a little customization too - the html structure of the component and it's items would need some re-structuring for this scenario, and the functionality (keyboard handlers etc) is likely to conflict too.
Originally Posted by lossendae
Reply With Quote