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
{{ message }}
Repository navigation
Bug - Non-Movable/Resizable items should be locked in place #19
When an item is made "non-movable" & "non-resizable", it should be fixed in place. It seems however that dragging other widgets near it can push the non-movable item out of it's current position. The position of non-movable item should not be considered as a possible new location for the item being dragged.
I will add another option for this case. I think it's not a good idea to use current movable/resizable options. Also I think it should only work for floating grid.
Definitely makes sense to make it it's own option. I think there still may be a use case for having it work with non-floating. With non-floating everything gets pushed up, as high as it can go. This may be the typical desired behavior (so a user would opt for non-floating mode), but there may be a couple of elements you want to lock, and not have pushed up. Not sure though.
Activity
troolee commentedon Dec 4, 2014
I will add another option for this case. I think it's not a good idea to use current
movable/resizableoptions. Also I think it should only work for floating grid.ishields commentedon Dec 4, 2014
Definitely makes sense to make it it's own option. I think there still may be a use case for having it work with non-floating. With non-floating everything gets pushed up, as high as it can go. This may be the typical desired behavior (so a user would opt for non-floating mode), but there may be a couple of elements you want to lock, and not have pushed up. Not sure though.
troolee commentedon Dec 6, 2014
It's done. See
data-gs-lockedattribute andlockedAPI method