If we pass true to the removeAll() , ExtJS6 will try to erase the leafes of a tree,
and then try to to iterate throuch these leaves in onNodeRemove() ( this obviously do not work)
The true parameter does not seem to be needed anyway anymore.
After a call to removeAll, the childNodes[] property of the rootNode is empty
Instead of extending the framework ComboBox, we extend the abstract
parent class Picker, so we don't rely on private methods ( and hopefull survive the
next ExtJS upgrade )
Usability improvement:
The selection model is now a checkboxmodel, which makes more clear to the user that
we can select more than one element in the list.
Options such as:
osd mount options xfs = -i size=2048 -n size=16k
were parsed as:
key: 'osd mount options xfs = -i size=2048 -n size'
value: '16k'
This is due to the greedy .* in the beginning. Making it
non-greedy fixes this.
Fixes#851
The Picker of the ComboBox, has by default a maxHeight of 300 px. If the list of elements is bigger that 300 pixels, then a scrollbar will be added.
This behaviour was broken with ExtJS4, but now works correctly with ExtJS6.
This fixes the problem that this ComboGrid was displayed with an empty value
( similar the to the Keyboard Selection and Realm Selection in the login window)
An component id 'comment' is already defined for the column Comment of UserView.js causing here a conflict.
It seems ExtJS6 is more stringent about that than ExtJS4.
If the default activeTab is *undefined* and *not* null, activeTab defaults to 0,
so we don't need to set this explicitely.
dug from ExtJS tabPanel:
activeTab = me.activeTab !== null ? (me.activeTab || 0) : null;
Using ExtJS6 a browser refresh (F5) do not send the 'show' event which we use to display the store as it did with ExtJS4.
At the momment only for tabs inside the datacenter tabpanel, since node and lxc tabpanels are not yet in manager6/
influxdb (> 0.9.5) now support fastly multiple values by mesuerement,
through a new column store engine.
Signed-off-by: Alexandre Derumier <aderumier@odiso.com>