# Dear Path Mapper,

**URL:** <https://discourse.mcneel.com/t/dear-path-mapper/99186>\
**Category:** Grasshopper\
**Created:** [March 31, 2020, 2:02pm UTC](https://discourse.mcneel.com/t/dear-path-mapper/99186 "2020-03-31T14:02:57Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Mahdiyar](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/mahdiyar/32/472862_2.png) [@Mahdiyar](https://discourse.mcneel.com/u/Mahdiyar)\
**Post date:** [March 31, 2020, 3:15pm UTC](https://discourse.mcneel.com/t/dear-path-mapper/99186/7 "2020-03-31T15:15:07Z")

</div>

> [@Dani\_Abalde](#):
>
> That’s like developing the math for counting with the fingers.

I totally agree, however, this way we can dynamically change `Path Mapper`:

> [@Path Mapper with Variable Input](https://discourse.mcneel.com/t/path-mapper-with-variable-input/97740/5):
>
> PathMapper doesn’t accept dynamic variable input. however here I’ve made a little script that can change PathMapper source and target dynamically: private void RunScript(string source, string target) { var pathMappers = FindPathMapperObjectInCurrentGroup(); if(pathMappers.Count != 1) { Component.AddRuntimeMessage(GH\_RuntimeMessageLevel.Warning, "This component should be added in a group with exactly one Path Mapper component."); return; } …

[PathMapper.gh](https://discourse.mcneel.com/uploads/short-url/pBhwiBbCZVUHvZJ0M6ikZgIw8Zy.gh) (16.7 KB)

---

_[View the full topic](https://discourse.mcneel.com/t/dear-path-mapper/99186)._