[3.x] Ext.ux.form.SuperBoxSelect

[danh2000]

some misstake.

Fixed thanks. Must be too much Christmas cheer

[danh2000]

New version attached to the first post in this thread.

UPDATE 27/12/2009

Additional fix to destroy process.
Implemented addNewItem method to fix issue raised in post #242

NOTE Anybody using this component with the allowAddNewData config and a remote store is advised to use the new addNewItem method within their newitem event listeners.

For a demo, see the remote example here:

http://www.technomedia.co.uk/SuperBo...lesRemote.html

[lanhun]

i can not use setValue() method.

In this example
http://www.technomedia.co.uk/SuperBo...lesRemote.html

[danh2000]

i can not use setValue() method.

In this example
http://www.technomedia.co.uk/SuperBo...lesRemote.html

Thanks again! It was a silly typo which I have now fixed.

[danh2000]

New version attached to the first post here.

UPDATE 28/12/2009

Fixed a silly typo which prevented setValue working with a remote store.

[lanhun]

Thanks again! It was a silly typo which I have now fixed.

Thank you for giving us such a good extension.You are the best!

[lanhun]

My English is poor.

I'm in a form using this extension.

when i select some items and then close the Form.

Now opens a new form,The selected items here will not arise.


but ver:21/10/2009 is no like this.New forms have all the data.

config: removeValuesFromStore: true,
mode:'local'

[danh2000]

My English is poor.

I'm in a form using this extension.

when i select some items and then close the Form.

Now opens a new form,The selected items here will not arise.


but ver:21/10/2009 is no like this.New forms have all the data.

config: removeValuesFromStore: true,
mode:'local'

Can you please post a test case with working code so that I can debug.

This thread may help : http://www.extjs.com/forum/showthread.php?t=71015

Alternatively, you could point me to an online example with clear instructions to reproduce the problem.

Thanks,

Dan

EDIT:

I think I understand now - because the records are removed from the store they are not replaced when the component is destroyed, so re-using the same store results in those records not being available.

I'll post a fix soon.

[danh2000]

New version attached to the first post here:

UPDATE 29/12/2009

Fix to replace removed store records when component is destroyed.

[galdaka]

Hi danh,

Excellent support!! thanks for all.

One problem.

I´m migrating from 3.0.3 to 3.1.0. When I updated the latest code of your component over this code:

new Ext.ux.form.SuperBoxSelect({
id: 'notasRTEmpleado',
transform: 'notasRTEmpleado',
allowBlank: false,
allowAddNewData: true,
resizable: true,
name: 'notasRTEmpleado',
width: 750,
extraItemCls: 'font-normal',
stackItems: true,
mode: 'local'
}) 

Don´t work in IE8, OK in FF3X. I have a problem in theses lines (doTransform function):

                        value = (Ext.isIE && !Ext.isIE8 ? o.getAttributeNode('value').specified : o.hasAttribute('value')) ? o.value : o.text,
                        cls = (Ext.isIE && !Ext.isIE8 ? o.getAttributeNode('class').specified : o.hasAttribute('class')) ? o.className : '',
                        style = (Ext.isIE && !Ext.isIE8 ? o.getAttributeNode('style').specified : o.hasAttribute('style')) ? o.style : ''; 

If I change theses lines for OLD lines:

                        value = (Ext.isIE ? o.getAttributeNode('value').specified : o.hasAttribute('value')) ? o.value : o.text,
                        cls = (Ext.isIE ? o.getAttributeNode('class').specified : o.hasAttribute('class')) ? o.className : '',
                        style = (Ext.isIE ? o.getAttributeNode('style').specified : o.hasAttribute('style')) ? o.style : ''; 

Works fine!

P.D: My field notasRTEmpleado is a "select".

Greetings,