topic Re: Passing parameters to Icommand in ArcGIS Pro SDK Questions

Passing parameters to Icommand

Cheetah24 — Thu, 16 Mar 2023 17:55:33 GMT

How can I pass a parameter using the following code where commandId is a custom class that extends MapTool. Is CanExecute implemented to accept parameters? I always get false when I specify an object.

IPlugInWrapper wrapper = FrameworkApplication.GetPlugInWrapper(commandId);
var command = wrapper as ICommand;

if ((command != null) && command.CanExecute(null))
command.Execute(null);

Re: Passing parameters to Icommand

GKmieliauskas — Thu, 16 Mar 2023 19:51:06 GMT

Hi,

Look at the existing thread:

https://community.esri.com/t5/arcgis-pro-sdk-questions/passing-a-parameter-to-an-icommand/m-p/787266

Re: Passing parameters to Icommand

Cheetah24 — Thu, 16 Mar 2023 20:08:17 GMT

Thanks for the response, this example uses binding and don't think it's translates to what I'm trying to do with Maptool.

Re: Passing parameters to Icommand

GKmieliauskas — Thu, 16 Mar 2023 20:15:21 GMT

You can use your module for parameter exchanging. Make property in module with public get and set methods. Before Execute call set parameter, and on tool activating read it.

Re: Passing parameters to Icommand

RichardDaniels — Thu, 16 Mar 2023 21:17:18 GMT

if your always getting null, you should check that you have Activated the tab your button is on.

FrameworkApplication.ActivateTab('esri_mapping_homeTab');

One activated you execute the button with command..Execute() as you show.

Re: Passing parameters to Icommand

Cheetah24 — Thu, 16 Mar 2023 22:23:16 GMT

Hi. I only get false if i attempt to pass a parameter to canexecute()

Re: Passing parameters to Icommand

Wolf — Fri, 17 Mar 2023 17:05:39 GMT

Neither classes derived from Button (processing your OnClick) nor classes derived from MapTool (processing your Tool) are accepting parameters. If you need to configure any of these button or tool classes, i recommend using properties in your Module derived class (or settings if that's appropriate). Your module derived class is a singleton and easily accessible from any of your code.

internal class Module1 : Module { private static Module1 _this = null; ... internal static string MyToolSetting { get; set; } }

To access this from your tool (within the same project):

internal class MapTool1 : MapTool { private string myParameter; public MapTool1() { IsSketchTool = true; SketchType = SketchGeometryType.Rectangle; SketchOutputMode = SketchOutputMode.Map; } protected override Task OnToolActivateAsync(bool active) { myParameter = Module1.MyToolSetting; return base.OnToolActivateAsync(active); } ... }