topic Re: Hide the Reload Window and show only input box in QlikView

Hide the Reload Window and show only input box

parul_mehta — Wed, 25 Nov 2020 16:16:04 GMT

I have an input box which is displayed when I press CTRL + R, where the user enters the required component name

On pressing CTRL + R I want to hide the Script Execution progress window, and show only the input box

Can you please let me know if it is possible, and what code needs to be added and where,

I need to hide the script execution progress window and show only the input box.

Re: Hide the Reload Window and show only input box

stabben23 — Tue, 27 Jun 2017 05:59:30 GMT

Hi Parul,

You can use a macro to hide script window.

Sub RefreshData
ActiveDocument.DoReload 2,false,false
End Sub

Re: Hide the Reload Window and show only input box

BalaBhaskar_Qlik — Tue, 27 Jun 2017 06:04:47 GMT

Try this:

Hide Script Execution Progress Window

Re: Hide the Reload Window and show only input box

parul_mehta — Tue, 27 Jun 2017 06:07:04 GMT

At what stage should I call this macro ?

Re: Hide the Reload Window and show only input box

parul_mehta — Tue, 27 Jun 2017 06:07:44 GMT

Bala, I have read this article ..

Where and how should I use this ?

Re: Hide the Reload Window and show only input box

stabben23 — Tue, 27 Jun 2017 06:15:06 GMT

How do you Call the script execution right now?

you should use a button or something similar to fire the trigger.

Re: Hide the Reload Window and show only input box

parul_mehta — Tue, 27 Jun 2017 08:30:31 GMT

I am just loading on CTRL + R

Need to use the same .

on CTRL+R, only input box should display, not script progress window

at what stage would it be best to call the macro ?

Re: Hide the Reload Window and show only input box

Peter_Cammaert — Tue, 27 Jun 2017 09:23:23 GMT

In QV Desktop, Ctrl-R by default triggers a standard reload, which includes displaying the Progress Window. You can circumvent that dialog by launching a reload by way of a macro, but AFAIK the macro cannot replace the Ctrl-R action. You'll have to devise another User sequence (for example using a big button, as suggested before) to trigger an alternate reload with your own chain of actions and dialogs.