You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
There is a feature request by a User to have a Custom view/form on Click event for a Calendar component. This is actually very useful and pretty straight forward to implement.
Describe the solution you'd like
From @FalkWolsky , " The new click event handler should make use of the stopPropagiation of the standard click handler.
It should not open the dialogue of the calendar, but offer the user to work for example with a modal."
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Hi, any news on implementing this?
There is an event handler for "Double click", but I don't think you can distinguish what element in the calendar was clicked.
Is your feature request related to a problem? Please describe.
There is a feature request by a User to have a Custom view/form on Click event for a Calendar component. This is actually very useful and pretty straight forward to implement.
Details are in Discord Chat link : https://discord.com/channels/1096896040159957084/1096896040650678314/1260284488164970657
Describe the solution you'd like
From @FalkWolsky , " The new click event handler should make use of the stopPropagiation of the standard click handler.
It should not open the dialogue of the calendar, but offer the user to work for example with a modal."
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: