What is the relationship between this project and isteven/angular-multi-select? Is this a fork and why is there no reference to @isteven?

Hi,

when I set the checked property to true in the input-model, the output-model does not update until the user select an other item.

ex:
$scope.inputmodel= [
{ name: "{{row.name}}", checked: true }
{ name: "{{row.name}}", checked: true }
{ name: "{{row.name}}", checked: false}
];

the output model stay empty ( [] ).

Thanks
Raph

Hi,

I have an issue, when I click outside the dropdown, it doesn't close.

Thanks in advance

I'm trying to implement the search area on the drop-down. Initially the search functionality works fine, but when you start removing characters from the search field, the list items in the drop down start behaving erratically. Some items are being repeated, while other items are being removed from the list.

Here is a plunkr to demonstrate the issue : http://plnkr.co/edit/uPvfSJ8IngeFFGAcHvMd?p=preview

I would imagine this is an error on how I'm implementing the search field, rather than a bug in the directive. Either way, if you have any suggestions I would love to hear them.

Thanks

The filtering doesn't work unless you are doing Grouping. For examples see the Minimal Demo or the Dynamic Update demo. If you type in the search box it doesn't limit what you see.

Create a helper functions that would allow to do programatically:

• select all
• select none
• select by id
• reset
• clear
• open
• close

This is actually caused because the backspace key makes the browser go back in history, and because removing a letter causes an immediate search, the input gets blocked and stops receiving events, thus the backspace key triggering a "back in history" event.

One possible solution is to delay the start of the filter by a few ms.

Здравствуйте. Использую ваш плагин. Но проблема вот в чем:
У меня есть, например, модель:

[{
name:'Test'
 sub: [
{name: 'Вася'},
{name: 'Петя'}
]
},
{
name:'Test2'
 sub: [
{name: 'Коля'},
{name: 'Вася'}

]
}
]

Когда я делаю поиск по имени Вася, то все Васи найдены.
Когда я стираю из строки поиска то, что ввел, то во второй группе Коля заменяется Васей.


Даже тут http://alexandernst.github.io/angular-multi-select/#/demo-grouping
Если ввести несколько раз слово Chrome, в первой группе все будет заменено на Chrome. При бэкспейсе - то же самое.

Can you support ability to clear a selection from the header (with an x next to selection)

Hi,

It could be great if the output-model would bind in the two way. If I clear my model, I would like the directive unselect all entries in the UI.

Thanks in advance

I'm loading 6 of these with ~1400 small objects each, and this makes it pretty unusable. If I get a chance, I'll try to put together a minimal demo, but in my app I'm developing it seems significantly slower than the isteven project version (which itself performs too slowly on this large a dataset).

Disabled items could be an option, but I'm not sure how would they behave.

If a disabled item's parent is checked, should the disabled item get checked too?

... as filtered model is reduced when searching, meaning that button label could show a different number of selected items than what there actually are.

The main property in bower.json points to the wrong path.
It should be 'src/angular-multi-select.js'.

Version 5 works quite well with small/medium data sets, but it's dog slow with big data sets (500+ items). Given the fact that there are some other issues that must be fixed as well, and those require some refactoring too, and the UI part needs to be redone with CSS3 (flex box), there is no reason to limit the project to what is done currently. A complete rewrite will be easier.

Those are the main features that will be worked on:

Faster data structure

Of course, the current data structure that is used to initialize the directive is fine and should probably be kept as it is, but internally some other type of data structure should be used that will allow a faster data access.

The data structure should allow doing the following operations in a fast way:

• Walk the entire data set (if possible, without recursions)
• Get first level children from a node
• Get all children from a node
• Get the parent from a random node

Also, use http://weaver.js.org/ to make the entire process faster.

Faster tick checker

Probably a separate data structure that would help in the process of checking which items are checked will be required.

ES6?

Decide if Babel/Typescript should be used

Searching

Searching is yet another important feature. We can't iterate over each item and perform a regex. Therefore, something else (like http://lunrjs.com/) should be used.

UI

The UI should be rewritten with flex box.

Backwards compatibility

Backwards compatibility should be kept. There is no reason to break it (but it could be broken if needed).

• - Better class names
• - Open widget applying certain logic for the positioning
• - Others

• specs for #21
• specs for #9

Currently item-label will receive a format delimited by {| |} and then it will interpolate it against the item itself. This makes it impossible to use a variable as a key in the object. Example:

$scope.lang = "en";
$scope.data = { "en": "hi", "es": "hola" };

...

item-label="{| data[lang] |}"

Hi,

I need to call a function every time an item is clicked. This function needs to have the list of the selected item from the multi-select and is triggered by on-item-click directive. However, the output-model gets updated only after the callback function have been called.

I think the output model should be updated before the callback is triggered.

I would like to disable the component and ng-disabled isn't working, is there another way to disable the component?

is there some reason you are not using npm/bower correctly and putting all your dependencies in the bower.json and correct publish details in there? If you did so this package would work properly like all other bower packages for client side where a) it auto updates your index.html and b) has the dependencies built in?

I have forked and will look at fixing but unclear why this wasn't done in first place. the npm packages.json should just be containing what you need to run the build and test harnesses.