Hard coded buttons for select 'all', 'none', 'reset' - allowing new buttons to be inserted. about angular-multi-select HOT 4 CLOSED

Hi aylwong,

May I know what do you mean with a "selected filtered" button? What will the button do?

On Fri, Jun 27, 2014 at 9:56 AM, aylwong [email protected] wrote:

Hi,

Looking at the code, currently the buttons for selection are relatively
hard-coded. I want to insert a selected 'filtered' button, but it required
hard edits into 'case' statements, and so didn't lend itself to an add-on
js file.

I added the button, but was wondering if the ease of adding / changing the
function / text of buttons will be easier in the new version you are
working on?

—
Reply to this email directly or view it on GitHub
#35.

from angular-multi-select.

Sure, a button that toggles the selected values of only the filtered values.

So clicking it will either tick or untick all the filtered entries.

As to how it relates to my original question, I could conceivably want to add more buttons (a 'load more values' or something), or change the text for the buttons (localization). Being able to insert this stuff cleanly without changing the base code would be a boon for me.

from angular-multi-select.

Actually a new version is coming soon, and in that new version, the select all, none, and reset buttons will only affect the filtered results.

Other than that, the new version will have:

• on-item-click() callback
• unlimited nested grouping
• arrow key navigation instead of just shift / shift + tab

I'm not sure on how to add buttons into the directive dynamically. I mean... it's possible of course, but I don't know what's the best practice of doing it. Probably you can show me some samples?

As for the moment, localization support is on my lower priority, so you'll have to modify the code directly. Since I am still working on the new version, I also won't accept pull requests temporarily. I hope you understand :)

from angular-multi-select.

Cool, no problem.

I'll wait for the updated version. As for best practices, I'm not sure either, but after the update I'll see about whether a good go at it can't be made.

from angular-multi-select.