Answers

• allan Posts: 65,434Questions: 1Answers: 10,865 Site admin

  December 24

  Fantastic feedback - thank you. I've added 1 and 3 to my features list (2 is already there).

  The between option might be a little tricky. With two text box inputs, it would be straightforward - but I'm a little unsure about the UI for that (making it not ugly!). It will be possible, but I'm not certain how I'll implement it yet.

  It will likely be a little while before I work on this points I'm afraid - I'm neck deep in DataTables 3 development and all that is going with that.

  Allan
• rickparrish Posts: 2Questions: 1Answers: 0

  December 24

  I did hack together a workaround for (2) using a global variable set in my page, which I then read from in the searchList init method.

  Do you think it's realistic for me to hack together something for (1) as well (and if so do you have any pointers)? Or because that would require my page to access the inner workings of columncontrol instead of simply having columncontrol reference a global variable like (2) did, maybe it's not realistic?
• allan Posts: 65,434Questions: 1Answers: 10,865 Site admin

  December 24

  With regard to setting a filter via an API, yes it can be done and I use it a lot in the unit tests - have a look here for example:

              $('thead tr:eq(1) td:eq(2) input')
                  .val('s')
                  .triggerNative('input');
  

  The triggerNative is use in the DataTables unit tests:

              $.fn.triggerNative = function (type) {
                  return this.each(function() {
                      this.dispatchEvent(new CustomEvent(type));
                  });
              };
  

  I've used jQuery for the unit tests for ColumnControl, as it just makes selecting etc easier. It could readily be done without if you wish.

  Setting a search term when the search input is in a dropdown is a little more complicated since you need to show the dropdown, set the value and then hide is, but is pefectly possible still.

  Allan