New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for the selection of non-consecutive cells #4708
Labels
Breaking change
Core: Callbacks
Plugin
Core: Handsontable
Plugin
Core: Walkontable
Plugin
Status: Released
Milestone
Comments
budnix
added
Type: Feature
Priority: normal
Core: Handsontable
Plugin
Core: Walkontable
Plugin
Status: In development
Core: Callbacks
Plugin
labels
Jan 9, 2018
related #2119 |
budnix
added a commit
that referenced
this issue
Jan 18, 2018
cell selection can work (#4708). To make this feature work necessary changes were introduced to the selection functionality. The logic responsible for selection was moved into separate files (without breaking change). Now, every file has its own responsibility: for keeping selection coordinates and for keeping properties necessary for visualizing the borders.
budnix
added a commit
that referenced
this issue
Jan 25, 2018
- Fixed all plugins to be compatible with the non-consecutive selection. Plugin which requires more time to be fixed was temporary disabled when that type selection is detected. - Added support for iterator protocol to array helpers (arrayReduce, arrayFilter, arrayMap, arrayEach). - Added new helpers to checking ctrl meta key codes. - Added new utility (keyStateObserver) designed for retrieving keyboard key states (is pressed or not). - Added missing documentation to the newly created classes.
budnix
added a commit
that referenced
this issue
Feb 9, 2018
- Add support to the Walkontable Selection for marking intersection with CSS class names in continuous manner ('area-1', 'area-2'...) - Optimize clearing CSS classes belongs to Selection - Add CSS classes to support multiple selections and normalized their colors - Adjust ContextMenu actions to make them work in multiple selections - Add support for enabling/disabling multiple selection via new property 'selectionMode' (posible values: 'single', 'contiguous', 'multiple') - Remove 'multiSelect' option. Move to "selectionMode: 'single'/'contiguous'" - Fix keyStateObserver which holds key states after window blur - Extend '.alter' method for supporting new arguments which allows removing rows and columns in batches Issue: #4708
budnix
added a commit
that referenced
this issue
Feb 12, 2018
Renamed `getSelectedRecently` method to `getSelectedLast` and `getSelectedRecentlyRange` to `getSelectedRangeLast` Issue: #4708
budnix
added a commit
that referenced
this issue
Feb 12, 2018
cell selection can work (#4708). To make this feature work necessary changes were introduced to the selection functionality. The logic responsible for selection was moved into separate files (without breaking change). Now, every file has its own responsibility: for keeping selection coordinates and for keeping properties necessary for visualizing the borders.
budnix
added a commit
that referenced
this issue
Feb 12, 2018
- Fixed all plugins to be compatible with the non-consecutive selection. Plugin which requires more time to be fixed was temporary disabled when that type selection is detected. - Added support for iterator protocol to array helpers (arrayReduce, arrayFilter, arrayMap, arrayEach). - Added new helpers to checking ctrl meta key codes. - Added new utility (keyStateObserver) designed for retrieving keyboard key states (is pressed or not). - Added missing documentation to the newly created classes.
budnix
added a commit
that referenced
this issue
Feb 12, 2018
- Add support to the Walkontable Selection for marking intersection with CSS class names in continuous manner ('area-1', 'area-2'...) - Optimize clearing CSS classes belongs to Selection - Add CSS classes to support multiple selections and normalized their colors - Adjust ContextMenu actions to make them work in multiple selections - Add support for enabling/disabling multiple selection via new property 'selectionMode' (posible values: 'single', 'contiguous', 'multiple') - Remove 'multiSelect' option. Move to "selectionMode: 'single'/'contiguous'" - Fix keyStateObserver which holds key states after window blur - Extend '.alter' method for supporting new arguments which allows removing rows and columns in batches Issue: #4708
budnix
added a commit
that referenced
this issue
Feb 12, 2018
Renamed `getSelectedRecently` method to `getSelectedLast` and `getSelectedRecentlyRange` to `getSelectedRangeLast` Issue: #4708
budnix
added a commit
that referenced
this issue
Feb 13, 2018
budnix
added a commit
that referenced
this issue
Feb 13, 2018
- Move 'beforeSetRangeStart' and 'beforeSetRangeStartOnly' hook before coordinates are cleared. This restores the previous behavior of this hook. - Add additionally argument ('ranges') check for ContextMenu 'checkSelectionConsistency' helper. Issue: #4708
budnix
added a commit
to handsontable/handsontable-pro
that referenced
this issue
Feb 13, 2018
Change all `hot.getSelected()` calls to `hot.getSelectedLast()` and `hot.getSelectedRange()` to `hot.getSelectedRangeLast()`. Related-issue: handsontable/handsontable#4708
New API
Breaking Changes:
Compatible Changes:
For all listed hooks the new |
budnix
added a commit
that referenced
this issue
Feb 13, 2018
After thinking about what necessary values are important to have in selection hooks I came to conclusion to revert arguments structure passed to the hooks. Now, the arguments types are the same as before the breaking change. As a compatible change, this commit adds new argument which is 'selectionLayerLevel' which indicates what selection layer is currently modified. Issue: #4708
budnix
added a commit
that referenced
this issue
Feb 14, 2018
- Add unit and e2e tests about changes introduced in previous commits - Fix and update TS types - Remove editor instance from public API (it was added by accident) Issue: #4708
This was referenced Feb 14, 2018
budnix
added a commit
that referenced
this issue
Feb 15, 2018
Replace unary increments/decrements to num += 1 and num -= 1 and add missing new lines for better code readability. Issue: #4708
budnix
added a commit
that referenced
this issue
Feb 15, 2018
Feature non-consecutive selection To make this feature work necessary changes were introduced to the selection functionality. The logic responsible for selection was moved into separate files (without breaking change). Now, every file has its own responsibility: for keeping selection coordinates and for keeping properties necessary for visualizing the borders. Additionally, added changes: - Fix all plugins to be compatible with the non-consecutive selection. Plugin which requires more time to be fixed was temporary disabled when that type selection is detected. - Add support for iterator protocol to array helpers (arrayReduce, arrayFilter, arrayMap, arrayEach). - Add new helpers to checking ctrl meta key codes. - Add new utility (keyStateObserver) designed for retrieving keyboard key states (is pressed or not). - Add missing documentation to the newly created classes. - Add support to the Walkontable Selection for marking intersection with CSS class names in continuous manner ('area-1', 'area-2'...) - Optimize clearing CSS classes belongs to Selection - Add CSS classes to support multiple selections and normalized their colors - Adjust ContextMenu actions to make them work in multiple selections - Add support for enabling/disabling multiple selections via new property 'selectionMode' (posible values: 'single', 'range', 'multiple') - Remove 'multiSelect' option. Move to "selectionMode: 'single'/'range'" - Extend '.alter' method for supporting new arguments which allows removing rows and columns in batches - Fix ObserveChanges plugin which calls 'afterChange' hook with first an argument as an array where should be composed as an array of array - Add unit and e2e tests - Fix and update TS types Issue: #4708
budnix
added a commit
to handsontable/handsontable-pro
that referenced
this issue
Feb 15, 2018
Feature non-consecutive selection Change all `hot.getSelected()` calls to `hot.getSelectedLast()` and `hot.getSelectedRange()` to `hot.getSelectedRangeLast()`. Related-issue: handsontable/handsontable#4708
budnix
added
Status: Merged (ready for release)
and removed
Status: In development
labels
Feb 15, 2018
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Breaking change
Core: Callbacks
Plugin
Core: Handsontable
Plugin
Core: Walkontable
Plugin
Status: Released
Description
This issue is about making support for the selection of non-consecutive cells. The first step to complete this new feature is to build a prototype which works visually without any glitches. The selection shouldn't break any previous functionality.
The text was updated successfully, but these errors were encountered: