Ext.ux.form.SuperBoxSelect as seen on facebook and hotmail

[danh2000]

This is a great component!

Thanks.

I've found it helpful to also be able to pass in an array of values to setValue (instead of having to join() just for the value to be re-split()), so I made the following change:

    setValue: function(value){
    	var values = Ext.isArray(value) ? value : ((typeof value == "string") ? value.split(this.valueDelimiter) : []);
    	this.removeAllItems().resetStore();
    	....

I imagined that most people would use the same format as returned by getValue, which is a delimited string (ie. What comes out goes back in), I have included this though as it may help those who split the values into an array.

[danh2000]

I've just updated the first post with a new version containing:

• -Fixed a couple of bugs that occured when using setValue when the component had not been rendered (eg. hidden tab).
• -Enabled setValue to accept either an array of values or a delimited string.

[radtad]

form enabled (everything seems fine, but it won't do addItem)...

this.buttonClear is undefined
this.buttonClear.addClassOnOver('x-superboxselect-btn-over')

I can't re-create this - I've set disabled to false and used addItem without issues.

If you are still having problems, please post a link to a working example, or copy and paste code that I can use to reproduce the error.

Thanks again,

This happens on a call to initButtonEvents (within onEnable). I think the following code for that should read :

    onEnable: function(){
        Ext.ux.form.SuperBoxSelect.superclass.onEnable.call(this);
        this.items.each(function(item){
            item.enable();
        });
        if(this.renderFieldBtns){
            this.initButtonEvents();
        }
    },

[danh2000]

@radtad

You are correct - thanks for the report.

[arconen]

Please help me

Then I try to use transform feature in IE8 (maybe for all from IE6) for SELECT tags, I'll receive the next one:

Object doesn't support this property or method

in next construction

var N=R.ownerDocument.createRange();

on ext-all.js (ExtJS 2.2)

- Try to use component like this:

    SelectDepartmentID = new Ext.ux.form.SuperBoxSelect({
      transform: 'DepartmentID',
      allowBlank: false,
      resizable: true,
      name: 'DepartmentID',
      width: 500,
      displayField: 'text',
      valueField: 'value',
      classField: 'cls',
      styleField: 'style',
      extraItemCls: 'x-flag',
      extraItemStyle: 'border-width:2px',
      stackItems: false
    });

<select id="DepartmentID" multiple size=5"  onchange="frm.submit()">
  <option value="value0" selected>text0</option>
  <option value="value1">text1</option>
  <!-- and more option in this place -->
  <option value="valueN">textN</option>
</select>

- Try to expand the SuperSelectBox on the page after rendering it
- And now I receive this error.
Also reproducing then I try to select one of the items from the list

What can I do for fix this? Or this is a bug?

[arconen]

Question are closed. Sorry

[gianpaulo]

It would be good to add token searching config. Just like facebook.

[danh2000]

It would be good to add token searching config. Just like facebook.

Thanks for the suggestion, but I've never used Facebook - can you elaborate on what token searching means?

Thanks,

Dan

[qooleot]

First off, very nice widget! I found two small issues, however, that might cause others issues when first starting out:

1) You mention allowNewData in the notes for example 2, but its really allowAddNewData in the example.

2) For example 2, the store fields seem to be required to be ['id','name']. If I change the store fields 2 index to 'test' instead of 'name' and the displayField to 'test' from 'name' for the superboxselect, then type in a new value (selecting one from the pulldown works fine), then the text is not displayed.

I was able to work past those, so no worries, but just a heads up. Keep up the good work!

[danh2000]

First off, very nice widget! I found two small issues, however, that might cause others issues when first starting out:

1) You mention allowNewData in the notes for example 2, but its really allowAddNewData in the example.

Yes I changed the name from a previous version - I'll update the text on the example page, Thanks!

2) For example 2, the store fields seem to be required to be ['id','name']. If I change the store fields 2 index to 'test' instead of 'name' and the displayField to 'test' from 'name' for the superboxselect, then type in a new value (selecting one from the pulldown works fine), then the text is not displayed.

I think you've misunderstood how it works - you can use any field names you want, but if you are changing the field names you must also change the 'newitem' callback to use the same.

Thanks for the feedback,

Dan