Hi Telerik Support Team,
I would like to request a feature enhancement for the Kendo UI for Angular TreeList component, specifically regarding the selection mechanisms.
Feature Request:
Please consider adding a (selectAllChange) event emitter to the <kendo-treelist-checkbox-column> component, similar to how selection events are handled or how other advanced components expose header checkbox interactions.
Use Case / Motivation:
Currently, when a user clicks the "Select-All" checkbox in the header, it is difficult to intercept this specific action efficiently to run custom business logic, perform secondary async operations, or manually update external states that depend strictly on the "all selected/unselected" toggle.
While we can listen to general selection changes on the TreeList, having a dedicated (selectAllChange) event that emits the current state (e.g., true, false, or even a custom event object) would provide much cleaner control over the application state, especially in complex data-binding scenarios.
Proposed Syntax:
<kendo-treelist-checkbox-column
[showSelectAll]="true"
(selectAllChange)="onSelectAllChange($event)">
</kendo-treelist-checkbox-column>
Hi,
We're heavily using the Scheduler component, but we've hit a problem with `slotClick` in scenarios involving multiple scheduler instances on the same page.
With two schedulers on one page, slot detection for the second scheduler (used in context-menu flows via slotByPosition) can be wrong.
Detaild repro: Stackblitz
Repro steps:- Right-click any slot in Scheduler #2.
- slotClick gives expected slot, but slotByPosition(...) can resolve incorrectly/undefined, which can cause error in the app when code depends on slotByPosition.
The issue:
- BaseSlotService.calculateScaleX() uses document.querySelector(".k-scheduler"), which always picks the first scheduler in DOM.
- With two schedulers on one page, slot detection for the second scheduler (used in context-menu flows via slotByPosition) can be wrong.
- Relevant code:
const h = document.querySelector(".k-scheduler");
return h.getBoundingClientRect().width / h.offsetWidth;
- Expected: the instance of scheduler used in the calculation should be the one that fired event, not the first one from DOM.
Hi,
When the first day of the week is changed dynamically through a custom IntlService, the Calendar weekday headers are updated, but the date cells are not repositioned. (The first day is changed as described in your guide: https://www.telerik.com/kendo-angular-ui/components/knowledge-base/calendar-first-day )
Reproduction (forked from your example): https://stackblitz.com/edit/angular-tqvypgwg
Click on "Set first day to Monday ": the weekday headers are updated to start with Monday, but the date cells remain in their previous positions.
Best regards,
Michael