You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 6, 2020. It is now read-only.
You can call it a usability or functionality or workflow issue but it appears that the contract deployment transaction doesn't happen (execute) until you click the Test button on the Invoke Contract dialog. This is counter-intuitive and will lead to a lot of "user error". Checkout the function btnTestScript_Click() here:
Agreed, but this is the way it has been implemented in neo-project/neo-gui. For the sake of future updates I don't think it is a big enough problem to warrant changing the workflow.
Thoughts?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
You can call it a usability or functionality or workflow issue but it appears that the contract deployment transaction doesn't happen (execute) until you click the Test button on the Invoke Contract dialog. This is counter-intuitive and will lead to a lot of "user error". Checkout the function
btnTestScript_Click()
here:neo-gui-developer/neo-gui/UI/InvokeContractDialog.cs
Line 254 in d1cc879
People are going to expect the deployment should take place when you click the Deploy button in the Deploy Contract dialog. This should be refactored.
The text was updated successfully, but these errors were encountered: