diff --git a/docs/images/a-deploy-run-deployed-instances.png b/docs/images/a-deploy-run-deployed-instances.png deleted file mode 100644 index 8d2cd5632b5..00000000000 Binary files a/docs/images/a-deploy-run-deployed-instances.png and /dev/null differ diff --git a/docs/images/a-deploy-run-open-instance.png b/docs/images/a-deploy-run-open-instance.png deleted file mode 100644 index 4cbcb1a2d78..00000000000 Binary files a/docs/images/a-deploy-run-open-instance.png and /dev/null differ diff --git a/docs/images/a-jvm-calling-instance.png b/docs/images/a-jvm-calling-instance.png deleted file mode 100644 index f12dcce662c..00000000000 Binary files a/docs/images/a-jvm-calling-instance.png and /dev/null differ diff --git a/docs/images/a-udapp-inputs.png b/docs/images/a-udapp-inputs.png deleted file mode 100644 index ec683501359..00000000000 Binary files a/docs/images/a-udapp-inputs.png and /dev/null differ diff --git a/docs/images/a-udapp-multi-param-man.png b/docs/images/a-udapp-multi-param-man.png deleted file mode 100644 index afb7e4f3a83..00000000000 Binary files a/docs/images/a-udapp-multi-param-man.png and /dev/null differ diff --git a/docs/images/udapp/a-deploy-run-deployed-instances.png b/docs/images/udapp/a-deploy-run-deployed-instances.png new file mode 100644 index 00000000000..77a865d4d94 Binary files /dev/null and b/docs/images/udapp/a-deploy-run-deployed-instances.png differ diff --git a/docs/images/udapp/a-deploy-run-open-instance.png b/docs/images/udapp/a-deploy-run-open-instance.png new file mode 100644 index 00000000000..a8fe553daaa Binary files /dev/null and b/docs/images/udapp/a-deploy-run-open-instance.png differ diff --git a/docs/images/udapp/a-jvm-calling-instance.png b/docs/images/udapp/a-jvm-calling-instance.png new file mode 100644 index 00000000000..1f32af9dfb8 Binary files /dev/null and b/docs/images/udapp/a-jvm-calling-instance.png differ diff --git a/docs/images/udapp/a-udapp-inputs.png b/docs/images/udapp/a-udapp-inputs.png new file mode 100644 index 00000000000..cc581a0bfb0 Binary files /dev/null and b/docs/images/udapp/a-udapp-inputs.png differ diff --git a/docs/images/udapp/a-udapp-multi-param-man.png b/docs/images/udapp/a-udapp-multi-param-man.png new file mode 100644 index 00000000000..0d45b5b3f6d Binary files /dev/null and b/docs/images/udapp/a-udapp-multi-param-man.png differ diff --git a/docs/images/udapp/click-caret.png b/docs/images/udapp/click-caret.png new file mode 100644 index 00000000000..6cac2d64b73 Binary files /dev/null and b/docs/images/udapp/click-caret.png differ diff --git a/docs/images/udapp/scientific-notation.png b/docs/images/udapp/scientific-notation.png new file mode 100644 index 00000000000..8cc46504d99 Binary files /dev/null and b/docs/images/udapp/scientific-notation.png differ diff --git a/docs/plugin_list.md b/docs/plugin_list.md index 4fe2bd5f1be..24ed9995711 100644 --- a/docs/plugin_list.md +++ b/docs/plugin_list.md @@ -398,7 +398,6 @@ Monitor and analyze your smart contracts inside Remix using Sentio. :class-card: plugin-card sd-border-1 sd-rounded-2 :link-type: url :link: https://remix.ethereum.org/?#activate=solidityscan -:img-top: images/plugin-list/solidityscan.png Real-time security analysis of your Solidity smart contracts. diff --git a/docs/udapp.md b/docs/udapp.md index c877801c846..4b828600ca3 100644 --- a/docs/udapp.md +++ b/docs/udapp.md @@ -2,15 +2,15 @@ ## Interacting with deployed contracts -After a contract is deployed or after it is accessed with AtAddress, the deployed instance will appear in the **Deploy/Unpinned Contracts** section at the bottom of the Deploy & Run panel. +After a contract is deployed or after it is accessed with `AtAddress`, the deployed instance will appear in the **Deploy/Unpinned Contracts** section at the bottom of the Deploy & Run panel. -![](images/a-deploy-run-deployed-instances.png) +![Deployed Instances](images/udapp/a-deploy-run-deployed-instances.png) The deployed contract's address is visible as are a few other icons - one of which is the **pin** icon. ## Pinned contracts -When a contract is pinned, it will jump up to the **Pinned Contracts** section and Remix will save the contract's address and the ABI (in the .deploys folder of the current Workspace). When Remix is refreshed, the pinned contracts will be loaded into the Pinned Contracts section. +When a contract is pinned, it will jump up to the **Pinned Contracts** section and Remix will save the contract's address and the ABI in the `.deploys` folder of the current Workspace. When Remix is refreshed, the pinned contracts will be loaded into the **Pinned Contracts** section. ### Pinned contracts are chain & Workspace specific @@ -20,7 +20,7 @@ Because a pinned contract's address and ABI are stored in a File Explorer Worksp To see a contract's functions, click the caret on the left side of the panel. -![](images/a-deploy-run-caret.png) +![Click Deployed Contracts caret](images/udapp/click-caret.png) The functions' buttons can have different colors. @@ -30,10 +30,7 @@ The functions' buttons can have different colors. - Red buttons are for `payable` functions. Clicking a red button will create a new transaction and this transaction can accept a **value** (typically ETH). The amount of value is set in the **Value** field which is under the Gas Limit field. -![](images/a-jvm-calling-instance.png) - -See more information about [Solidity -modifiers](https://docs.soliditylang.org/en/latest/cheatsheet.html#modifiers) - in the Solidity docs. +![Calling different function types](images/udapp/a-jvm-calling-instance.png) ## Inputting parameters @@ -43,7 +40,7 @@ A function has two views - the collapsed and the expanded view, which is visible - Numbers and addresses do not need to be wrapped in double quotes. - Strings do not need to be wrapped. -![](images/a-udapp-inputs.png) +![Inputting Parameters in function calls](images/udapp/a-udapp-inputs.png) ### Inputting parameters in the collapsed view @@ -57,7 +54,7 @@ In the example above the "delegate" function has 3 parameters. Clicking the 'down' caret brings you to the expanded view - where parameters are input one at a time. -![](images/a-udapp-multi-param-man.png) +![](images/udapp/a-udapp-multi-param-man.png) ## Low level interactions @@ -65,11 +62,11 @@ Low level interactions are used to send funds or calldata or funds & calldata to The low level interactions section is below the functions in each deployed contract. -![](images/a-deploy-run-open-instance.png) - -Please note the following: +![](images/udapp/a-deploy-run-open-instance.png) -- If you are executing a plain Ether transfer to a contract, you need to have the receive() function in your contract. If your contract has been deployed and you want to send it funds, you would input the amount of Ether or Wei etc. (see **A** in graphic below), and then input **NOTHING** in the calldata field of **Low level interactions** (see **B** in graphic) and click the Transact button (see **C** in graphic below). +```{note} +If you are executing a plain Ether transfer to a contract, you need to have the receive() function in your contract. If your contract has been deployed and you want to send it funds, you would input the amount of Ether or Wei etc. (see **A** in graphic below), and then input **NOTHING** in the calldata field of **Low level interactions** (see **B** in graphic) and click the Transact button (see **C** in graphic below). +``` ![](images/a-receive-fun.png) @@ -81,6 +78,12 @@ Please note the following: Please see the [solidity docs](https://solidity.readthedocs.io/en/latest/contracts.html#receive-ether-function) for more specifics about using the **fallback** and **receive** functions. +## Scientific Notation in Function Inputs + +You can use scientific notation to pass numbers as function argument. For example, instead of inputting 12000000000000000000, you can input 12e18. This works for both arrays and single inputs. + +![Scientific Notation](images/udapp/scientific-notation.png) + ## Inputting a tuple or struct to a function To pass a tuple, you need to put in an array [].