miker i also noticed that IconClone does not run from Shell, and the icon must be of Type "WB".
The def_Tool.info of AROS but also Amiga includes that parameter "TOOL" "CLI", so if IconClone is run with the "def_Tool.info Icon", or from SHELL, IconClone will not start
I thought you said it works great.
There is a ReadMe text file in the release package you should read.
Assign an icon to IconClone then use it from Workbench. Or use it in a shell with the correct arguments and switches. Opening it from a def_tool icon is not recommended nor has it been tested by me.
In the shell "IconClone" by itself does nothing. Likewise "IconClone icon.info" also does not work. Wrong number of arguments. However "IconClone icon1.info icon2.info" will perform the icon exchange at the command line.
There are two switches --h & --o (note that they have double dashes). The 'h' is for help. The 'o' is for open.
At the command line "IconClone --o" will open the empty GUI ready for drag-n-drop. "IconClone --o icon1.info" will open the GUI and display the source icon. "IconClone --o icon1.info icon2.info" will open the GUI and display both images ready for the icon exchange.
If the images fail to display using drag-n-drop for whatever reason simply use the file requester buttons ( ? ).
There are two instances when file requesters are useful and opening from shell is useful. If you are trying to load disk.info and you can't see it use the file requester or type "IconClone --o disk1.info disk.info" where disk1.info is the source for new images and disk.info receives them.
To make things easier for testing I simply copy the binary file of IconClone to Ram Disk then in a shell "IconClone --o". Then no app icon is required and Printf statements can provide feedback in the shell for debugging.