How to only let nodes move in a single lane of the swimlane

Question

I created a swimlane with multiple lanes and allows to dynamically add nodes in swimlane, so I want to know if I choose a lane when adding nodes how to only let nodes move in this choosen lane of the swimlane and not to move to other lanes

Deepa Thiruppathy · Answer

Hi
NIma,Requirement:
How to restrict node’s move from native lane to other lanesWe
do not have any direct support for this requirement. We will try possible work-around solutions and update
you the more details on April 6, 2022.Regards,Deepa
Thiruppathy

Deepa Thiruppathy · Answer

Requirement: How to
restrict node’s move from native lane to other lanesWe have tried a work-around
solution for your requirement, and we are facing an issue in that. We will fix
that issue and fix will be available on or before April 12, 2022.Feedback link: https://www.syncfusion.com/feedback/33992/args-cancel-block-abort-properties-of-selectorchanged-event-is-not-working

Deepa Thiruppathy · Answer

Requirement:
How to
restrict node’s move from native lane to other lanes.We have achieved your requirement
by using BoundaryConstraints property of NodeChangedCommand.Code snippet:

private void
  OnNodeChangedCommand(object obj)
  {
      var args = obj as
  ChangeEventArgs<object, NodeChangedEventArgs>;
      CustomNodeVM node = args.Item as
  CustomNodeVM;
      if (node != null
  && node.ParentLane != null &&
  args.NewValue.InteractionState == NodeChangedInteractionState.Dragging)
      {
          LaneViewModel parentlane = (args.Item
  as CustomNodeVM).ParentLane as LaneViewModel;
          //Setting boundary constraint as lane’s
  parent bounds.
          args.BoundaryConstraints =
  (parentlane.Info as ILaneInfo).Bounds;
      }
  }

Sample
link: https://www.syncfusion.com/downloads/support/directtrac/general/ze/SwimlaneSample-382660735As
we mentioned earlier, we have faced an issue when restrict node’s move from native lane to
other lanes. We have fixed that issue and integrated the code changes of the issue in 19.4.0.48
version.Please find the patch
details as below,Recommended
approach - exe will perform automatic configuration   Please
find the patch setup from below location:https://syncfusion.com/Installs/support/patch/19.4.0.48/1442848/F174100/SyncfusionPatch_19.4.0.48_1442848_4122022081420843_F174100.exe  Advanced
approach – use only if you have specific needs and can directly replace
existing assemblies for your build environment   Please
find the patch assemblies alone from below location:   https://syncfusion.com/Installs/support/patch/19.4.0.48/1442848/F174100/SyncfusionPatch_19.4.0.48_1442848_4122022081420843_F174100.zip  NuGet
Link:https://syncfusion.com/Installs/support/patch/19.4.0.48/1442848/F174100/SyncfusionNuget_19.4.0.48_1442848_4122022081420843_F174100.zipAssembly
Version: 19.4.0.48Installation
Directions : This patch
should replace the files “Syncfusion.SfDiagram.WPF.dll” under the following
folder. $system
drive:\ Files\Syncfusion\Essential Studio\$Version # \precompiledassemblies\$Version#\4.6 Eg :
$system drive:\Program Files\Syncfusion\Essential
Studio\16.3.0.21\precompiledassemblies\19.4.0.48\4.6             To
automatically run the Assembly Manager, please check the Run assembly manager
checkbox option while installing the patch. If this option is unchecked, the
patch will replace the assemblies in precompiled assemblies’ folder only. Then,
you will have to manually copy and paste them to the preferred location, or you
will have to run the Syncfusion Assembly Manager application (available from
the Syncfusion Dashboard, installed as a shortcut in the Application menu) to
re-install assemblies.   Disclaimer
:                Please
note that we have created this patch for version 19.4.0.48 specifically to
resolve the issue reported in this forum 174100.If you have received other patches for the same
version for other products, please apply all patches in the order
received. If
you need the fix in any other version, please let us know. We will provide the
patch in that version. Also, the fix details will be available in our next
weekly NuGet release which will be expected to be release on April 19, 2022.

Deepa Thiruppathy · Answer

Sorry.
We could not include the fix in our latest NuGet release as promised. We will
include the fix in our next weekly NuGet which is expected to be released by
April 26, 2022.

Karkuvel Rajan Shanmugavel · Answer

Hi
NIma, Reported
Issue: BoundaryConstraints argument in the NodeChangedEvent is not working.We
are glad to announce that our weekly NuGet was rolled out successfully. We have
included the fix for the reported issue in this weekly NuGet.NuGet
Version: 20.1.0.51 NuGet
Link: https://www.nuget.org/packages/Syncfusion.SfDiagram.WPF/    Feedback
Link: https://www.syncfusion.com/feedback/33992/args-cancel-block-abort-properties-of-selectorchanged-event-is-not-workingRegards,Karkuvel Rajan S