Well, yes and no.
The main buttons of the current step can't be changed based on what is displayed on the current step.
So you can't easily hide them when an address is being edited.
Now, it's not impossible to do it:
HikaShop has a bunch of events in javascript:
www.hikashop.com/support/documentation/6...ocumentation.html#js
So, with these, and normal javascript events ( like DOMContentLoaded :
developer.mozilla.org/en-US/docs/Web/API...MContentLoaded_event
), you could write javascript code to handle this on the checkout. But this will probably require a developer to spend at least several hours to get right. So, it's not easy.
Also, I would recommend another approach. Instead of trying to hide the buttons when the address is edited, I would recommend adapting your checkout workflow. The "continue shopping" button, for example, is only displayed on the first step of the checkout.
So, I would recommend having the first step of the checkout with the cart and coupon views, and then you could have the login and address views on a second step. That way, you wouldn't have the "continue shopping" button at all on the login / address step.
And if you have a checkout in several steps, then the login / address step usually won't be the last step. So you won't have a "finish" button on the bottom right corner, but a "next" button. And the "next" button could be used by the user the same way as the "ok" button.
You can read more about the the checkout workflow here:
www.hikashop.com/support/documentation/4...eckout-workflow.html