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
"Hi, we're trying to programatically disable the ability to drag columns into a certain area within a grid and we're having issues with the columnDrag event, which sounds like it should do the job for us.
We believe our only option is to use the insertBefore property on the event to determine if the drop is valid or not, however we're seeing that the insertBefore value is the HTML element for the column, not the bryntum column itself.
I've reproduced it here, just open up the console and try dragging the first name column around. You'll see that the thing logged out is definitely not a bryntum Column! https://codepen.io/GJFForce/pen/bGQBWRg?editors=1011
Is this expected? Is there a workaround? And finally, is there a way to prevent column drags into a specified grid region entirely using the columnDrag event handler? We've had no luck so far in knowing whether a column is being dragged to the end of the locked region, or the start of the unlocked region, as the position is the same from the perspective of the column store. If there is an alternative approach available to us it would be most welcome!"
We need to update the documentation or update the payload to match the current documentation
The text was updated successfully, but these errors were encountered:
Forum post
"Hi, we're trying to programatically disable the ability to drag columns into a certain area within a grid and we're having issues with the columnDrag event, which sounds like it should do the job for us.
We believe our only option is to use the insertBefore property on the event to determine if the drop is valid or not, however we're seeing that the insertBefore value is the HTML element for the column, not the bryntum column itself.
I've reproduced it here, just open up the console and try dragging the first name column around. You'll see that the thing logged out is definitely not a bryntum Column!
https://codepen.io/GJFForce/pen/bGQBWRg?editors=1011
Is this expected? Is there a workaround? And finally, is there a way to prevent column drags into a specified grid region entirely using the columnDrag event handler? We've had no luck so far in knowing whether a column is being dragged to the end of the locked region, or the start of the unlocked region, as the position is the same from the perspective of the column store. If there is an alternative approach available to us it would be most welcome!"
We need to update the documentation or update the payload to match the current documentation
The text was updated successfully, but these errors were encountered: