Repository navigation
init after destroy(false) doesn't work #1204
Description
Subject of the issue
A grid initialised on the DOM left by grid.destroy(false) doesn't seem to work: widgets are not draggable.
Your environment
- version of gridstack.js 1.1.0
- which browser and its version Chrome Version 80.0.3987.132 (Official Build) (64-bit)
Steps to reproduce
grid = GridStack.init() // works well
grid.destroy(false)
grid = GridStack.init() // widgets are no longer draggablehttps://jsfiddle.net/n4f2dpv5/
Expected behaviour
Initialising a new grid (GridStack.init()) on the DOM of the destroyed one (grid.destroy(false)) should work the same way as initialising a "fresh" grid.
Activity
adumesny commentedon Mar 10, 2020
Hey thanks,
did this ever worked before ?
I assume this is a valid user case - what are you trying to do ?
FYI you can disable grid drag/resize by making the grid fixed as well instead of 'destroying it' and re-creating, in case you didn't know.
adumesny commentedon Mar 11, 2020
simple possible workaround for now (there might be more issues as I discovered stuff we didn't do during
destroy(false)is to callgrid.enable();after you init the second time.still a bug that it doesn't work out of the box.
destroy drag&drop when removing node(s)
destroy drag&drop when removing node(s)
adumesny commentedon Mar 11, 2020
fixed in next release.