[UX] Apply filtering in contract invoke input fields

[ixje]

It is possible to type in the contract name and "operation" input fields, but no filtering is applied. Ideally filtering should be applied, otherwise disable the possibility to type in those fields.

[robliou]

@ixje @devhawk Erik, can you please explain what you mean by 'filtering' here?

From my end, I've been unable to get these methods to work, much less get consistent access to this page..?

Is this page even operable at this point for you (i.e. do the methods function properly when called from this page)?

[devhawk]

Yes, this page works for me. I just did the following:

1. opened the Registrar sample
2. opened the command palettte
3. Selected the "Neo N3: Invoke Contract" command

You can also open the register-sample-domain.neo-invoke.json to bring up the invoke file editor

This brings up the contract invoke file editor. When the cursor is in the top text box, it will display the visual from @ixje screenshot of all the contract's DevTracker is aware of and their operations.

What I think @ixje is asking for is for that visual to automatically exclude contracts from the visualization as the user types. So if the user types N, then NeoToken contract should remain but GasToken contract should disappear

[robliou]

Yes, this page works for me. I just did the following:

1. opened the Registrar sample
2. opened the command palettte
3. Selected the "Neo N3: Invoke Contract" command

You can also open the register-sample-domain.neo-invoke.json to bring up the invoke file editor

This brings up the contract invoke file editor. When the cursor is in the top text box, it will display the visual from @ixje screenshot of all the contract's DevTracker is aware of and their operations.

What I think @ixje is asking for is for that visual to automatically exclude contracts from the visualization as the user types. So if the user types N, then NeoToken contract should remain but GasToken contract should disappear

Thanks, Harry. I followed these steps and was able to get the Invoke Contract menu to show up.

I tried a simple command, GetContract, with a sample contract name as an argument. However, even though my status is confirmed as being connected (using both MainNet as well as TestNet), I keep getting the error "You must be connected to a NeoExpress blockchain to invoke contract."

Does this error show up for you as well?

@devhawk

[ixje]

I’m on a holiday and have very poor internet connectivity. As i can hardly load a webpage i can’t lookup what i wrote and made a screenshot of. I’ll revisit when i’m back

On 5 Jun 2022, at 11:38, Rob L. @.***> wrote:

 Yes, this page works for me. I just did the following:

opened the Registrar sample opened the command palettte Selected the "Neo N3: Invoke Contract" command You can also open the register-sample-domain.neo-invoke.json to bring up the invoke file editor

This brings up the contract invoke file editor. When the cursor is in the top text box, it will display the visual from @ixje screenshot of all the contract's DevTracker is aware of and their operations.

What I think @ixje is asking for is for that visual to automatically exclude contracts from the visualization as the user types. So if the user types N, then NeoToken contract should remain but GasToken contract should disappear

Thanks, Harry. I followed these steps and was able to get the Invoke Contract menu to show up.

I tried a simple command, GetContract, with a sample contract name as an argument. However, even though my status is confirmed as being connected (using both connecting to both MainNet as well as TestNet), I keep getting the error "You must be connected to a NeoExpress blockchain to invoke contract."

Does this happen error show up for you as well?

@devhawk

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[devhawk]

Contract execution on MainNet or TestNet is disabled at this time. We could probably allow for contract invocation as that does not require wallet integration. But contract execution that modifies chain state (i.e. submitting a signed transaction) has to remain disabled until wallet integration is added

[robliou]

Contract execution on MainNet or TestNet is disabled at this time. We could probably allow for contract invocation as that does not require wallet integration. But contract execution that modifies chain state (i.e. submitting a signed transaction) has to remain disabled until wallet integration is added

OK, so contract invocation is currently not enabled or even functioning for other users as well? Just wanted to confirm that..